Bug 1886709
| Summary: | [External] RGW storageclass disappears after upgrade from OCS 4.5 to 4.6 | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Rachael <rgeorge> |
| Component: | ocs-operator | Assignee: | Jose A. Rivera <jarrpa> |
| Status: | CLOSED ERRATA | QA Contact: | Parikshith <pbyregow> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.6 | CC: | ebenahar, jarrpa, jijoy, jthottan, madam, mbukatov, muagarwa, nberry, ocs-bugs, pbyregow, shan, sostapov |
| Target Milestone: | --- | Keywords: | AutomationTriaged |
| Target Release: | OCS 4.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 4.6.0-148.ci | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-12-17 06:24:47 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Rachael
2020-10-09 07:55:41 UTC
Rook does not create SC, ocs-op does, moving to ocs-op :) (In reply to Mudit Agarwal from comment #4) > Related to https://bugzilla.redhat.com/show_bug.cgi?id=1873580? It is not. That is the RGW SC never being created at all. I'm not sure what is going on here. There is nothing in the ocs-operator code that would delete the SC without recreating it, and even there it would only be triggered if the StorageClusterInitialization was removed. Does this happen immediately after upgrade? Is it reliably reproducible? Sorry for the delay, I missed the notification.
Looks like the problem is this:
2020-10-14T17:26:59.952188571Z {"level":"error","ts":"2020-10-14T17:26:59.952Z","logger":"controller_storagecluster","msg":"failed to create needed StorageClasses","Request.Namespace":"openshift-storage","Request.Name":"ocs-external-storagecluster","error":"resourceVersion should not be set on objects to be created"}
Being caused by these lines:
https://github.com/openshift/ocs-operator/blob/master/pkg/controller/storagecluster/storageclasses.go#L69-L70
I'm not sure why we're doing this here, I'll have to investigate.
Based on today's bug triage, providing qa ack. QE team will validate this BZ during upgrade testing. I think this is just intermittent, nothing should have changed to resolve the issue. This PR includes the fix to fully resolve the issue: https://github.com/openshift/ocs-operator/pull/856 @pbyregow though this bug was reported in externam mode upgrade, it would be good if we can verify this BZ for upgrade in both Internal and external mode. Just so we can be sure that the storageclass doesn't disappear in any mode. thanks 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: Red Hat OpenShift Container Storage 4.6.0 security, bug fix, enhancement 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-2020:5605 Removing AutomationBackLog keyword. Presence of storageclasses are verified in automated upgrade test. |