So question here, we know the keyring is the issue here.
How can we go about rebuilding the keyring?
Several Questions:
* Do the controller containers nova_libvirt and nova_compute use the host files in /etc/kolla/nova-api/nova.conf
* Do the compute containers used the host files in /etc/kolla/nova-compute and /etc/kolla/nova-libvirt
Example Compute /etc/kolla/nova-compute/:
[compute-01 nova-compute]# ls
ceph.client.cinder.keyring ceph.client.nova.keyring ceph.conf config.json nova.conf
Example Compute /etc/kolla/nova-libvirt/:
[compute-01 nova-libvirt]# ls
ceph.client.nova.keyring ceph.conf config.json libvirtd.conf qemu.conf secrets
Example Controller Node /etc/kolla/nova-api/:
[control-01 nova-api]# ls
config.json nova.conf
Can we just copy the ceph.client.cinder.keyring over into nova-libvirt?
Or do we need to rebuild the entire authflow from our openstack cluster to the in-network ceph cluster that is currently running? If so, how would we go about this?
So question here, we know the keyring is the issue here.
How can we go about rebuilding the keyring?
Several Questions: nova-api/ nova.conf nova-compute and /etc/kolla/ nova-libvirt
* Do the controller containers nova_libvirt and nova_compute use the host files in /etc/kolla/
* Do the compute containers used the host files in /etc/kolla/
Example Compute /etc/kolla/ nova-compute/ : cinder. keyring ceph.client. nova.keyring ceph.conf config.json nova.conf
[compute-01 nova-compute]# ls
ceph.client.
Example Compute /etc/kolla/ nova-libvirt/ : nova.keyring ceph.conf config.json libvirtd.conf qemu.conf secrets
[compute-01 nova-libvirt]# ls
ceph.client.
Example Controller Node /etc/kolla/ nova-api/ :
[control-01 nova-api]# ls
config.json nova.conf
Can we just copy the ceph.client. cinder. keyring over into nova-libvirt?
Or do we need to rebuild the entire authflow from our openstack cluster to the in-network ceph cluster that is currently running? If so, how would we go about this?