Bug 1979620 - Applying an OLM descriptor to a deeply nested child property then doing the same for a parent property will cause the descriptor for the child to be removed.
Summary: Applying an OLM descriptor to a deeply nested child property then doing the s...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.9.0
Assignee: Yadan Pei
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-06 14:49 UTC by Jon Jackson
Modified: 2021-10-18 17:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:38:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
deeply nested field (82.65 KB, image/png)
2021-07-12 06:49 UTC, Yadan Pei
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 9417 0 None open Bug 1979620: Parent descriptors don't overwrite children 2021-07-06 16:10:37 UTC
Red Hat Product Errata RHSA-2021:3759 0 None Waiting on Customer Some SCAP rules result in a status of notchecked 2022-05-12 15:55:49 UTC

Description Jon Jackson 2021-07-06 14:49:49 UTC
Description of problem:
Applying an OLM descriptor to a deeply nested child property then doing the same for a parent property will cause the descriptor for the child to be removed.


Version-Release number of selected component (if applicable):
4.8

How reproducible:
Always

Steps to Reproduce:
1. In any namespace, create the CRD and CSV from https://gist.github.com/TheRealJon/3680c8a573bde88a974588e269230562
2. Navigate to Operators > Installed Operators > Mock Operator
3. Navigate to the Mock Resource operand creation form by clicking "Create instance" on the "Mock Resource" card


Actual results:
A "Deeply Nested" field is not displayed on the operand creation form

Expected results:
Near the bottom of the operand creation form should be a collapsed field group called "Deeply Nested". Expanding all of the nested fields reveals a nested structure like the following:

Deeply Nested
  Foo
    Bar
      Baz
        Foo Bar Baz Bat
          Limits
            CPU CORES  MEMORY  STORAGE
          Requests
            CPU CORES  MEMORY  STORAGE

Comment 2 Yadan Pei 2021-07-12 06:49:51 UTC
Created attachment 1800674 [details]
deeply nested field

1. In any namespace, create the CRD and CSV from https://gist.github.com/TheRealJon/3680c8a573bde88a974588e269230562
2. Navigate to Operators > Installed Operators > Mock Operator
3. Navigate to the Mock Resource operand creation form by clicking "Create instance" on the "Mock Resource" card, there is 'Deeply Nested' group, expand it and all nested fields will look like:

Deeply Nested
  Foo
    Bar
      Baz
        Foo Bar Baz Bat
          Limits
            CPU CORES  MEMORY  STORAGE
          Requests
            CPU CORES  MEMORY  STORAGE

Verified on 4.9.0-0.nightly-2021-07-10-081034

Comment 5 errata-xmlrpc 2021-10-18 17:38:02 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security 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-2021:3759


Note You need to log in before you can comment on or make changes to this bug.