[K8s]: Agent down in new pod after initial agent pod is killed
Bug #1732607 reported by
Pulkit Tandon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R4.0 |
New
|
High
|
Sachchidanand Vaidya | |||
R4.1 |
New
|
High
|
Sachchidanand Vaidya | |||
Trunk |
Invalid
|
High
|
Sachchidanand Vaidya |
Bug Description
Build: R4.0-98
contrail-
Setup:
5 node system
3 Controllers. 1 of the contrail controller is Kube master
2 agent + Kube slaves
Setup provisioned through Single Yaml.
Steps:
After provisioning, everything came up fine.
Delete the agent pod on 1 of the slave.
The new container will get automatically triggered.
Observation:
agent was in "inactive' state.
Agent bring up failed in the new pod.
The reason was that agent.conf was having nothing populated.
Workaround:
Reprovision the contrail containers using single yaml.
Its easily reproducible. Please let me know if any specific logs are required.
Changed in juniperopenstack: | |
assignee: | nobody → Sachchidanand Vaidya (vaidyasd) |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/37794
Submitter: Prasanna Mucharikar (<email address hidden>)