Bug 2154319 - KubevirtHyperconvergedClusterOperatorCRModification alert in firing state during cnv upgrade (4.11.2->4.12.0)
Summary: KubevirtHyperconvergedClusterOperatorCRModification alert in firing state dur...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Installation
Version: 4.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.13.1
Assignee: Nahshon Unna-Tsameret
QA Contact: Debarati Basu-Nag
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-16 15:25 UTC by Debarati Basu-Nag
Modified: 2023-08-16 14:10 UTC (History)
2 users (show)

Fixed In Version: hco-bundle-registry-container-v4.13.1.rhel9-11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-16 14:09:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt hyperconverged-cluster-operator pull 2297 0 None Merged fix CRModification alert in upgrade 2023-03-29 09:37:57 UTC
Github kubevirt hyperconverged-cluster-operator pull 2305 0 None Merged [release-1.9] fix CRModification alert in upgrade 2023-05-02 12:06:11 UTC
Red Hat Issue Tracker CNV-23461 0 None None None 2022-12-16 15:39:55 UTC
Red Hat Product Errata RHSA-2023:4664 0 None None None 2023-08-16 14:10:13 UTC

Comment 2 Debarati Basu-Nag 2023-06-13 01:04:59 UTC 
We did not see this issue during 4.13.0->4.13.1 upgrade. Marking this as verified.
Comment 10 errata-xmlrpc 2023-08-16 14:09:56 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 (Important: OpenShift Virtualization 4.13.3 Images 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-2023:4664
Note You need to log in before you can comment on or make changes to this bug.