Bug 1835005
Summary: | Portworx Operator - Incorrect mapped "UpdateStrategy" widget on Operand Creation view. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | tony.wu | ||||||
Component: | Management Console | Assignee: | Jon Jackson <jonjacks> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 4.5 | CC: | aos-bugs, jokerman, jonjacks, xiaocwan | ||||||
Target Milestone: | --- | ||||||||
Target Release: | 4.5.0 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | No Doc Update | |||||||
Doc Text: |
Manifested, discovered, and fixed before release.
|
Story Points: | --- | ||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2020-07-13 17:37:59 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: | |||||||||
Attachments: |
|
Created attachment 1691674 [details]
Verification screenshot
Now the admin could specify the deployment strategy when creating instance. Please refer to the screenshot in attachment. Verified on 4.5.0-0.nightly-2020-05-24-191212 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:2409 |
Created attachment 1687826 [details] [portworx-operator]_create_StorageCluster_form Description of problem: The current "UpdateStrategy" specDescriptor (and UI widget) is for "Deployment" object; however, the Operand of Portworx Operator, "StorageCluster", is managing a "DaemonSet" object. Console shouldn't auto-apply the existing "UpdateStrategy" widget on Creation Operand view since there could be cases that the CR is managing a "DaemonSet" object, like the Portworx case. Version-Release number of selected component (if applicable): OCP 4.5 How reproducible: 100% Steps to Reproduce: 1. Go to 'OperatorHub' view and install "Portworx Operator" to a Namespace 2. Go to 'Installed Operatos' view and create "StorageCluster" 3. Scroll toward the bottom of the "Create StorageCluster" view Actual results: "UpdateStrategy" widget is auto-applied on the "Create StorageCluster" view. Expected results: Console doesn't auto apply "UpdateStrategy" widget but requires Operator authors to explicitly map it in the CSV file. Additional info: