Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[swss service] flush fast-reboot enabled flag upon swss stopping #3908

Merged
merged 1 commit into from
Dec 16, 2019

Conversation

yxieca
Copy link
Contributor

@yxieca yxieca commented Dec 14, 2019

- What I did

If we need to stop swss during fast-reboot procedure on the boot up path, it means that something went wrong, like syncd/orchagent crashed already, we are stopping and restarting swss/syncd to re-initialize. In this case, we should proceed as if it is a cold reboot.

Signed-off-by: Ying Xie ying.xie@microsoft.com

- How to verify it
Instrument code to cause an failure on fast-reboot recovering path. Without the change, syncd/swss will restart 3 times and stuck at failure state until manually resets the state and try again. With the change, the fast reboot fail once and recovered with a cold start automatically.

If we need to stop swss during fast-reboot procedure on the boot up path,
it means that something went wrong, like syncd/orchagent crashed already,
we are stopping and restarting swss/syncd to re-initialize. In this case,
we should proceed as if it is a cold reboot.

Signed-off-by: Ying Xie <ying.xie@microsoft.com>
@yxieca
Copy link
Contributor Author

yxieca commented Dec 15, 2019

retest vsimage please

@yxieca yxieca merged commit 9baf8f7 into sonic-net:master Dec 16, 2019
@yxieca yxieca deleted the fast-reboot branch December 16, 2019 15:58
yxieca added a commit that referenced this pull request Dec 16, 2019
If we need to stop swss during fast-reboot procedure on the boot up path,
it means that something went wrong, like syncd/orchagent crashed already,
we are stopping and restarting swss/syncd to re-initialize. In this case,
we should proceed as if it is a cold reboot.

Signed-off-by: Ying Xie <ying.xie@microsoft.com>
abdosi pushed a commit that referenced this pull request Jan 3, 2020
If we need to stop swss during fast-reboot procedure on the boot up path,
it means that something went wrong, like syncd/orchagent crashed already,
we are stopping and restarting swss/syncd to re-initialize. In this case,
we should proceed as if it is a cold reboot.

Signed-off-by: Ying Xie <ying.xie@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.

None yet

3 participants