Using scenario001 multinode containers is failing on "Ceph deployment is not available anymore during overcloud deploy"

Bug #1986974 reported by Sofer Athlan-Guyot
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Triaged
Medium
Unassigned

Bug Description

Hi,

using reproducer I'm trying to deploy a multinode container setup with 3ctl and 1 comp.

Using the scenario001-multinode-containers.yaml fails with:

2022-08-18 13:14:19 | 2022-08-18 13:14:19.183 138776 ERROR openstack [-] Ceph deployment is not available anymore during overcloud deploy. If you want to deploy Ceph, please see "openstack overcloud ceph deploy --help" to deploy ceph before deploying the overcloud and then include the cephadm environment file.: tripleoclient.exceptions.InvalidConfiguration: Ceph deployment is not available anymore during overcloud deploy. If you want to deploy Ceph, please see "openstack overcloud ceph deploy --help" to deploy ceph before deploying the overcloud and then include the cephadm environment file.
2022-08-18 13:14:19 | 2022-08-18 13:14:19.184 138776 INFO osc_lib.shell [-] END return value: 1
2022-08-18 13:14:19 | + status_code=1

using scenario010 doesn't work neither and has the same error.

So only scenario007 and scenario000 are working as they don't use Ceph at all.

For reference the commit that introduced the new functionality is https://review.opendev.org/c/openstack/python-tripleoclient/+/839727

[0] full command for deployment is:

openstack overcloud deploy --stack overcloud \
  --override-ansible-cfg /home/zuul/custom_ansible.cfg \
  --templates /usr/share/openstack-tripleo-heat-templates \
  --libvirt-type qemu --timeout 90 --ntp-server 10.5.26.10,clock.redhat.com,clock2.redhat.com -e /home/zuul/cloud-names.yaml -e /home/zuul/hostnamemap.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/deployed-server-environment.yaml --overcloud-ssh-user zuul --deployed-server -e /home/zuul/containers-prepare-parameter.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml -e /usr/share/openstack-tripleo-heat-templates/ci/environments/scenario001-multinode-containers.yaml -e /home/zuul/overcloud_network_params.yaml -e /home/zuul/overcloud_storage_params.yaml -e /home/zuul/src/opendev.org/openstack/tripleo-ci/test-environments/worker-config.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/debug.yaml --overcloud-ssh-user zuul --validation-errors-nonfatal --roles-file /home/zuul/overcloud_roles.yaml -e /home/zuul/overcloud-topology-config.yaml -e /home/zuul/config-download.yaml --disable-validations --verbose --heat-type pod -e /home/zuul/overcloud-selinux-config.yaml --disable-protected-resource-types --baremetal-deployment \
  "$@" && status_code=0 || status_code=$?

Tags: ci
summary: - Using scenario007, scenario010 or scenario001 multinode containers is
- failing on "Ceph deployment is not available anymore during overcloud
- deploy"
+ Using scenario001 multinode containers is failing on "Ceph deployment is
+ not available anymore during overcloud deploy"
Revision history for this message
Sofer Athlan-Guyot (sofer-athlan-guyot) wrote :

I might be wrong but it seems that https://opendev.org/openstack/tripleo-quickstart-extras/src/branch/master/roles/standalone/tasks/ceph-install.yml should be ported to roles/multinodes and that scenarios should be updated with DeployedCeph.

Given that no public job is using this on a multinodes configuration I don't expect it to be done any time soon. I might give it a try, given some time.

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.