Bug 1888898 - Undercloud upgrade failed. New certificate was generated despite the previous one was not expired
Summary: Undercloud upgrade failed. New certificate was generated despite the previou...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: z16
: 13.0 (Queens)
Assignee: Ade Lee
QA Contact: Jeremy Agee
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-16 07:44 UTC by Eduard Barrera
Modified: 2022-10-03 14:45 UTC (History)
10 users (show)

Fixed In Version: puppet-tripleo-8.5.1-22.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-16 10:58:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 784823 0 None MERGED Always update the local certmonger ca cert 2021-04-06 19:55:50 UTC
OpenStack gerrit 784980 0 None NEW Always update the local certmonger ca cert 2021-04-06 19:54:55 UTC
Red Hat Issue Tracker OSP-207 0 None None None 2022-10-03 14:45:21 UTC
Red Hat Product Errata RHBA-2021:2385 0 None None None 2021-06-16 10:59:26 UTC

Comment 10 Ade Lee 2021-04-06 22:09:35 UTC 
As seen in the patch to fix this, I think this problem occurs because an unless clause that prevents the renewed cert from being updated and trusted because
it checks if the current cert is not expired.

The fix removes this unless clause.
Comment 24 errata-xmlrpc 2021-06-16 10:58:54 UTC 
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 (Red Hat OpenStack Platform 13.0 bug fix and enhancement 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.

https://access.redhat.com/errata/RHBA-2021:2385
Note You need to log in before you can comment on or make changes to this bug.