After changing force_config_drive option to True instance fails to restart

Bug #1626198 reported by sryabin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Timofey Durakov

Bug Description

Upstream bug : https://bugs.launchpad.net/nova/+bug/1303714

Steps to reproduce:
 1. Check that force_config_drive option is set to false
 2. Boot instance
 3. Set force_config_drive option to true
 4. Restart nova services
 5. Stop instance
 6. Start instance

Expected results:
 The instance is successfully started.

Actual result:
 Cannot reboot instance: [Errno 2] No such file or directory: '/var/lib/nova/instances/instance-0000004d/disk.config'

Reproducibility:
 100%

Workaround:
 cold migrate instance after changing force_config_drive in nova.
Information:
 The traceback can be found here: http://paste.openstack.org/show/582524/

Changed in fuel:
importance: Undecided → High
Ilya Kharin (akscram)
Changed in fuel:
status: New → Confirmed
Ilya Kharin (akscram)
summary: - [upgrade] after successfully MOS non-livemigration upgrade 7->9, nova
+ [upgrade] after successfully MOS (non-)livemigration upgrade 7->9, nova
can't boot vm
summary: - [upgrade] after successfully MOS (non-)livemigration upgrade 7->9, nova
- can't boot vm
+ [upgrade] after successfully MOS upgrade 7->9, nova can't boot VMs
summary: - [upgrade] after successfully MOS upgrade 7->9, nova can't boot VMs
+ After successfully MOS upgrade 7->9, nova can't boot VMs
summary: - After successfully MOS upgrade 7->9, nova can't boot VMs
+ After successfully upgraded MOS 7->9, nova can't boot VMs
summary: - After successfully upgraded MOS 7->9, nova can't boot VMs
+ After successfully upgraded MOS 7->9, nova can't reboot VMs
Changed in fuel:
assignee: Ilya Kharin (akscram) → Timofey Durakov (tdurakov)
Ilya Kharin (akscram)
description: updated
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote : Re: After live migrating a VM without a config drive to a node with force_config_drive=True Nova can't reboot it

Note, that we've defaulted to force_config_drive=True since 9.0

summary: - After successfully upgraded MOS 7->9, nova can't reboot VMs
+ After live migrating a VM without a config drive to a node with
+ force_config_drive=True Nova can't reboot it
description: updated
tags: added: area-nova
Ilya Kharin (akscram)
tags: added: release-notes
summary: - After live migrating a VM without a config drive to a node with
- force_config_drive=True Nova can't reboot it
+ After changing force_config_drive option to True instance fails to
+ restart
description: updated
Anton Matveev (amatveev)
Changed in fuel:
milestone: 9.1 → 9.2
description: updated
tags: added: release-notes-done
removed: release-notes
tags: added: release-notes
Revision history for this message
Vitaly Sedelnik (vsedelnik) wrote :

Still waiting for upstream fix, retargeted to 9.3

Changed in fuel:
milestone: 9.2 → 9.3
tags: added: move-to-9.3
Revision history for this message
Maria Zlatkova (mzlatkova) wrote :

A release note has been added to 9.2 known issues: https://review.fuel-infra.org/#/c/29721.

tags: removed: release-notes
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.