Reboot operation fails if force_disk_config is switched to True after spawning
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
yuanyue |
Bug Description
A hard reboot operation fails if force_disk_config is switch to True after spawning the instance without a config drive.
This was found using the libvirt driver, I'm not sure if it affects other drivers.
Steps to recreate would be:
1. Spawn an instance without a config drive
2. Change force_config_drive to True in your nova.conf
3. Restart nova-compute
4. Attempt to reboot the instance
An error similar to the following message will be displayed in the nova compute logs:
2013-10-18 15:26:42.268 ERROR nova.compute.
tags: | added: compute |
tags: | added: libvirt |
description: | updated |
Changed in nova: | |
assignee: | nobody → ugvddm (271025598-9) |
Changed in nova: | |
assignee: | ugvddm (271025598-9) → nobody |
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in nova: | |
status: | Triaged → In Progress |
Changed in nova: | |
assignee: | nobody → Michael Still (mikalstill) |
status: | Confirmed → In Progress |
Changed in nova: | |
assignee: | nobody → Zhenzan Zhou (zhenzan-zhou) |
Changed in nova: | |
assignee: | Zhenzan Zhou (zhenzan-zhou) → Stephen Finucane (sfinucan) |
status: | Confirmed → In Progress |
Changed in nova: | |
assignee: | Stephen Finucane (sfinucan) → nobody |
status: | In Progress → Confirmed |
Changed in nova: | |
assignee: | nobody → Stephen Finucane (sfinucan) |
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in nova: | |
status: | Expired → Incomplete |
status: | Incomplete → In Progress |
importance: | Undecided → High |
assignee: | nobody → Timofey Durakov (tdurakov) |
Changed in nova: | |
assignee: | Timofey Durakov (tdurakov) → Stephen Finucane (stephenfinucane) |
Changed in nova: | |
assignee: | yuanyue (yyuanyuee) → Chris Dent (cdent) |
Changed in nova: | |
assignee: | Chris Dent (cdent) → yuanyue (yyuanyuee) |
This is a special case of bug 1303714 I think. The only time we should care about the value of force_config_drive is on first boot of the instance. A hard reboot should just give you what you already had, even if the value of this flag has changed in the mean time.