network interface changes don't initiate a restart
Bug #1551256 reported by
Andy McCrae
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
High
|
Andy McCrae | ||
Kilo |
Fix Released
|
High
|
Andy McCrae | ||
Liberty |
Fix Released
|
High
|
Andy McCrae |
Bug Description
When changing network interface options (e.g. adding static_routes) the task to make changes on the container doesn't initiate a restart of the interface or of the container itself.
This means the static_routes are never actually adopted unless you go afterward to restart the container/
Due to the nature of the task itself, and being a flat "container_command" we can't use notify so will have to perform some type of check in the command itself.
Changed in openstack-ansible: | |
milestone: | none → 13.0.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/286078
Review: https:/