5 mins after swact calico-kube-controllers pod not getting ready
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Joseph Richard |
Bug Description
Brief Description
-----------------
After swact-host, checking pod status. After 5 mins, calico-
Severity
--------
Major
Steps to Reproduce
------------------
as description
TC-name: mtc/test_
Expected Behavior
------------------
pod get ready in a reasonable time
Actual Behavior
----------------
Reproducibility
---------------
Reproducible
System Configuration
-------
Multi-node system
IPv6
Lab-name: WCP_71-75
Branch/Pull Time/Commit
-------
master as of
Load: 2019-10-09_20-00-00
Last Pass
---------
Unknown
Timestamp/Logs
--------------
2019-10-10 07:55:15,693] 311 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://[face::2]:5000/v3 --os-user-
[2019-10-10 07:56:40,684] 311 DEBUG MainThread ssh.send :: Send 'kubectl get nodes'
[2019-10-10 07:56:40,954] 433 DEBUG MainThread ssh.expect :: Output:
NAME STATUS ROLES AGE VERSION
compute-0 Ready <none> 29m v1.16.0
compute-1 Ready <none> 29m v1.16.0
compute-2 Ready <none> 29m v1.16.0
controller-0 Ready master 74m v1.16.0
controller-1 Ready master 37m v1.16.0
controller-1:~$
[
[2019-10-10 07:56:48,499] 311 DEBUG MainThread ssh.send :: Send 'kubectl get pod -o=wide --all-namespaces'
[2019-10-10 07:56:48,719] 433 DEBUG MainThread ssh.expect :: Output:
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system calico-
k
0-10 08:01:47,379] 311 DEBUG MainThread ssh.send :: Send 'kubectl get pod -o=wide --all-namespaces'
[2019-10-10 08:01:47,596] 433 DEBUG MainThread ssh.expect :: Output:
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system calico-
Test Activity
-------------
Sanity
tags: | added: stx.retestneeded |
@Peng, what is the impact of this? How long does it take for this pod to recover?