baremetal machine fail in local boot in virtualbox

Bug #1554908 reported by bin Yu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
Fix Released
Undecided
bin Yu

Bug Description

The virtualbox driver can work in net boot mode, but fails to finish deploy and restart the virtualbox VMs in local boot mode which boots from the local hard disk.

The main problem is that ironic set the boot sequence firstly and them restart the machine, but changing boot sequence while VMs is powered on is not supported in virtualbox. So we should shutdown the VMs before change it boot sequence.

Tags: driver
bin Yu (froyo-bin)
Changed in ironic:
assignee: nobody → bin Yu (froyo-bin)
bin Yu (froyo-bin)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ironic (master)

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

bin Yu (froyo-bin)
description: updated
Changed in ironic:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ironic (master)

Reviewed: https://review.openstack.org/290951
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=d76f12f4f91a01cab447ba0833816852cba873d3
Submitter: Jenkins
Branch: master

commit d76f12f4f91a01cab447ba0833816852cba873d3
Author: bin yu <email address hidden>
Date: Wed Mar 16 02:16:09 2016 +0000

    Fix VirtualBox cannot set boot device when powered on

    When the VirtualBox VMs is powered on, Ironic cannot set the boot
    device. As a result, VirtualBox driver cannot finish deploying
    local harddisk boot VMs and also set and get Virtualbox VMs's
    boot devices correctly.

    Solution: We get boot device from set_boot_device and store the
    target boot device in driver_internal_info. Before next starting up
    we set the boot device and clean target_boot_device information,
    if the target_boot_device is None, we just skip setting boot device.
    For the get_boot_device call, if the VMs is powered off, we call
    remotebox to get current boot device. otherwise, we return the target
    boot device from driver_internal_info(if target_boot_device
    is not None) or we call remotebox to return the current boot device.
    Returning target boot device when VMs is powered on will avoid the
    problem that even users set the target boot device while returning
    the last boot device.

    Change-Id: Ice489ba642bf093fe7015aa97e6a92717f676118
    Closes-Bug: #1554908

Changed in ironic:
status: In Progress → Fix Released
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/ironic 6.0.0

This issue was fixed in the openstack/ironic 6.0.0 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.