Ocata -> Pike overcloud upgrade fails because paunch is not installed during upgrade:
Upgrade is failing during major-upgrade-composable-steps-docker.yaml because python-paunch package is not installed:
(undercloud) [stack@undercloud-0 ~]$ openstack stack failures list overcloud --long
overcloud.AllNodesDeploySteps.AllNodesPostUpgradeSteps.ControllerDeployment_Step1.0:
resource_type: OS::Heat::StructuredDeployment
physical_resource_id: 4eefc9ca-bf2a-42fb-a1d1-21cd794d360f
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: |
PLAY [localhost] ***************************************************************
TASK [setup] *******************************************************************
ok: [localhost]
TASK [Write the config_step hieradata] *****************************************
ok: [localhost]
TASK [Run puppet host configuration for step 1] ********************************
ok: [localhost]
TASK [Run docker-puppet tasks (generate config)] *******************************
ok: [localhost]
TASK [Check if /var/lib/hashed-tripleo-config/docker-container-startup-config-step_1.json exists] ***
ok: [localhost]
TASK [Start containers for step 1] *********************************************
fatal: [localhost]: FAILED! => {"changed": false, "cmd": "paunch --debug apply --file /var/lib/tripleo-config/hashed-docker-container-startup-config-step_1.json --config-id tripleo_step1 --managed-by tripleo-Controller", "failed": true, "msg": "[Errno 2] No such file or directory", "rc": 2}
to retry, use: --limit @/var/lib/heat-config/heat-config-ansible/3fd8749f-044b-45ab-82c0-e12f0b1ed7b5_playbook.retry
PLAY RECAP *********************************************************************
localhost : ok=5 changed=0 unreachable=0 failed=1
deploy_stderr: |
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
Valid example: CONFIRMED FOR: FUTURE