Description of problem: Cephadm fails to bootstrap the controller during overcloud deployment It's basically the same as documented here https://access.redhat.com/articles/6850761 , during installation. I think for openstack environment where ceph is director deployed rgw will be located on 1 cluster itself so this can be bypassed through introducing --yes-i-know in the cephadm bootstrap playbook. /usr/share/ansible/roles/tripleo_cephadm/tasks/bootstrap.yaml - name: Bootstrap Ceph if there are no running Ceph Daemons block: - name: Run cephadm bootstrap shell: | {{ tripleo_cephadm_bin }} \ {% if not tripleo_cephadm_default_container %}--image {{ tripleo_cephadm_container_ns + '/' + tripleo_cephadm_container_image + ':' + tripleo_cephadm_container_tag }} \{% endif %} bootstrap \ --skip-firewalld \ --ssh-private-key /home/{{ tripleo_cephadm_ssh_user }}/.ssh/id_rsa \ --ssh-public-key /home/{{ tripleo_cephadm_ssh_user }}/.ssh/id_rsa.pub \ --ssh-user {{ tripleo_cephadm_ssh_user }} \ --allow-fqdn-hostname \ --output-keyring {{ tripleo_cephadm_admin_keyring }} \ --output-config {{ tripleo_cephadm_conf }} \ --fsid {{ tripleo_cephadm_fsid }} \ {% if tripleo_cephadm_registry_url|length > 0 %}--registry-url {{ tripleo_cephadm_registry_url }} \{% endif %} {% if tripleo_cephadm_registry_username|length > 0 %}--registry-username {{ tripleo_cephadm_registry_username }} \{% endif %} {% if tripleo_cephadm_registry_password|length > 0 %}--registry-password {{ tripleo_cephadm_registry_password }} \{% endif %} {% if tripleo_cephadm_spec_on_bootstrap %}--apply-spec {{ tripleo_cephadm_spec }} \{% endif %} {% if tripleo_cephadm_assimilate_conf_stat.stat.exists %}--config {{ tripleo_cephadm_assimilate_conf }} \{% endif %} {% if tripleo_cephadm_single_host_defaults %}--single-host-defaults \{% endif %} --skip-monitoring-stack --skip-dashboard \ --mon-ip {{ tripleo_cephadm_first_mon_ip }} \ --yes-i-know << Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Isn't this a duplicate of bug 2072665 ?
*** This bug has been marked as a duplicate of bug 2072665 ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days