Bug 1836447
Summary: | Operator update is failing due to missing replace field in Operator CSV | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
Component: | OLM | Assignee: | Alexander Greene <agreene> |
OLM sub component: | OLM | QA Contact: | Jian Zhang <jiazha> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | bsong, ecordell, krizza |
Version: | 4.3.z | Keywords: | UpcomingSprint |
Target Milestone: | --- | ||
Target Release: | 4.2.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: If an operator is being upgraded that provides a required API whose GVK has not changed since the previous version of the operator and the operator that depends on the API uses a skipRange instead of the Spec.Replaces field, OLM fails to generate the "upgraded CSV" with the correct replaces field. Specifically, OLM would:
1. Add the new operator to the generation, and marking the APIs it provides as "present".
2. Remove the old operator from the generation, marking the APIs it provides as "absent", despite being provided by the new version of the operator.
3. Attempt to resolve the "missing" apis, overwriting the the new version of the operator with a copy that does not have its Spec.Replaces field set.
Consequence: Certain operators would fail to upgrade to new versions.
Fix: OLM was updated to remove the old operator from the current generation before adding the new operator to the generation.
Result: The upgrade will succeed as expected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-01 16:08:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1827822 | ||
Bug Blocks: |
Comment 6
Jian Zhang
2020-06-22 02:29:32 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, 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-2020:2589 |