Open Stack

Hello Guys,

Thanks a lot.

I had actually checked the nova -compute.log  on the compute node and they
were showing the error I will post at the end about the cinder keyring but
I know its correct because its the same I was using on wallaby, I even
tried to use another ceph cluster with ofcouse different keyrings but its
the same issue.

Below is the error

r Stderr: '2021-09-22T15:04:31.574+0000 7fbce2f4f700 -1 auth: unable to
find a keyring on
/etc/ceph/ceph.client.cinder.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,:
(2) No such file or directory\n2021-09-22T15:04:31.574+0000 7fbce2f4f700 -1
AuthRegistry(0x7fbcdc05a8b8) no keyring found at
/etc/ceph/ceph.client.cinder.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,,
disabling cephx\n2021-09-22T15:04:31.582+0000 7fbce2f4f700 -1 auth: unable
to find a keyring on
/etc/ceph/ceph.client.cinder.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,:
(2) No such file or directory\n2021-09-22T15:04:31.582+0000 7fbce2f4f700 -1
AuthRegistry(0x7fbcdc060698) no keyring found at
/etc/ceph/ceph.client.cinder.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,,
disabling cephx\n2021-09-22T15:04:31.582+0000 7fbce2f4f700 -1 auth: unable
to find a keyring on
/etc/ceph/ceph.client.cinder.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,:
(2) No such file or directory\n2021-09-22T15:04:31.582+0000 7fbce2f4f700 -1
AuthRegistry(0x7fbce2f4e020) no keyring found at
/etc/ceph/ceph.client.cinder.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,,
disabling cephx\n[errno 2] RADOS object not found (error connecting to the
cluster)\n'
2021-09-22 15:04:31.592 8 ERROR nova.compute.manager
2021-09-22 15:04:31.592 8 ERROR nova.compute.manager During handling of the
above exception, another exception occurred:
Regards

Tony Karera




On Wed, Sep 22, 2021 at 4:50 PM Sean Mooney <smooney at redhat.com> wrote:

> On Wed, 2021-09-22 at 10:46 -0400, Laurent Dumont wrote:
> > It could also be a compute cell discovery issue maybe?
> no they shoudl still show up in the hypervior list api
> >
> > Do you see anything under "openstack compute service list"?
> if they show up in the service list but not they hyperiors api it
> means that the comptue service started and registered its service entry but
> something broke it before it could create a compute node recored in the db.
>
> with ceph the case i have hit this most often is when the keyright used by
> nova to
> get the avaiable capastiy of the ceph cluster is wrong whihc prevent the
> resoucetack and compute manager
> form actully creating the compute node record.
>
>
> it can happen for other reason too but best place to start is check if
> there is an error in the nova compute agent log and go from there.
> >
> > On Wed, Sep 22, 2021 at 10:33 AM Sean Mooney <smooney at redhat.com> wrote:
> >
> > > On Wed, 2021-09-22 at 15:39 +0200, Karera Tony wrote:
> > > > Hello Team,
> > > >
> > > > I have deployed Openstack Victoria using Kolla-ansible on Ubuntu
> 20.04
> > > and
> > > > ceph as the backend storage for Nova, Cinder and Glance.
> > > >
> > > > It finished with no error but it has failed to register any on the
> > > Compute
> > > > Nodes under Hypervisors.
> > > >
> > > > kolla-openstack) stack at deployment:~$ openstack hypervisor list
> > > >
> > > > (kolla-openstack) stack at deployment:~$
> > > >
> > > >
> > > > Any idea on how to resolve this ?
> > > that usually means that somehthing prevented the comptue agent form
> > > strating properly
> > >
> > > for example incorrect ceph keyrings there are several other case but
> you
> > > mentioned you are
> > > using ceph.
> > >
> > > if this is hte case you should see error in the compute agent log.
> > >
> > > >
> > > > Regards
> > > >
> > > > Tony Karera
> > >
> > >
> > >
> > >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210922/5064c78c/attachment-0001.htm>