Bug 1979620

Summary: 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.
Product: OpenShift Container Platform Reporter: Jon Jackson <jonjacks>
Component: Management ConsoleAssignee: Yadan Pei <yapei>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.8CC: aos-bugs, jokerman
Target Milestone: ---   
Target Release: 4.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-18 17:38:02 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:
Description Flags
deeply nested field none

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