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
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
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