Skip to content

[reload config] use /bin/bash as shell for config reload#1705

Merged
yxieca merged 1 commit intosonic-net:masterfrom
stepanblyschak:fix_reload
Jun 1, 2020
Merged

[reload config] use /bin/bash as shell for config reload#1705
yxieca merged 1 commit intosonic-net:masterfrom
stepanblyschak:fix_reload

Conversation

@stepanblyschak
Copy link
Contributor

@stepanblyschak stepanblyschak commented May 27, 2020

This change was introduced in
#1687 to fix connection reset
caused by 'config reload'. The fix was to redirect output to /dev/null.
Shell will interpret 'config reload -y &> /dev/null' as request to run
the command in the background instead of redirecting stdout/stderr to
/dev/null. It looks like not the redirection fixed the issue but the
fact that it was running in background. However, it introduced another
issue because config reload takes ~1.5m so that 90/120 sec wait time is
not enough time waiting for system to become ready.

Signed-off-by: Stepan Blyschak stepanb@mellanox.com

Description of PR

Summary:
Fixes # (issue)

Type of change

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

Approach

How did you do it?

How did you verify/test it?

I ran vlan test and verified that test waits till config reload finishes. Before this change vlan test finishes, "config reload -y" running in background gets killed and leaves system with stopped swss. With this change vlan test behaves correctly.

Any platform specific information?

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

Documentation

This change was introduced in
sonic-net#1687 to fix connection reset
caused by 'config reload'. The fix was to redirect output to /dev/null.
Shell will interpret 'config reload -y &> /dev/null' as request to run
the command in the background instead of redirecting stdout/stderr to
/dev/null. It looks like not the redirection fixed the issue but the
fact that it was running in background. However, it introduced another
issue because config reload takes ~1.5m so that 90/120 sec wait time is
not enough time waiting for system to become ready.

Change-Id: I9d44c0a55e4fa016bbe177524891c9b14302c761
Signed-off-by: Stepan Blyschak <stepanb@mellanox.com>
@stepanblyschak stepanblyschak requested a review from yxieca May 27, 2020 15:30
@yxieca yxieca merged commit 031dd2a into sonic-net:master Jun 1, 2020
shlomibitton pushed a commit to Junchao-Mellanox/sonic-mgmt that referenced this pull request Jul 12, 2020
)

This change was introduced in
sonic-net#1687 to fix connection reset
caused by 'config reload'. The fix was to redirect output to /dev/null.
Shell will interpret 'config reload -y &> /dev/null' as request to run
the command in the background instead of redirecting stdout/stderr to
/dev/null. It looks like not the redirection fixed the issue but the
fact that it was running in background. However, it introduced another
issue because config reload takes ~1.5m so that 90/120 sec wait time is
not enough time waiting for system to become ready.

Change-Id: I9d44c0a55e4fa016bbe177524891c9b14302c761
Signed-off-by: Stepan Blyschak <stepanb@mellanox.com>
kazinator-arista pushed a commit to kazinator-arista/sonic-mgmt that referenced this pull request Mar 4, 2026
Includes below commits
```
d19829c 2021-07-16 | Revert "[minigraph][port_config] Consume port_config.json while reloading minigraph (sonic-net#1705)" [Guohan Lu]
cd1f6e6 2021-07-15 | Reworked IP validation in "config interface ip add/remove" command (sonic-net#1709) [Andriy Kokhan]
66c34c0 2021-07-15 | [minigraph][port_config] Consume port_config.json while reloading minigraph (sonic-net#1705) [Blueve]
```
kazinator-arista pushed a commit to kazinator-arista/sonic-mgmt that referenced this pull request Mar 4, 2026
1c12a4050fecabd88245c7aa64a61259bc00db3b (HEAD -> 201911, origin/201911)Allowing the first time FEC and AN configuration to be pushed to SAI (sonic-net#1705) (sonic-net#2196)
Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants