libvirt, rbd imagebackend, disk.rescue not deleted when unrescued
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
melanie witt | ||
Newton |
Fix Committed
|
Medium
|
Lee Yarwood |
Bug Description
Reproduced on juno version (actually tested on a fork from 2014.2.3, sorry in advance if invalid but i think the legacy version is also concerned by it)
not tested on younger versions, but looking at the code they seem impacted too
For Rbd imagebackend only, when unrescuing an instance the disk.rescue file is actually not deleted on remote storage (only the rbd session is destroyed)
Consequence: when rescuing instance once again, it simply ignores the new rescue image and takes the old _disk.rescue image
Reproduce:
1. nova rescue instance
(take care that you are booted to the vda rescue disk -> when rescuing an instance from the same image it was spawned from (case by default), since fs uuid is the same, according to your image fstab (if entry UUID=) you can actually boot from the image you are actually trying to rescue, but this is another matter that concerns template building -> see https:/
edit rescue image disk
2. nova unrescue instance
3. nova rescue instance -> you get back the disk.rescue spawned in 1
if confirmed, fix coming soon
Concerning fix several possibilities:
- nova.virt.
or
- nova.virt.
Rebuild not concerned by issue, delete instance correctly deletes files on remote storage
description: | updated |
description: | updated |
Changed in nova: | |
assignee: | raphael.glon (raphael-glon) → nobody |
status: | In Progress → Confirmed |
Changed in nova: | |
assignee: | nobody → Bartek Żurawski (bartekzurawski1) |
tags: | added: ceph |
Changed in nova: | |
assignee: | Bartek Żurawski (bartekzurawski1) → melanie witt (melwitt) |
Changed in nova: | |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. openstack. org/203086
Review: https:/