DCN/cephadm: Can't run container nova_libvirt_init_secret

Bug #1935841 reported by Emilien Macchi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Medium
John Fulton

Bug Description

tripleo master / centos8-stream
DCN environment, with CephClusterName set to "az0":

Deployment failed:

2021-07-12 14:20:26.213544 | | WARNING | ERROR: Can't run container nova_libvirt_init_secret
stderr: awk: fatal: cannot open file `/etc/ceph/az0.conf' for reading (No such file or directory)
2021-07-12 14:20:26.214680 | 80615f03-9370-f3b2-cd2e-000000001dca | FATAL | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_4 | mecha-az0 | error={"changed": false, "msg": "Failed containers: nova_libvirt_init_secret"}

Revision history for this message
Emilien Macchi (emilienm) wrote :

$ ls /var/lib/tripleo-config/ceph
ceph.client.openstack.keyring ceph.client.radosgw.keyring ceph.conf

$ ls /etc/ceph
az0.client.admin.keyring az0.client.openstack.keyring az0.client.radosgw.keyring az0.conf

Changed in tripleo:
importance: Undecided → Medium
status: New → Triaged
milestone: none → xena-2
Changed in tripleo:
assignee: nobody → John Fulton (jfulton-org)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-ansible (master)
Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-ansible (master)

Reviewed: https://review.opendev.org/c/openstack/tripleo-ansible/+/800525
Committed: https://opendev.org/openstack/tripleo-ansible/commit/a02213ab1952088ce038825bec161bb3432006dd
Submitter: "Zuul (22348)"
Branch: master

commit a02213ab1952088ce038825bec161bb3432006dd
Author: John Fulton <email address hidden>
Date: Mon Jul 12 13:32:39 2021 -0400

    Pass tripleo_ceph_client_cluster in ceph_client template

    When ceph_client.yaml.j2 is built by tripleo_cephadm for
    client configuration, we pass the FSID by setting
    tripleo_ceph_client_fsid to tripleo_cephadm_fsid but we
    were not passing the tripleo_ceph_client_cluster name
    the same way which resulted in bug 1935841. This patch
    updates ceph_client.yaml.j2 to set the cluster name the
    same way that we set the cluster FSID.

    Change-Id: I7a8e819858a7d75bb0dd1eb22146916d30eeff0b
    Closes-Bug: #1935841

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-ansible (stable/wallaby)

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/tripleo-ansible/+/801247

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-ansible (stable/wallaby)

Reviewed: https://review.opendev.org/c/openstack/tripleo-ansible/+/801247
Committed: https://opendev.org/openstack/tripleo-ansible/commit/a8f9ab0353c68a73e2de118ae69729dccda0764f
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit a8f9ab0353c68a73e2de118ae69729dccda0764f
Author: John Fulton <email address hidden>
Date: Mon Jul 12 13:32:39 2021 -0400

    Pass tripleo_ceph_client_cluster in ceph_client template

    When ceph_client.yaml.j2 is built by tripleo_cephadm for
    client configuration, we pass the FSID by setting
    tripleo_ceph_client_fsid to tripleo_cephadm_fsid but we
    were not passing the tripleo_ceph_client_cluster name
    the same way which resulted in bug 1935841. This patch
    updates ceph_client.yaml.j2 to set the cluster name the
    same way that we set the cluster FSID.

    Change-Id: I7a8e819858a7d75bb0dd1eb22146916d30eeff0b
    Closes-Bug: #1935841
    (cherry picked from commit a02213ab1952088ce038825bec161bb3432006dd)

tags: added: in-stable-wallaby
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-ansible 3.3.0

This issue was fixed in the openstack/tripleo-ansible 3.3.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-ansible 4.1.0

This issue was fixed in the openstack/tripleo-ansible 4.1.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.