Bug 1826126
| Summary: | Operand form advanced fields within field/array field groups should render in the advanced configuration section | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jon Jackson <jonjacks> | ||||||
| Component: | Management Console | Assignee: | Jon Jackson <jonjacks> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.4 | CC: | aos-bugs, bpeterse, eparis, jokerman, spadgett, yanpzhan | ||||||
| Target Milestone: | --- | Keywords: | UpcomingSprint | ||||||
| Target Release: | 4.5.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
Cause: On the create operand form, [array] field groups were taking priority over advanced fields.
Consequence: If a field had both [array] field group and advanced descriptors, it would show up in the field group instead of the advanced fields section.
Fix: Adjust grouping logic to prioritize advanced descriptor over [array] field group descriptor.
Result: Fields with both [array] field group descriptor and advance descriptor now get grouped with advanced fields.
|
Story Points: | --- | ||||||
| Clone Of: | |||||||||
| : | 1831137 (view as bug list) | Environment: | |||||||
| Last Closed: | 2020-07-13 17:29:33 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: | 1831137 | ||||||||
| Attachments: |
|
||||||||
|
Description
Jon Jackson
2020-04-21 00:10:24 UTC
Resolved by https://github.com/openshift/console/pull/4944 Checked on ocp 4.5 cluster with payload 4.5.0-0.nightly-2020-05-07-144853. 1. Go to OperatorHub and install Portworx operator in a namespace 2. From the Portworx operator details page, create a Storage Cluster instance 3. In the 'Edit Form' view, check the 'Delete Strategy' field group, it's still near the top of the form, not in the 'Advanced Configuration' section at the bottom of the form. Pls refer to screenshots. Created attachment 1686371 [details]
AdvancedConfiguration
Created attachment 1686372 [details]
DeleteStrategy
Sorry, Yanping I should have clarified this one a bit more. In 4.5 we moved to a different implementation around field groups and advanced descriptors. The behavior that was reported as a 4.4 bug here is very similar to what we intentionally implemented in 4.5. You'll notice that there is actually a separate 'Advanced Configuration' section in the 'Delete Strategy' field group now. This is the expected behavior and is slightly different than the bug being reported here. Long story short, this bug has been fixed in 4.5 because there is a new behavior: Fields within a group that have an 'advanced' descriptor will be rendered in an 'Advanced Configuration' section within their parent field group instead of being moved into an Advanced Configuration section at the end of the entire form. 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 |