Skip to content

Reset sshd timeout in upgrade_sonic.yml.#6839

Merged
yutongzhang-microsoft merged 1 commit intosonic-net:masterfrom
yutongzhang-microsoft:yutongzhang/reset_sshd_timeout
Nov 17, 2022
Merged

Reset sshd timeout in upgrade_sonic.yml.#6839
yutongzhang-microsoft merged 1 commit intosonic-net:masterfrom
yutongzhang-microsoft:yutongzhang/reset_sshd_timeout

Conversation

@yutongzhang-microsoft
Copy link
Copy Markdown
Contributor

Description of PR

In pr [https://github.com/https://github.com/https://github.com/sonic-net/sonic-buildimage/pull/12109], it decrease the sshd timout from 15mins to 5mins. It may cause timeout when executing reduce_and_add_sonic_images in upgrade_sonic.yml. So in this pr, we reset this time before executing reduce_and_add_sonic_images.

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Back port request

  • 201911
  • 202012
  • 202205

Approach

What is the motivation for this PR?

In pr [https://github.com/https://github.com/https://github.com/sonic-net/sonic-buildimage/pull/12109], it decrease the sshd timout from 15mins to 5mins. It may cause timeout when executing reduce_and_add_sonic_images in upgrade_sonic.yml. So in this pr, we reset this time before executing reduce_and_add_sonic_images.

How did you do it?

Modify the value /etc/ssh/sshd_config/ClientAliveInterval in upgrade_sonic.yml.

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

@yutongzhang-microsoft yutongzhang-microsoft merged commit 33bdb51 into sonic-net:master Nov 17, 2022
@yutongzhang-microsoft yutongzhang-microsoft deleted the yutongzhang/reset_sshd_timeout branch November 17, 2022 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants