Skip to content

[config reload][202012] Call systemctl reset-failed for snmp,telemetry,mgmt-f…#1786

Merged
qiluo-msft merged 1 commit intosonic-net:202012from
Junchao-Mellanox:cherry-pick-1173
Aug 30, 2021
Merged

[config reload][202012] Call systemctl reset-failed for snmp,telemetry,mgmt-f…#1786
qiluo-msft merged 1 commit intosonic-net:202012from
Junchao-Mellanox:cherry-pick-1173

Conversation

@Junchao-Mellanox
Copy link
Copy Markdown
Collaborator

@Junchao-Mellanox Junchao-Mellanox commented Aug 27, 2021

Back port PR #1773 to 202012 branch.

What I did

When issue config reload -y or config load_minigraph -y command, most of the sonic services will be reset by command systemctl reset-failed <service_name>. The purpose is to avoid services reach to its start retry limit and cannot be started. However, systemctl reset-failed only resets those services belong to sonic.target, snmp, telemetry and mgmt-framework are not part of them. So if we run config reload -y or config load_minigraph -y continues, snmp, telemetry and mgmt-framework services might enter into failed state. This PR is to fix the issue.

How I did it

Also call systemctl reset-failed for services like snmp, telemetry and mgmt-framework.

How to verify it

Manual test.

Previous command output (if the output of a command-line utility has changed)

No command output changes.

New command output (if the output of a command-line utility has changed)

No command output changes.

…ramework services (sonic-net#1773)

When issue `config reload -y` or `config load_minigraph -y` command, most of the sonic services will be reset by command `systemctl reset-failed <service_name>`. The purpose is to avoid services reach to its start retry limit and cannot be started. However, `systemctl reset-failed` only resets those services belong to sonic.target, snmp, telemetry and mgmt-framework are not part of them. So if we run `config reload -y` or `config load_minigraph -y` continues, snmp, telemetry and mgmt-framework services might enter into failed state. This PR is to fix the issue.

I would like to cherry-pick this fix to 202012 branch, but this fix also depends on PR sonic-net/sonic-buildimage#7846. So if we decide to cherry-pick this PR to 202012, we need cherry-pick sonic-net/sonic-buildimage#7846 first.

Also call `systemctl reset-failed` for services like snmp, telemetry and mgmt-framework.

Manual test.
+
@Junchao-Mellanox Junchao-Mellanox changed the title [config reload] Call systemctl reset-failed for snmp,telemetry,mgmt-f… [config reload][202012] Call systemctl reset-failed for snmp,telemetry,mgmt-f… Aug 27, 2021
@dprital
Copy link
Copy Markdown
Collaborator

dprital commented Aug 28, 2021

@qiluo-msft - Can you please review. Thanks.

@qiluo-msft qiluo-msft merged commit 7041400 into sonic-net:202012 Aug 30, 2021
@Junchao-Mellanox Junchao-Mellanox deleted the cherry-pick-1173 branch October 29, 2021 01:46
stepanblyschak pushed a commit to stepanblyschak/sonic-utilities that referenced this pull request Apr 18, 2022
…627)

7041400 [config reload] Call systemctl reset-failed for snmp,telemetry,mgmt-framework services (sonic-net#1773) (sonic-net#1786)
399d370 Fix logic in RIF counters print (sonic-net#1732)
8329544 [vnet_route_check] don't hardcode prefix length of /24 (sonic-net#1756)
193b028 [neighbor-advertiser] delete the tunnel maps appropriately (sonic-net#1663)
2c82bcf [neighbor_advertiser] Use existing tunnel if present for creating tunnel mappings (sonic-net#1589)
8e22960 [202012][Config] Update config command of Kdump. (sonic-net#1778)
be3e5c6 [show][config] cli refactor for muxcable with abstract class implementation from vendors (sonic-net#1722) (sonic-net#1782)
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.

3 participants