Bug 1847943 - aws-s3-provisioner is getting created as part of OCS
Summary: aws-s3-provisioner is getting created as part of OCS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: OCS 4.5.0
Assignee: Nimrod Becker
QA Contact: Filip Balák
URL:
Whiteboard:
Depends On: 1798571
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-17 12:02 UTC by Pratik Surve
Modified: 2023-09-14 06:02 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-15 10:17:44 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ocs-operator pull 594 0 None closed Bug 1798571: Release 4.5: owning ob and obc crds 2020-10-01 14:14:47 UTC
Red Hat Product Errata RHBA-2020:3754 0 None None None 2020-09-15 10:18:06 UTC

Comment 2 Yaniv Kaul 2020-06-17 13:45:49 UTC 
Severity is missing. But I also don't understand how the user is impacted.
Comment 5 Jose A. Rivera 2020-06-29 15:30:58 UTC 
Is this still seen as an issue now that we've changed to owning the CRDs?
Comment 6 Michael Adam 2020-06-30 11:56:50 UTC 
(In reply to Jose A. Rivera from comment #5)
> Is this still seen as an issue now that we've changed to owning the CRDs?

We reverted the owning. And afaict, we have not reverted it. Not in master and not in 4.5. We can talk about reverting back to owning now that the olm has been fixed.
Comment 7 Michael Adam 2020-06-30 21:53:41 UTC 
What is this awss3operator really?
I find https://github.com/yard-turkey/awss3operator .
It seems that this is yet another community(?) OLM entry (by the same author?) that would own the ob/obc crds.
Therefore, it might get pulled in if we require those CRDs.

So the owning PR should fix this.
I.e. essentially a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1798571 .

Assigining to Nimrod for further treatment.
And ACK-ing based on this interpretation.
Comment 8 Nimrod Becker 2020-07-01 06:07:42 UTC 
I agree, this should go away with changing the ownership model.
Comment 13 Filip Balák 2020-07-10 13:04:48 UTC 
$ oc get csv -A
NAMESPACE                              NAME                         DISPLAY                       VERSION        REPLACES   PHASE
openshift-operator-lifecycle-manager   packageserver                Package Server                0.15.1                    Succeeded
openshift-storage                      ocs-operator.v4.5.0-484.ci   OpenShift Container Storage   4.5.0-484.ci              Succeeded

$ oc get pods -A | grep aws-s3-provisioner
<nothing>

aws-s3-provisioner is not created during deployment of OCS 4.5.0-484.ci. --> VERIFIED
Comment 15 errata-xmlrpc 2020-09-15 10:17:44 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 OpenShift Container Storage 4.5.0 bug fix and 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/RHBA-2020:3754
Comment 16 Red Hat Bugzilla 2023-09-14 06:02:19 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.