octavia health manager ports losing their address after controller reboot

Bug #1746742 reported by Brent Eagles on 2018-02-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
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.

Brent Eagles (beagles) on 2018-02-01
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
Brent Eagles (beagles) wrote :

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:

While the workaround works, it would be good to figure out the actual issue.

Reviewed: https://review.openstack.org/540955
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=c5dca891004e259d980aa8f33294c814d5eff0f8
Submitter: Zuul
Branch: master

commit c5dca891004e259d980aa8f33294c814d5eff0f8
Author: Brent Eagles <email address hidden>
Date: Mon Feb 5 14:30:53 2018 -0330

    Workaround reboot issue in Octavia hm interface template

    The health manager port fails to start on reboot if the ONBOOT line
    appears after the longish OVS_EXTRA line.

    Closes-Bug: #1746742
    Change-Id: Ib12d0c0c7712bfd3d8adb032d174e4b5829bf913

Changed in tripleo:
status: In Progress → Fix Released

This issue was fixed in the openstack/tripleo-common 8.5.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers