+++ This bug was initially created as a clone of Bug #1714584 +++ Description of problem: Recent changes for edge scenarios caused intended move of discovery from controller to bootstrap compute node, this change was also backported to RHOS 14 so now this task is triggered by deploy-identifier [1], meaning - with --skip-deploy-identifier flag used, discovery will not be triggered at all and as result causing failures in previously supported scenarios [2] [1] - https://github.com/openstack/tripleo-heat-templates/blob/master/deployment/nova/nova-compute-container-puppet.yaml#L667 [2] - https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/DFG-df-rfe-14-virsh-3cont_2comp_3ceph-skip-deploy-identifier-scaleup/24//artifact/tempest-results/tempest-results-smoke.1.html Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Documentation here https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/server_blacklist.html#skip-deploy-identifier
related to BZ1693563 where host discovery was moved to computes, specifically the bootstrap node to not run into a race when the discovery command gets triggered on multiple computes at the same time. To make sure we run at every overcloud deploy/scale/.. the deploy identifier gets passed to the step. if we skip the identifier the step does not run. A workaround would be to manually run the nova-manage discovery after the deploy run when --skip-deploy-identifier was used.
According to our records, this should be resolved by openstack-tripleo-heat-templates-9.3.1-0.20190513171752.el7ost. This build is available now.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3745