Bug 2028505 - Overcloud update fails on the first controller
Summary: Overcloud update fails on the first controller
Keywords:
Status: CLOSED DUPLICATE of bug 2015325
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 16.1 (Train)
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Damien Ciabrini
QA Contact: pkomarov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-02 14:24 UTC by Eric Nothen
Modified: 2022-06-29 12:08 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-29 12:08:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-11153 0 None None None 2021-12-02 15:23:40 UTC

Description Eric Nothen 2021-12-02 14:24:11 UTC
Description of problem:
An overcloud update fails on the first controller at the task "Wait for containers to start for step 2 using paunch". Times out after 650 retries (rougly 30 minutes).
When the overcloud update is retried without any change done on the controller, it completes without the error. Afterwards, the overcloud is fully available. 


Version-Release number of selected component (if applicable):
16.1.4 to 16.1.6

How reproducible:
Customer ran into this issue on the first 2 clusters they updated. I have not been able to reproduce yet.

Steps to Reproduce:
1.
2.
3.

Actual results:
Overcloud update fails on the first controller that is updated.


Expected results:
Overcloud update completes on the first try without error.


Additional info:
Attaching case with sosreport from the controller and output of ansible job.

Comment 7 Eric Nothen 2021-12-10 08:51:15 UTC
Now that BZ#2015325 is resolved, I'll ask my customer if it's possible to test the update from 16.1.4 to 16.1.7, and if it works well we can assume this bug is a duplicate of the other and close it.

Comment 9 Eric Nothen 2022-02-09 18:08:21 UTC
Customer confirmed on the attached case that the workaround for this issue is the same detailed on BZ#2015325 (removing mariadb-server in advance), so this BZ can be closed as duplicate.

Comment 10 Luca Miccini 2022-06-29 12:08:17 UTC

*** This bug has been marked as a duplicate of bug 2015325 ***


Note You need to log in before you can comment on or make changes to this bug.