Openstack Component not working

asked 2019-10-23 15:38:20 -0600

kums gravatar image

Hi All, I am new to openstack and it's deployment, so having some issues with it.

I deployed openstack bundle using juju(version 2.6.9-bionic-amd64) and this tutorial https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/install-openstack-bundle.html (https://docs.openstack.org/project-de...).

After deployment I found out ceph-osd and ceph-radosgw has status "blocked" and message "No block devices detected using current configuration". Can you please shed light on what the problem maybe. Also some other components such as "nova-compute" complains of "Incomplete relations: storage-backend". What do I need to do to rectify this. I have tried to instal openstack by components, but this does not resolve it.

I cannot upload pictures because I am a new member, but below shows what I see, when I run juju status

BlockquoteUnit Workload Agent Machine Public address Ports Message ceph-mon/0 waiting idle 1/lxd/0 172.20.0.123 Monitor bootstrapped but waiting for number of OSDs to reach expected-osd-count (3) ceph-mon/1* waiting idle 2/lxd/0 172.20.0.117 Monitor bootstrapped but waiting for number of OSDs to reach expected-osd-count (3) ceph-mon/2 waiting idle 3/lxd/0 172.20.0.120 Monitor bootstrapped but waiting for number of OSDs to reach expected-osd-count (3) ceph-osd/0* blocked idle 1 172.20.0.111 No block devices detected using current configuration ceph-osd/1 blocked idle 2 172.20.0.112 No block devices detected using current configuration ceph-osd/2 blocked idle 3 172.20.0.113 No block devices detected using current configuration ceph-radosgw/0* blocked idle 0/lxd/0 172.20.0.116 80/tcp Missing relations: mon cinder/0* active idle 1/lxd/1 172.20.0.125 8776/tcp Unit is ready cinder-ceph/0* waiting idle 172.20.0.125 Incomplete

edit retag flag offensive close merge delete

Comments

I'm totally unfamiliar with juju, but it sounds like the ceph cluster isn't built correctly. If the message is correct and the MONs have been deployed successfully, can you run ceph -s on one of the MONs and share the output? There are probably no (or not enough) OSDs yet.

eblock gravatar imageeblock ( 2019-10-24 05:06:15 -0600 )edit

Thanks for the response. I ran ceph -s and this is the output.

2019-10-24 11:50:41.191 7f41eec6d700 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory 2019-10-24 11:50:41.191 7f41eec

kums gravatar imagekums ( 2019-10-24 06:54:35 -0600 )edit

2019-10-24 11:50:41.191 7f41eec6d700 -1 monclient: ERROR: missing keyring, cannot use cephx for authentication [errno 2] error connecting to the cluster

kums gravatar imagekums ( 2019-10-24 06:55:01 -0600 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2019-10-24 11:38:27 -0600

kums gravatar image

I have resolved this issue. The block device were not properly named in the bundle.yaml that I deployed. So I ssh into each of the ceph-osd machine using sudo juju ssh NameOfCeph, ran lsblk to see the name of the drive. I then opened juju GUI and changed the name under ceph-osd.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

Stats

Asked: 2019-10-23 15:38:20 -0600

Seen: 590 times

Last updated: Oct 24 '19