Undercloud deployment reports false successfully deployment but deployment was already failed with RuntimeError: wait_api_port_ready: Max retries 30 reached
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Rabi Mishra |
Bug Description
In below update job, Undercloud deploy was already failed with already failed with "RuntimeError: wait_api_
~~~
2020-07-29 07:10:21.281908 | primary | TASK [undercloud-deploy : Copy stackrc created at the UC user $HOME to the working dir] ***
2020-07-29 07:10:21.282822 | primary | Wednesday 29 July 2020 07:10:21 +0000 (0:00:00.393) 0:43:17.054 ********
2020-07-29 07:10:24.978150 | primary | fatal: [undercloud]: FAILED! => {
2020-07-29 07:10:24.978334 | primary | "changed": false
2020-07-29 07:10:24.978441 | primary | }
2020-07-29 07:10:24.978618 | primary |
~~~
~~~
Exception: wait_api_
Traceback (most recent call last):
File "/usr/lib/
utils.
File "/usr/lib/
"wait_
RuntimeError: wait_api_
None
Not cleaning working directory /home/zuul/
Not cleaning ansible directory /home/zuul/
Install artifact is located at /home/zuul/
#######
Deployment successful!
#######
Writing the stack virtual update mark file /var/lib/
#######
~~~
tags: | added: queens-backport-potential train-backport-potential ussuri-backport-potential |
Fix proposed to branch: master /review. opendev. org/743744
Review: https:/