[Bug 1509979] Re: Volume can't delete, after start instance with state 'ERROR'
James Page
james.page at ubuntu.com
Thu Sep 8 11:45:48 UTC 2016
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
** Changed in: cinder (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to cinder in Ubuntu.
https://bugs.launchpad.net/bugs/1509979
Title:
Volume can't delete, after start instance with state 'ERROR'
Status in cinder package in Ubuntu:
Incomplete
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'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1509979/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list