Bug 2217473

Summary: [FFU] Create containers managed by Podman in Overcloud FFU
Product: Red Hat OpenStack Reporter: Ricardo Diaz <rdiazcam>
Component: rhosp-releaseAssignee: Jason Joyce <jjoyce>
Status: CLOSED NOTABUG QA Contact: Arik Chernetsky <achernet>
Severity: high Docs Contact:
Priority: unspecified    
Version: 17.1 (Wallaby)   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-26 15:36:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ricardo Diaz 2023-06-26 11:37:04 UTC
Description of problem:
When running the FFU 17.1 CI job found this error:
~~~
 (undercloud) [stack@undercloud-0 ~]$ grep -i fatal overcloud_upgrade_run-computehwoffload-0,computehwoffload-1,controller-0,controller-1,controller-2,undercloud.log 
2023-06-26 08:16:36 | [WARNING]: any_errors_fatal only stops any future tasks running on the host
2023-06-26 08:56:44 | 2023-06-26 08:56:44.524230 | 52540040-c122-dcb6-bb30-00000000ee90 |      FATAL | Check password of Keystone user | undercloud | error={"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
2023-06-26 08:59:36 | 2023-06-26 08:59:36.405921 | 52540040-c122-dcb6-bb30-00000000fab9 |      FATAL | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_4 | controller-1 | error={"changed": false, "msg": "Failed containers: neutron_metadata_agent"}
~~~

Version-Release number of selected component (if applicable):
17.1 FFU


How reproducible:
100%

Steps to Reproduce:
1.Run Overcloud FFU stage
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Ricardo Diaz 2023-06-26 15:36:01 UTC
The problem was not reproduced in a second execution so we can consider it was a temporary issue.