Network cache is not flushed on deploying host when containers are destroyed
Bug #1469285 reported by
Shu Shen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Low
|
Shu Shen |
Bug Description
lxc-container-
In a multiple host deployment, the deploying host (which runs the playbooks) may not be the host for the containers being destroyed. Therefore, flush-net-cacahe is not performed on the deploying host.
This would cause connectivity problem between the deploying host and the containers before the staled net cache timed out ultimately.
Changed in openstack-ansible: | |
assignee: | nobody → Shu Shen (shu-shen) |
Changed in openstack-ansible: | |
status: | New → In Progress |
Changed in openstack-ansible: | |
importance: | Undecided → Low |
milestone: | none → 11.0.4 |
Changed in openstack-ansible: | |
status: | In Progress → Fix Committed |
Changed in openstack-ansible: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.