Controller-0 showing disabled/offline in dm while it is unlocked/available in sysinv
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Mihnea Saracin |
Bug Description
Brief Description
-----------------
Controller-0 is shown as disabled/offline in DM
[2021-02-03 18:52:44,489] 314 DEBUG MainThread ssh.send :: Send 'kubectl get hosts -n=deployment -o=wide'
[2021-02-03 18:52:44,602] 436 DEBUG MainThread ssh.expect :: Output: NAME ADMINISTRATIVE OPERATIONAL AVAILABILITY PROFILE INSYNC RECONCILED controller-0 unlocked disabled offline controller-
But in sysinv, it is unlocked/available
[2021-02-03 18:12:39,506] 314 DEBUG MainThread ssh.send :: Send 'system --os-endpoint-type internalURL --os-region-name RegionOne host-show controller-0'
[2021-02-03 18:12:40,497] 436 DEBUG MainThread ssh.expect :: Output: +------
Steps to Reproduce
------------------
Fresh install the system
Expected Behavior
------------------
DM shows controller-0 unlocked and available
Actual Behavior
----------------
DM shows controller-0 disabled and offline
Reproducibility
---------------
Intermittent
System Configuration
-------
Distributed Cloud - System Controller
Branch/Pull Time/Commit
-------
stx master build on "2020-02-01"
Timestamp/Logs
--------------
[sysadmin@
[2021-02-03 18:52:23,266] 69 INFO MainThread kube_helper.
[2021-02-03 18:52:23,267] 479 DEBUG MainThread ssh.exec_cmd:: Executing command...
[2021-02-03 18:52:23,267] 314 DEBUG MainThread ssh.send :: Send 'kubectl get hosts -n=deployment -o=wide'
[2021-02-03 18:52:23,382] 436 DEBUG MainThread ssh.expect :: Output: NAME ADMINISTRATIVE OPERATIONAL AVAILABILITY PROFILE INSYNC RECONCILED controller-0 unlocked disabled offline controller-
Test Activity
-------------
Regression Testing
CVE References
Changed in starlingx: | |
assignee: | nobody → Mihnea Saracin (msaracin) |
tags: | added: stx.containers |
Changed in starlingx: | |
importance: | Undecided → Low |
status: | New → Triaged |
After node reboot the deployment manager pod was left in a Unknown state. Adding the deployment manager's namespace to the pod recovery service will allow recovery of the deployment manager's functionality.
Fix proposed here: https:/ /review. opendev. org/c/starlingx /integ/ +/778737