Bug 1941367 - The containerruntimecontroller doesn't roll back to CR-1 if we delete CR-2
Summary: The containerruntimecontroller doesn't roll back to CR-1 if we delete CR-2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.7.z
Assignee: Urvashi Mohnani
QA Contact: MinLi
URL:
Whiteboard:
Depends On: 1825417
Blocks: 1926271
TreeView+ depends on / blocked
 
Reported: 2021-03-21 21:24 UTC by OpenShift BugZilla Robot
Modified: 2021-04-05 13:56 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-05 13:56:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 2476 0 None open [release-4.7] Bug 1941367: Make getting the suffix of an MC more robust 2021-03-22 13:41:04 UTC
Red Hat Product Errata RHSA-2021:1005 0 None None None 2021-04-05 13:56:54 UTC

Comment 2 MinLi 2021-03-25 11:20:30 UTC
verified on version: 4.7.0-0.nightly-2021-03-25-045200

Comment 5 errata-xmlrpc 2021-04-05 13:56:42 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 (Moderate: OpenShift Container Platform 4.7.5 security and bug fix update), 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/RHSA-2021:1005


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