cleaner pods stuck at init status after system installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Triaged
|
Low
|
Unassigned |
Bug Description
Brief Description
-----------------
After lab installation is done, two cleaner pods, heat-engine-cleaner and panko-events-
Severity
--------
Major
Steps to Reproduce
------------------
Installation SX lab, check pods status
TC-name:
Expected Behavior
------------------
All pods should be in Running or Completed status
Actual Behavior
----------------
two cleaner pod in init status
Reproducibility
---------------
Seen once
System Configuration
-------
One node system
Lab-name: SM-3
Branch/Pull Time/Commit
-------
stx master as of 20190704T013000Z
Last Pass
---------
Lab: SM_2
Load: 20190701T233000Z
Timestamp/Logs
--------------
[2019-07-04 08:30:09,278] 301 DEBUG MainThread ssh.send :: Send 'kubectl get pod --all-namespaces -o=wide --field-
[2019-07-04 08:30:09,584] 423 DEBUG MainThread ssh.expect :: Output:
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
openstack cinder-
openstack heat-engine-
openstack panko-events-
[2019-07-04 08:44:34,198] 301 DEBUG MainThread ssh.send :: Send 'kubectl get pod --all-namespaces -o=wide --field-
[2019-07-04 08:44:34,458] 423 DEBUG MainThread ssh.expect :: Output:
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
openstack cinder-
openstack heat-engine-
openstack panko-events-
controller-0:~$ kubectl get pod --all-namespaces -o=wide --field-
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system ceph-pools-
openstack barbican-
openstack cinder-
openstack heat-engine-
openstack horizon-
openstack nova-api-
openstack nova-scheduler-
openstack panko-events-
controller-0:~$ date
Thu Jul 4 14:40:11 UTC 2019
Test Activity
-------------
Sanity
tags: | added: stx.retestneeded |
@Peng, Is there any system impact to this issue?