octavia health manager ports losing their address after controller reboot
Bug #1746742 reported by
Brent Eagles
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
High
|
Brent Eagles | ||
Bug Description
The health manager port appears to "come up" as services are binding to the IP, but it appears to be taken down and loses its IP sometime once the system has settled.
| Changed in tripleo: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| assignee: | nobody → Brent Eagles (beagles) |
| milestone: | none → queens-rc1 |
| Changed in tripleo: | |
| status: | Triaged → In Progress |
Revision history for this message
| Brent Eagles (beagles) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to tripleo-common (master) | #2 |
| Changed in tripleo: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tripleo-common 8.5.0 | #3 |
To post a comment you must log in.
Strange issue. It seems that the multiline OVS_EXTRA parameter is interfering with the recognition of the ONBOOT parameter. Moving ONBOOT above OVS_EXTRA seems to work.
Addressed by:
https:/
While the workaround works, it would be good to figure out the actual issue.