Skip to content

Increase syncd start timeout#2776

Merged
liat-grozovik merged 2 commits intosonic-net:masterfrom
andriymoroz-mlnx:syncd_timeout
Apr 24, 2019
Merged

Increase syncd start timeout#2776
liat-grozovik merged 2 commits intosonic-net:masterfrom
andriymoroz-mlnx:syncd_timeout

Conversation

@andriymoroz-mlnx
Copy link
Collaborator

Signed-off-by: Andriy Moroz [email protected]

- What I did
Increased syncd start timeout to let post-boot FW update on Mellanox platform finish successfully.

- How I did it
Added TimeoutSec field to the syncd service config

- How to verify it
Verified upgrade from 201803 to 201811 or master finishes successfully

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

Signed-off-by: Andriy Moroz <[email protected]>
Copy link
Collaborator

@qiluo-msft qiluo-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like a workaround, not a fix.
The fast-reboot or warm-reboot time will be impacted.

ExecStart=/usr/local/bin/syncd.sh wait
ExecStop=/usr/local/bin/syncd.sh stop
{% if sonic_asic_platform == 'mellanox' %}
TimeoutSec=150
Copy link
Collaborator

@qiluo-msft qiluo-msft Apr 14, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TimeoutSec [](start = 0, length = 10)

Is it better to use TimeoutStartSec? #Closed

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agree

@yxieca
Copy link
Contributor

yxieca commented Apr 15, 2019

@andriymoroz-mlnx do we still want to merge this change after #2788 being merged to 201803?

This is just a question, not a rejection :-)

@andriymoroz-mlnx
Copy link
Collaborator Author

yes, because if after upgrade reboot will be via power/kernel crash/etc or user will not change default in GRUB but select it manually on boot we need this fix to let post-boot FW burn finish successfully

@liat-grozovik
Copy link
Collaborator

Just to summarize.
In all recent active branches (including 201803) the FW burn is done before the reboot command (any reboot type which is supported). But in rare cases when FW is to be burn after power off/hard reset we should make sure syncd will not be restarted in the middle of that.

@liat-grozovik liat-grozovik merged commit ca7924e into sonic-net:master Apr 24, 2019
yxieca pushed a commit that referenced this pull request Apr 26, 2019
* Increase syncd start timeout

Signed-off-by: Andriy Moroz <[email protected]>

* Replace TimeoutSec to TimeoutStartSec

Signed-off-by: Andriy Moroz <[email protected]>
MichelMoriniaux pushed a commit to criteo-forks/sonic-buildimage that referenced this pull request May 28, 2019
* Increase syncd start timeout

Signed-off-by: Andriy Moroz <[email protected]>

* Replace TimeoutSec to TimeoutStartSec

Signed-off-by: Andriy Moroz <[email protected]>
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.

5 participants