Failure when deploying the overcloud on a predeployed server

Bug #1742237 reported by emanoel on 2018-01-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

When following the steps documented here the overcloud deployment gets stuck eventually timing out during stack creation.

Steps to reproduce
* Deployed the undercloud using the steps here
* The repo used for the undercloud was current-tripleo-dev
* Followed the steps here to deploy the overcloud. All the documented steps passed except for the final overcloud deploy command (see logs and config used below)
* The VM used for the undercloud was a Centos 7 and all the needed packages were installed as documented above.

Expected result
Overcloud deployment completes successfully and the overcloud services are present in the controller node as containers.

Actual result
Overcloud deployment is stuck at this step `[overcloud.AllNodesDeploySteps.ControllerDeployedServerDeployment_Step1.0]: CREATE_IN_PROGRESS state change`

Logs & Configs

Overcloud deploy command and output:
os-collect-config log:

Changed in tripleo:
milestone: none → rocky-1
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

It seems that
OS::TripleO::DeployedServer::ControlPlanePort: ../deployed-server/deployed-neutron-port.yaml

needs to have an absolute path instead?

Revision history for this message
emanoel (emanoelxavier) wrote :

Could be. After changing that, deleting the existing failed overcloud stack and retrying the deployment i got a different error. The overcloud deploy command now executed with the --debug option produced the output

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

The failed software deployment's resources.NetworkDeployment should be analyzed then,
perhaps the commands like:

openstack software deployment show <id>
openstack stack resource list --nested-depth 5 <stack>
openstack --os-cloud rdo-cloud stack resource show <stack> <resource>

though, I'm not too good with navigating nested heat entities :/

Revision history for this message
emanoel (emanoelxavier) wrote :

I did some steps similar to above, looks like the issue may be related with discovering or pinging the $METADATA_IP ?

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

It seems that you should double-check the EC2MetadataIp value that Heat takes from quickstart inventory vars, see network_environment_args and use_resource_registry_nic_configs that enables the former. If you configure networking via custom tht templates, look there instead.

Revision history for this message
emanoel (emanoelxavier) wrote :

The value I currently have for EC2MetadaIP is the undercloud API IP. From the overcloud VM:
{"versions": [{"status": "CURRENT", "id": "v1.0", "links": [{"href": "", "rel": curl
<html><h1>Not Found</h1><p>The resource could not be found.</p></html>[root@overcloud ~]

There is a route to that IP from the overcloud VM, and the behavior above is the expected one according to The configuration I am currently using is based on Should the value of the EC2MetadataIp be something else?

Revision history for this message
Sanjay Upadhyay (saneax) wrote :

EC2MetadataIP should be your undercloud ip. The variable might be correctly set. However the failure is at the NetworkConfig stage. The error could be related to any other network config parameter issues. We might need to see if the packets for ping are being received on undercloud node. Mostly this could be the network setup.

Revision history for this message
emanoel (emanoelxavier) wrote :

Is the ping happening from inside of one of the containers deployed in the overcloud guest VM? I did the steps here (ping, curl the undercloud IP and everything worked as mentioned above. See traces and ip config here

Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Changed in tripleo:
milestone: stein-2 → stein-3
Changed in tripleo:
milestone: stein-3 → train-1
Changed in tripleo:
milestone: train-1 → train-2
Changed in tripleo:
milestone: train-2 → train-3
Changed in tripleo:
milestone: train-3 → ussuri-1
Changed in tripleo:
milestone: ussuri-1 → ussuri-2
wes hayutin (weshayutin) on 2020-02-10
Changed in tripleo:
milestone: ussuri-2 → ussuri-3
wes hayutin (weshayutin) on 2020-04-13
Changed in tripleo:
milestone: ussuri-3 → ussuri-rc3
wes hayutin (weshayutin) on 2020-05-11
Changed in tripleo:
status: Triaged → Incomplete
wes hayutin (weshayutin) on 2020-05-26
Changed in tripleo:
milestone: ussuri-rc3 → victoria-1
Changed in tripleo:
milestone: victoria-1 → victoria-3
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers