Reboot of compute node breaks VMs with volumes

Bug #1188326 reported by Brent Eagles
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Brent Eagles
Grizzly
Fix Released
High
Brent Eagles

Bug Description

The virtualization drivers perform several steps in preparation for attaching a volume to an instances. These are transient in nature and if a compute node's host system is rebooted, the VMs with attached instances cannot start. These include file system mounts and iSCSI initiated connections. The problem is known to occur with libvirt, but may also exist with other virtualization technologies.

Brent Eagles (beagles)
Changed in nova:
assignee: nobody → Brent Eagles (beagles)
Changed in nova:
status: New → In Progress
Alan Pevec (apevec)
tags: added: grizzly-backport-potential
Revision history for this message
Alan Pevec (apevec) wrote :

Fix proposed to master https://review.openstack.org/31992
(why hudson-openstack didn't put that?)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/31992
Committed: http://github.com/openstack/nova/commit/db3989586a8d5bbbcf857b9294a124ecc5fc57e8
Submitter: Jenkins
Branch: master

commit db3989586a8d5bbbcf857b9294a124ecc5fc57e8
Author: Brent Eagles <email address hidden>
Date: Thu Jun 6 15:33:42 2013 -0230

    Refresh volume connections when starting instances

    This patches adds network and block device information to the signature
    of the power_on method on the virtualization driver. The relevant call
    sites are also modified to provide the required information. The libvirt
    implementation of power_on has been altered to re-establish network and
    volume related connections.

    Fixes bug: 1188326

    Change-Id: If617b570e082e3aa321414a2680a3aa0754f6153

Changed in nova:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/grizzly)

Fix proposed to branch: stable/grizzly
Review: https://review.openstack.org/34597

Alan Pevec (apevec)
Changed in nova:
importance: Undecided → High
milestone: none → havana-2
Alan Pevec (apevec)
tags: removed: grizzly-backport-potential
Thierry Carrez (ttx)
Changed in nova:
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/grizzly)

Reviewed: https://review.openstack.org/34597
Committed: http://github.com/openstack/nova/commit/ce789f7f62ad932fb3833ec6c69bfb3fdaadcbc6
Submitter: Jenkins
Branch: stable/grizzly

commit ce789f7f62ad932fb3833ec6c69bfb3fdaadcbc6
Author: Brent Eagles <email address hidden>
Date: Thu Jun 6 15:33:42 2013 -0230

    Refresh volume connections when starting instances

    This patches adds network and block device information to the signature
    of the power_on method on the virtualization driver. The relevant call
    sites are also modified to provide the required information. The libvirt
    implementation of power_on has been altered to re-establish network and
    volume related connections.

    Fixes bug: 1188326

    (cherry picked from commit db3989586a8d5bbbcf857b9294a124ecc5fc57e8)

    Conflicts:
     nova/tests/test_vmwareapi.py
     nova/virt/baremetal/driver.py
     nova/virt/libvirt/driver.py
     nova/virt/vmwareapi/driver.py
     nova/virt/vmwareapi/vmops.py

    (Includes some collateral additions for console tests in the vmware
     tests.)

    Change-Id: If617b570e082e3aa321414a2680a3aa0754f6153

Thierry Carrez (ttx)
Changed in nova:
milestone: havana-2 → 2013.2
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.