Open Stack

Hi Alan,
Thank you for your response.
We cannot run that particular command as the container itself doesn't run.
That container is only used to set the secret and stays in exited state if
i am correct.

[root at dcn01-hci-1 ~]# podman exec -ti 3e5e6c1a7864 virsh secret-undefine
bd136bb0-fd78-5429-ab80-80b8c571d821
Error: can only create exec sessions on running containers: container state
improper

With regards,
Swogat Pradhan

On Tue, Mar 28, 2023 at 9:26 AM Alan Bishop <abishop at redhat.com> wrote:

>
>
> On Mon, Mar 27, 2023 at 5:56 PM Swogat Pradhan <swogatpradhan22 at gmail.com>
> wrote:
>
>> Update podman logs:
>> [root at dcn01-hci-1 ~]# podman logs 3e5e6c1a7864
>> ------------------------------------------------
>> Initializing virsh secrets for: dcn01:openstack
>> --------
>> Initializing the virsh secret for 'dcn01' cluster
>> (cec7cdfd-3667-57f1-afaf-5dfca9b0e975) 'openstack' client
>> The /etc/nova/secret.xml file already exists
>> error: Failed to set attributes from /etc/nova/secret.xml
>> error: internal error: a secret with UUID
>> bd136bb0-fd78-5429-ab80-80b8c571d821 already defined for use with
>> client.openstack secret
>>
>>
>> On Tue, Mar 28, 2023 at 6:19 AM Swogat Pradhan <swogatpradhan22 at gmail.com>
>> wrote:
>>
>>> Hi,
>>> For some reason, i had to redeploy ceph for my hci nodes and then found
>>> that the deployment command is giving out the following error:
>>> 2023-03-28 01:49:46.709605 |                                      |
>>>  WARNING | ERROR: Can't run container nova_libvirt_init_secret
>>> stderr: error: Failed to set attributes from /etc/nova/secret.xml
>>> error: internal error: a secret with UUID
>>> bd136bb0-fd78-5429-ab80-80b8c571d821 already defined for use with
>>> client.openstack secret
>>> 2023-03-28 01:49:46.711176 | 48d539a1-1679-623b-0af7-000000004b45 |
>>>  FATAL | Create containers managed by Podman for
>>> /var/lib/tripleo-config/container-startup-config/step_4 | dcn01-hci-0 |
>>> error={"changed": false, "msg": "Failed containers:
>>> nova_libvirt_init_secret"}
>>>
>>> Can you please tell me how I can undefine the existing secret?
>>>
>>
> Use "podman exec -ti <nova libvirt container> bash" to open a shell within
> the nova_libvirt container, then you can use virsh commands to examine and
> delete any extraneous secrets. This command might be all that you need:
>
> [root at dcn01-hci-1 ~]# podman exec -ti 3e5e6c1a7864 virsh secret-undefine
> bd136bb0-fd78-5429-ab80-80b8c571d821
>
> You should also delete the /etc/nova/secret.xml file, and let it be
> recreated when you re-run the deployment command.
>
> Alan
>
>
>>> With regards,
>>> Swogat Pradhan
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230328/339fdd00/attachment.htm>