VMs are unusable after nova_libvirt container redeployment

Bug #1569828 reported by Piotr Misiak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
High
Hui Kang
Liberty
Fix Released
High
Jeffrey Zhang
Mitaka
Fix Released
High
Jeffrey Zhang

Bug Description

libvirt domains XML definitions are stored in /etc/libvirt/qemu directory inside nova_libvirt container
this have to be persistent (stored on a named volume)

after nova_libvirt redeployment (docker rm /docker run) all libvirt domains are "Transient" because they don't have XML definitions and they won't survive next host reboot, I can't also attach a volume to them:

libvirtError: Requested operation is not valid: cannot modify device on transient domain

I think this is critical issue.

Hui Kang (huikang27)
Changed in kolla:
status: New → Confirmed
assignee: nobody → Hui Kang (huikang27)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (master)

Fix proposed to branch: master
Review: https://review.openstack.org/305471

Changed in kolla:
status: Confirmed → In Progress
Changed in kolla:
importance: Undecided → High
milestone: none → newton-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (master)

Reviewed: https://review.openstack.org/305471
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=a01355029f6060ca77a25ea00bfb41d4b22c0581
Submitter: Jenkins
Branch: master

commit a01355029f6060ca77a25ea00bfb41d4b22c0581
Author: Hui Kang <email address hidden>
Date: Wed Apr 13 16:08:33 2016 -0400

    Add named volume for nova-libvirt

    VM instance state (e.g., instance.xml) should be persistent
    regardless of nova-libvirt container.

    Change-Id: I4463d0634db2aaefde7dc2c45a144e920d9cb1ac
    Closes-Bug: #1569828

Changed in kolla:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/kolla 3.0.0.0b2

This issue was fixed in the openstack/kolla 3.0.0.0b2 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (stable/mitaka)

Reviewed: https://review.openstack.org/344134
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=48934eeb21995ddf9ce23b6f5f41617431e0f741
Submitter: Jenkins
Branch: stable/mitaka

commit 48934eeb21995ddf9ce23b6f5f41617431e0f741
Author: Hui Kang <email address hidden>
Date: Wed Apr 13 16:08:33 2016 -0400

    Add named volume for nova-libvirt

    VM instance state (e.g., instance.xml) should be persistent
    regardless of nova-libvirt container.

    Change-Id: I4463d0634db2aaefde7dc2c45a144e920d9cb1ac
    Closes-Bug: #1569828
    (cherry picked from commit a01355029f6060ca77a25ea00bfb41d4b22c0581)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (stable/liberty)

Reviewed: https://review.openstack.org/344135
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=2a6af0d151f2f8f44257fbd2e736a8f3d5cf0cb8
Submitter: Jenkins
Branch: stable/liberty

commit 2a6af0d151f2f8f44257fbd2e736a8f3d5cf0cb8
Author: Hui Kang <email address hidden>
Date: Wed Apr 13 16:08:33 2016 -0400

    Add named volume for nova-libvirt

    VM instance state (e.g., instance.xml) should be persistent
    regardless of nova-libvirt container.

    Change-Id: I4463d0634db2aaefde7dc2c45a144e920d9cb1ac
    Closes-Bug: #1569828
    (cherry picked from commit a01355029f6060ca77a25ea00bfb41d4b22c0581)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 2.0.3

This issue was fixed in the openstack/kolla 2.0.3 release.

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

Other bug subscribers

Remote bug watches

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