Re: [Openstack] Snapshot: Cannot determine the parent storage pool

[John Petrini]

That's a great question and I'm honestly not sure. Anytime I've tried to do
so myself I've also received an error. A colleague of mine first renamed
the image and then deleted it without issue. I'm going to see if I can
reproduce this somehow. Thank you for the link - I may end up going a
simpler route and just snapshooting the affected instances and rebuilding
them from the snapshots so they have a base image again.

Here's the nova output from an affected VM:

nova show 63ef9e03-0b0e-4d89-9334-3a68af0a2731 | grep image
| image| Image not found
(cfa4f24e-24f5-4c03-8edf-8d0469247fa5)
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Snapshot: Cannot determine the parent storage pool

[Eugen Block]

Just out of curiosity, how exactly did you manage to delete base  
images from running instances? I was not able to do that, glance  
raised error messages when I tried it.


I'm not sure if [1] helps in any way, but here someone tried to edit  
the rbd-information for specific objects in his (copied) pool. But I  
hope there's another way than this...


Regards,
Eugen

[1] http://lists.ceph.com/pipermail/ceph-users-ceph.com/2015-May/001453.html

Zitat von John Petrini :


Hi List,

We're running Mitaka with Ceph. Recently I enabled RBD snapshots by adding
write permissions to the images pool in Ceph. This works perfectly for some
instances but is failing back to standard snapshots for others with the
following error:

Performing standard snapshot because direct snapshot failed: Cannot
determine the parent storage pool for 7a7b5119-
85da-429b-89b5-ad345cfb649e; cannot determine where to store images

Looking at the code here:
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/imagebackend.py
it appears that it looks for the pool of the base image to determine where
to save the snapshot. I believe the problem I'm encountering is that for
some of our instances the base image no longer exists.

Am I understanding this correctly and is there anyway to explicitly set the
pool to be used for snapshots and bypass this logic?

Thank You,

John Petrini




--
Eugen Block voice   : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail  : ebl...@nde.ag

Vorsitzende des Aufsichtsrates: Angelika Mozdzen
  Sitz und Registergericht: Hamburg, HRB 90934
  Vorstand: Jens-U. Mozdzen
   USt-IdNr. DE 814 013 983


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Snapshot: Cannot determine the parent storage pool

[John Petrini]

Hi List,

We're running Mitaka with Ceph. Recently I enabled RBD snapshots by adding
write permissions to the images pool in Ceph. This works perfectly for some
instances but is failing back to standard snapshots for others with the
following error:

Performing standard snapshot because direct snapshot failed: Cannot
determine the parent storage pool for 7a7b5119-
85da-429b-89b5-ad345cfb649e; cannot determine where to store images

Looking at the code here:
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/imagebackend.py
it appears that it looks for the pool of the base image to determine where
to save the snapshot. I believe the problem I'm encountering is that for
some of our instances the base image no longer exists.

Am I understanding this correctly and is there anyway to explicitly set the
pool to be used for snapshots and bypass this logic?

Thank You,

John Petrini
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack