Thanks for your willingness to help The issue was that images where not in raw format ( i.e the proper approach is to run "qemu-img convert -f qcow2 -O raw ...." and add the resulted image to openstack ( openstack image create ...) )
Volumes build based on a image in raw format are bootable Many thanks Steven On Thu, 20 Dec 2018 at 04:20, Eugen Block <[email protected]> wrote: > > Volumes are being created just fine in the "volumes" pool but they are > not > > bootable > > Also, ephemeral instances are working fine ( disks are being created on > the > > dedicated ceph pool "instances') > > That sounds like cinder is missing something regarding glance. So the > instance is listed as "ACTIVE" but what do you see on the instance? > Does it show something like "no bootable device" or a similar message? > > I don't have Rocky and Mimic, so there might be something else. To > rule out the qemu layer you could try to launch from a volume with kvm > like suggested in [1]. > > Is this a new setup or an upgraded environment? If it's an existing > environment, did it ever work with volumes? Do you use cephx and have > you setup rbd_secret on your compute node(s)? > > Regards, > Eugen > > [1] > http://lists.ceph.com/pipermail/ceph-users-ceph.com/2013-May/031454.html > > > Zitat von Steven Vacaroaia <[email protected]>: > > > Thanks for your prompt reply > > > > Volumes are being created just fine in the "volumes" pool but they are > not > > bootable > > Also, ephemeral instances are working fine ( disks are being created on > the > > dedicated ceph pool "instances') > > > > Access for cinder user from compute node is fine > > > > [root@ops-ctrl-new ~(devops)]# rbd --user cinder -k > > /etc/ceph/ceph.client.cinder.keyring -p volumes ls > > volume-04c3d1a6-e4f0-40bf-a257-0d76c2a6e337 > > volume-6393ea70-b05d-4926-a2e0-a4a41f8b38e7 > > volume-82d97331-6b9b-446c-a5a4-b402a5212e4c > > volume-9ed2658a-1a9c-4466-a36a-587cc50ed1ff > > volume-baa6c928-8ac1-4240-b189-32b444b434a3 > > volume-c23a69dc-d043-45f7-970d-1eec2ccb10cc > > volume-f1872ae6-48e3-4a62-9f46-bf157f079e7f > > > > > > On Wed, 19 Dec 2018 at 09:25, Eugen Block <[email protected]> wrote: > > > >> Hi, > >> > >> can you explain more detailed what exactly goes wrong? > >> In many cases it's an authentication error, can you check if your > >> specified user is allowed to create volumes in the respective pool? > >> > >> You could try something like this (from compute node): > >> > >> rbd --user <OPENSTACK_USER> -k > >> /etc/ceph/ceph.client.OPENSTACK_USER.keyring -p <POOL> ls > >> > >> additionally, try to create an image in that pool. If that works, you > >> should double check the credentials you created within ceph and > >> compare them to the credentials in your openstack configs. > >> That would be my first guess. > >> > >> Regards, > >> Eugen > >> > >> Zitat von Steven Vacaroaia <[email protected]>: > >> > >> > Hi, > >> > > >> > I'll appreciated if someone can provide some guidance for > >> troubleshooting / > >> > setting up Openstack (rocky) + ceph (mimic) so that volumes created > on > >> > ceph be bootable > >> > > >> > I have followed this > http://docs.ceph.com/docs/mimic/rbd/rbd-openstack/ > >> > enabled debug in both nova and cinder but still not been able to > figure > >> it > >> > out why volumes are not bootable > >> > > >> > Many thanks > >> > Steven > >> > >> > >> > >> _______________________________________________ > >> ceph-users mailing list > >> [email protected] > >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > >> > > > >
_______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
