Examples of Overcloud creation:

1)
openstack overcloud deploy --templates \
-e /usr/share/openstack-tripleo-heat-templates/environments/networkisolation.yaml \
-e ~/templates/network-environment.yaml \
-e ~/templates/storage-environment.yaml \
--control-scale 3 \
--compute-scale 3 \
--ceph-storage-scale 3 \
--control-flavor control \
--compute-flavor compute \
--ceph-storage-flavor ceph-storage \
--ntp-server pool.ntp.org \
--neutron-network-type vxlan \
--neutron-tunnel-types vxlan \

2)
openstack overcloud deploy ‐‐templates ~/templates \
> ‐‐control‐scale 1 ‐‐compute‐scale 1 \
> ‐‐ceph‐storage‐scale 1 \
> ‐‐control‐flavor control \
> ‐‐compute‐flavor compute \
> ‐‐ceph‐storage‐flavor ceph‐storage \
> ‐‐neutron‐tunnel‐types vxlan ‐‐neutron‐network‐type vxlan \
> ‐e ~/templates/compute‐extraconfig.yaml \
> ‐e ~/templates/environments/network‐isolation.yaml \
> ‐e ~/templates/environments/storage‐environment.yaml \
> ‐e ~/templates/network‐environment.yaml \
> ‐e ~/templates/pre‐config‐fix.yaml
Deploying templates in the directory /home/stack/templates/

3)

openstack overcloud deploy ‐‐templates ~/templates \

> ‐‐control‐scale 1 ‐‐compute‐scale 1 \
> ‐‐control‐flavor control ‐‐compute‐flavor compute \
> ‐‐neutron‐tunnel‐types vxlan ‐‐neutron‐network‐type vxlan \
> ‐e ~/templates/compute‐extraconfig.yaml \
> ‐e ~/templates/environments/network‐isolation.yaml \
> ‐e ~/templates/network‐environment.yaml \
> ‐e ~/templates/pre‐config‐fix.yaml
Deploying templates in the directory
Modifying the overcloud environment (add a new environment file):

1) openstack overcloud deploy --templates -e /usr/share/openstacktripleo-heat-

templates/environments/network-isolation.yaml -e ~/templates/network-environment.yaml -e
~/templates/storage-environment.yaml -e ~/templates/new-environment.yaml --control-scale
3 --compute-scale 3 --ceph-storage-scale 3 --control-flavor control -- compute-flavor compute --
ceph-storage-flavor ceph-storage --ntp-server pool.ntp.org --neutron-network-type vxlan --
neutron-tunnel-types vxlan

Monitor the Overcloud creation:

1) heat stack-list --show-nested

2) ssh heat-admin@I92.0.2.23 (IP of the server – control or compute)

Troubleshooting on Registration:

a) ironic node-port-list NODE-UUID (view MAC address)

b) ironic port-update [PORT UUID] replace address=[NEW MAC]
c) ironic node-update [NODE UUID] replace driver_info/ipmi_address=[NEW IPMI ADDRESS]
d) sudo journalctl -u openstack-ironic-inspector -u openstack-ironic-inspector-dnsmasq

Troubleshooting overcloud creation:

There are three layers where the deployment can fail:

A) Orchestration (heat and nova services)

B) Bare Metal Provisioning (ironic service)
C) Post-Deployment Configuration (Puppet)

a) heat stack-list
b) ironic node-list
 Here are some common issues that arise from the provisioning process:

Review the Provision State and Maintenance columns in the resulting table. Check for the following:

 An empty table, or fewer nodes than you expect

 Maintenance is set to True
 Provision State is set to manageable. This usually indicates an issue with the registration
or discovery processes. For example, if Maintenance sets itself to True automatically,
the nodes are usually using the wrong power management credentials.

If Provision State is available, then the problem occurred before bare metal deployment has even
started.

If Provision State is active and Power State is power on, the bare metal deployment has finished
successfully. This means that the problem occurred during the post-deployment configuration step.

If Provision State is wait call-back for a node, the bare metal provisioning process has not yet finished
for this node. Wait until this status changes, otherwise, connect to the virtual console of the failed node
and check the output.

If Provision State is error or deploy failed, then bare metal provisioning has failed for this node. Check
the bare metal node’s details:

ironic node-show [NODE UUID]

sudo journalctl -u openstack-ironic-conductor -u openstack-ironic-api (look for last_error field)

If you see wait timeout error and the node Power State is power on, connect to the virtual console of
the failed node and check the output.

c) heat resource-list overcloud (look for failed resource with status CREATE_FAILED).
heat resource-show overcloud [FAILED RESOURCE]

Check for any information in the resource_status_reason field that can help your diagnosis.

nova list or openstack server list

ssh heat-admin@192.0.2.14

sudo journalctl -u os-collect-config

In some cases, nova fails deploying the node in entirety. This situation would be indicated by a
failed OS::Heat::ResourceGroup for one of the Overcloud role types. Use nova to see the failure
in this case.
$ nova list
$ nova show [SERVER ID]
Troubleshooting the overcloud after creation:

heat stack-list --show-nested

List all stacks. The --show-nested displays all child stacks and their respective parent
stacks. This command helps identify the point where a stack failed.

heat resource-list overcloud

List all resources in the overcloud stack and their current states. This helps identify
which resource is causing failures in the stack. You can trace this resource failure to its
respective parameters and configuration in the heat template collection and the Puppet
modules.

heat event-list overcloud

List all events related to the overcloud stack in chronological order. This includes the
initiation, completion, and failure of all resources in the stack. This helps identify points of
resource failure.

systemctl status openstack-nova-compute.service

sudo journalctl -u openstack-nova-compute.service

/var/log/nova/nova-compute.log – primary log for compute nodes

Overcloud Configuration (Summary of Last Puppet Run) - /var/lib/puppet/state/

last_run_summary.yaml
Overcloud Configuration (Report from Last Puppet Run) - /var/lib/puppet/state/
last_run_report.yaml