8cc522bed5
Remove NOT_RUNNING return in case sysinv-api pid is still active but fails to ping. This scenario can happen in case sysinv-api is manually killed and SM triggers a start. Also, on the new routine to check if sysinv-api is properly replying, return ERROR instead of NOT_RUNNING for SM consistency. Testing: Tested double sysinv-api kill withing 90 seconds as per SM configuration. Upon first sysinv-api kill it should be restarted, upon second sysinv-api kill, if done within 90 seconds, a swact is triggered. Also verified that sysinv-api request routine was engaged. Also tested AIO-DX boostrap, manual swact via host-swact and patch application. After boostrap and patch application tested double sysinv-api kill and manual swact. Other fix related to this issue was addressed by this change: https://review.opendev.org/c/starlingx/stx-puppet/+/783980 Closes-Bug: 1893669 Signed-off-by: Adriano Oliveira <adriano.oliveira@windriver.com> Change-Id: I1b1ab0560237f602dadf074331f6a165d12330c7 |
||
|---|---|---|
| .. | ||
| kube-cert-rotation.sh | ||
| manage-partitions | ||
| partition_info.sh | ||
| query_pci_id | ||
| sysinv-api | ||
| sysinv-api.service | ||
| sysinv-conductor | ||
| sysinv-conductor.service | ||
| validate-platform-backup.sh | ||