Bug 1755699
| Summary: | "Add Capacity" workflow for OCS breaks Portworx Operator | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | umanga <uchapaga> | ||||
| Component: | Console Storage Plugin | Assignee: | Kanika Murarka <kmurarka> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Raz Tamir <ratamir> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 4.2.0 | CC: | anbehl, aos-bugs, kmurarka, nthomas, spadgett | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1755980 (view as bug list) | Environment: | |||||
| Last Closed: | 2020-05-13 21:25:21 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1755980 | ||||||
| Attachments: |
|
||||||
@Sam, Please review and I think this needs to get into 4.2 We will send a patch soon 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:0062 |
Created attachment 1619356 [details] Screenshot from Portworx for "Add Capacity" Description of problem: When I install portworx operator and ocs operator, the expand workflow meant only for ocs operator is available even for portworx due to same "StorageCluster" Kind used by CRD of both operators. This lets Portworx users to trigger Expansion but it fails with an error saying "OCS StorageCluster is not available." Version-Release number of selected component (if applicable): OCS 4.2 - latest OCP 4.2 - latest nightly builds How reproducible: Steps to Reproduce: 1. Install OCS Operator 2. Install Portworx Operator 3. Create StorageCluster for Portworx 4. In the instance listing page, "Add Capacity" from the kebab menu Actual results: "Add Capacity" is available for Portworx. Portworx StorageClass can be used to expand Portworx. Expected results: "Add Capacity" should not be available for Portworx. Additional info: