Closed dgsudharsan closed 3 months ago
@adyeung @sg893052 @rajendra-dendukuri FYI This issue is blocking in some scenarios as sflow depends on system ready, else will wait for 3 minutes. Please refer to https://github.com/sonic-net/SONiC/pull/1627 .This results in sflow test failure.
@sflow FYI
@dgsudharsan @Junchao-Mellanox We could consider to ignore the ztp service for system ready. Sysmonitor has the logic in place to skip the services mentioned in the platform specific system_health configuration file under "services_to_ignore" field list.
/usr/share/sonic/device/{platform_name}/system_health_monitoring_config.json
{
"services_to_ignore": ["ztp.service"],
"devices_to_ignore": [],
"user_defined_checkers": [],
"polling_interval": 60,
"led_color": {
"fault": "amber",
"normal": "green",
"booting": "orange_blink"
}
}
@sg893052 This is not a platform specific issue and would occur in any platform since ZTP is common service. I prefer not adding this to platform directory. This needs to be handled in health monitor. For feature table we check if the feature is enabled or disabled and only consider it for system monitoring. Same should be done for ZTP through special handling
@dgsudharsan @adyeung https://github.com/sonic-net/sonic-buildimage/pull/18911 is the PR raised to address this issue.
Description
When ZTP is disabled if system-health services starts after sonic-ztp exit, system ready is show as no ready with ZTP shown as down.
If system-health starts before ZTP exit this issue is not seen
Good state
Issue state
In both scenarios ZTP is disabled
This issue can be reproduced easily even if ztp starts after healthd. Restarting system-health service will result in problem state
Steps to reproduce the issue:
Describe the results you received:
System is shown as not ready
Describe the results you expected:
System should be in ready state as ztp is administratively disabled.
Output of
show version
:(paste your output here or download and attach the file here )