I understand. I wasn't doing things right. Now it is very clear.
thanks a lot.
Franck
Le 16 nov. 2023 à 18:42, Alan Bishop abishop@redhat.com a écrit :
On Thu, Nov 16, 2023 at 12:28 AM Franck VEDEL <franck.vedel@univ-grenoble-alpes.fr mailto:franck.vedel@univ-grenoble-alpes.fr> wrote:
Hi,
I come back to a point that caused me a big problem, because I would like to understand something that I did not do correctly. I have a lab with an Openstack (2023.1, kolla-ansible, ubuntu 22-04, 2 nodes) and to show that it works, I start with an LVM backend. Everything is working. I'm adding a Ceph (Pacific) cluster and want to switch from LVM backend to CEPH. If we edit the globals.yml file and make the changes, then the "deploy" command, the LVM backend is still in the list of backends. If we restart the cinder containers, same thing. If we do "stop" then "deploy": same thing.
I had to do "stop", "destroy", "deploy" to no longer have the LVM backend but only the CEPH backend.
My question is therefore the following: what should we do in this situation? Is there a solution to easily no longer take into account a backend?
cinder-volume services generate an entry in the cinder DB, which persists even when the service is no longer running ("openstack volume service list" will show the service being down). You can use the cinder-manage command to clean up stale entries in the DB, such as the one for your LVM backend.
I refer you to this [1] thread, which contains an example of using the command, plus some useful information on where to run the command (basically, do it on a controller node).
[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack....
Alan
Thansk for your help
Franck