Volume can't delete, after start instance with state 'ERROR'

Bug #1509979 reported by iwan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cinder (Ubuntu)
Expired
Low
Unassigned

Bug Description

I can't delete a virtual disk from cinder after start a instance with state 'ERROR'.
Instance has been removed, but a disk have point to connect to instance: 'Attached to None on /dev/vda'

Revision history for this message
iwan (igoshin-r) wrote :

Release: Openstack Liberty.

Revision history for this message
James Page (james-page) wrote :

Hi

We need a bit more information to help triage this bug; specifically it would be good to know exactly how the instance was configured - where you trying to boot an instance for a cinder volume for example? It looks like that might be the case, but confirming would be useful.

Logs are also useful in this type of bug - the log files from cinder-volume and the nova-compute node which failed to launch the instance would be helpful in understanding what went wrong.

Marking 'Incomplete' for now - please provide the requested information and set the status back to 'New'.

Changed in cinder (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for cinder (Ubuntu) because there has been no activity for 60 days.]

Changed in cinder (Ubuntu):
status: Incomplete → Expired
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.