Should an instance based on a deleted glance image stop working?

asked 2015-06-15 10:11:07 -0500

Jet gravatar image

updated 2015-06-15 12:12:56 -0500

I have an instance where the glance image it was created from has been deleted. Rebooting this instance caused it to not come up. Is this the expected behavior? Will instances only work if the image they were created from is in glance? If so this is surprising to me in that I thought the instances would still work even if the glance image they were based off of was deleted. Please advise. Thanks.

Here is what I saw at the end of the boot up log I see:

...
end_request: I/O error, dev vda, sector 1955384
end_request: I/O error, dev vda, sector 1955384
end_request: I/O error, dev vda, sector 438216
...

and on the compute node I see:

<179>Jun 15 15:00:43 node-3 nova-compute Exception during message handling: Image 0d350344-2692-49c9-aeb1-6a2083879c32 could not be found.
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last):
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 137, in _dispatch_and_reply
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher     incoming.message))
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 180, in _dispatch
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher     return self._do_dispatch(endpoint, method, ctxt, args)
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 126, in _do_dispatch
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher     result = getattr(endpoint, method)(ctxt, **new_args)
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.6/site-packages/nova/exception.py", line 88, in wrapped
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher     payload)
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 82, in __exit__
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher     six.reraise(self.type_, self.value, self.tb)
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.6/site-packages/nova/exception.py", line 71, in wrapped
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher     return f(self, context, *args, **kw)
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 298, in decorated_function
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher     pass
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 82, in __exit__
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher     six.reraise(self.type_, self.value, self.tb)
2015-06-15 11:00:43.885 8474 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.6 ...
(more)
edit retag flag offensive close merge delete

Comments

can you check, if this is related information-Image deletion causes instance hard-reboot failure

sunnyarora gravatar imagesunnyarora ( 2015-06-16 15:30:08 -0500 )edit

well I was able to verify that this must just be an issue with this 1 image. I was not able to reproduce the issue with a new image or the bug that you linked to. I created an instance from and image and then deleted that image. I was able to 'soft reboot', 'hard reboot', and shutdown and startup

Jet gravatar imageJet ( 2015-06-18 12:51:53 -0500 )edit