Scenario: 1. Deploy undercloud and prepare overcloud with TLS (3 controllers, 2 computes) 2. openstack overcloud roles generate Compute Controller 3. Copy-paste controller role 3 times, change 1st to Controller0 and the hostname to %stackname%-controller0-%index. Remove "primary" from second and third - name: Controller0 description: | First Controller role CountDefault: 1 tags: - primary - controller HostnameFormatDefault: '%stackname%-controller0-%index%' - name: Controller2 description: | Third Controller role tags: - controller HostnameFormatDefault: '%stackname%-controller2-%index%' 4. Change predictable-ips.yaml from one list for all the controllers to 3 lists: Controller0IPs: external: - 10.0.0.180 internal_api: - 172.17.1.160 storage: - 172.17.3.160 storage_mgmt: - 172.17.4.160 tenant: - 172.17.2.160 Controller1IPs: external: - 10.0.0.181 internal_api: - 172.17.1.161 storage: - 172.17.3.161 storage_mgmt: - 172.17.4.161 tenant: - 172.17.2.161 Controller2IPs: external: - 10.0.0.182 internal_api: - 172.17.1.162 storage: - 172.17.3.162 storage_mgmt: - 172.17.4.162 tenant: - 172.17.2.162 5. network-environment.yaml: resource_registry: OS::TripleO::Controller0::Net::SoftwareConfig: three-nics-vlans//controller.yaml OS::TripleO::Controller1::Net::SoftwareConfig: three-nics-vlans//controller.yaml OS::TripleO::Controller2::Net::SoftwareConfig: three-nics-vlans//controller.yaml 6. nodes_data.yaml: parameter_defaults: Controller0Count: 1 Controller1Count: 1 Controller2Count: 1 Overcloud deployment failed: 2019-06-20 09:35:03Z [overcloud.AllNodesDeploySteps.Controller1Deployment_Step3.0]: CREATE_FAILED Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2 2019-06-20 09:35:03Z [overcloud.AllNodesDeploySteps.Controller1Deployment_Step3]: CREATE_FAILED Resource CREATE failed: Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2 2019-06-20 09:35:04Z [overcloud.AllNodesDeploySteps.Controller1Deployment_Step3]: CREATE_FAILED Error: resources.Controller1Deployment_Step3.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2 2019-06-20 09:35:04Z [overcloud.AllNodesDeploySteps]: CREATE_FAILED Resource CREATE failed: Error: resources.Controller1Deployment_Step3.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2 2019-06-20 09:35:05Z [overcloud.AllNodesDeploySteps]: CREATE_FAILED Error: resources.AllNodesDeploySteps.resources.Controller1Deployment_Step3.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2 2019-06-20 09:35:05Z [overcloud]: CREATE_FAILED Resource CREATE failed: Error: resources.AllNodesDeploySteps.resources.Controller1Deployment_Step3.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2 Stack overcloud CREATE_FAILED overcloud.AllNodesDeploySteps.Controller1Deployment_Step3.0: resource_type: OS::Heat::StructuredDeployment physical_resource_id: 452e55a9-bb84-483d-bd3b-0a04b670e4e1 status: CREATE_FAILED status_reason: | Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2 deploy_stdout: | ... "+ exit 6", "2019-06-20 09:35:01,079 INFO: 103562 -- Finished processing puppet configs for keystone_init_tasks", "2019-06-20 09:35:01,080 ERROR: 103555 -- ERROR configuring keystone_init_tasks" ] } to retry, use: --limit @/var/lib/heat-config/heat-config-ansible/06f9ac00-b5ca-4034-a3c9-3b6408424264_playbook.retry PLAY RECAP ********************************************************************* localhost : ok=10 changed=3 unreachable=0 failed=1 (truncated, view all with --long) deploy_stderr: | Heat Stack create failed. Heat Stack create failed.
Build available.
VERIFIED puppet-tripleo-8.4.1-14.el7ost.noarch
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:1738