Created attachment 1414796 [details]
Tracebacks from Mistral and deployment log
Description of problem:
Deployment of RHOS12 compat (undercloud RHOS13) failed with error overcloud could not be found, the openstack deployment failed before it created the overcloud stack.
default default] Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/mistral/actions/openstack/base.py", line 117, in run
result = method(**self._kwargs_for_run)
File "/usr/lib/python2.7/site-packages/swiftclient/client.py", line 1753, in head_container
return self._retry(None, head_container, container, headers=headers)
File "/usr/lib/python2.7/site-packages/swiftclient/client.py", line 1691, in _retry
File "/usr/lib/python2.7/site-packages/swiftclient/client.py", line 993, in head_container
resp, 'Container HEAD failed', body)
ClientException: Container HEAD failed: https://192.168.24.2:13808/v1/AUTH_70bc67243b844673a3a0bfc5e145ac82/overcloud-swift-rings 404 Not Found
: ClientException: Container HEAD failed: https://192.168.24.2:13808/v1/AUTH_70bc67243b844673a3a0bfc5e145ac82/overcloud-swift-rings 404 Not Found
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install undercloud RHOS13
2. copy THT compat, use that location on deployment
3. deploy overcloud RHOS13
overcloud deployment failed
no missing resources on deployment
please triage this we are going through the list and assigning round robin thanks (DFG:Upgrades triage call)
I reproduced the issue. I hope https://review.openstack.org/#/c/561898/ with backport to RSOP 12 will help to understand the details
We are testing this on stable/pike, this issue was already fixed but not backported, after the stable/pike backport is merged (https://review.openstack.org/#/c/570574/) I'll move it to POST, and after is tested we will move it to VERIFIED.
There is a typo in swift URL. Mathieu Bultel is working on it right now.
Im attaching the review on it, but to me, its not a blocker at all, its an automation tool (infrared?) issue.
I submitted a fix to the client to be more robust and to handle such mistake, but imho, we should not block this BZs to wait for this review to land.
Mathieu introduced the fix though the original issue was caused by // in URL. infrared has been fixed also so it doesn't contain // in overcloud_deploy.sh. Could you confirm/reject our actions fixed the issue.
Issue hasn't been reproduced the link seems to be fine and not broken
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.