compute-hyperv

Invalid ports after failover

Bug #1841778 reported by Lucian Petrut
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compute-hyperv
Fix Released
Undecided
Lucian Petrut

Bug Description

OVS ports can become invalid after the instances are failed over. If an instance lands back on the initial host and the ports are not cleaned up, it will be left with those stale ports.

Revision history for this message
Lucian Petrut (petrutlucian94) wrote :

Fix: https://review.opendev.org/#/c/679023/

OpenStack Infra (hudson-openstack)
Changed in compute-hyperv:
assignee: nobody → Lucian Petrut (petrutlucian94)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to compute-hyperv (master)

Reviewed: https://review.opendev.org/679023
Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=7dd16950d3dea87c9853c62fea26437de0dfd814
Submitter: Zuul
Branch: master

commit 7dd16950d3dea87c9853c62fea26437de0dfd814
Author: Lucian Petrut <email address hidden>
Date: Wed Aug 28 13:07:46 2019 +0300

    Recreate ports for failed over instances

    OVS ports can become invalid after the instances are failed over.
    If an instance lands back on the initial host and the ports are
    not cleaned up, it will be left with those stale ports.

    This change adds a config option, allowing those ports to be recreated.
    It will be enabled by default. Deployers may consider disabling it
    if the remaining ports are cleaned up when rebooting nodes or if the
    network backend is not affected by this issue.

    Closes-Bug: #1841778

    Change-Id: I58aba53b7bc0a5e8954cf31adac6e7e106944b7e

Changed in compute-hyperv:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to compute-hyperv (stable/stein)

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/680350

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to compute-hyperv (stable/stein)

Reviewed: https://review.opendev.org/680350
Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=9c07fe4b59ec7a8150a88411a8d20810dfc5bdb0
Submitter: Zuul
Branch: stable/stein

commit 9c07fe4b59ec7a8150a88411a8d20810dfc5bdb0
Author: Lucian Petrut <email address hidden>
Date: Wed Aug 28 13:07:46 2019 +0300

    Recreate ports for failed over instances

    OVS ports can become invalid after the instances are failed over.
    If an instance lands back on the initial host and the ports are
    not cleaned up, it will be left with those stale ports.

    This change adds a config option, allowing those ports to be recreated.
    It will be enabled by default. Deployers may consider disabling it
    if the remaining ports are cleaned up when rebooting nodes or if the
    network backend is not affected by this issue.

    Closes-Bug: #1841778

    Change-Id: I58aba53b7bc0a5e8954cf31adac6e7e106944b7e
    (cherry picked from commit 7dd16950d3dea87c9853c62fea26437de0dfd814)

tags: added: in-stable-stein
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/compute-hyperv 9.0.0.0rc1

This issue was fixed in the openstack/compute-hyperv 9.0.0.0rc1 release candidate.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.