Bug 1876701 - podCount specDescriptor change doesn't take effect on operand details page
Summary: podCount specDescriptor change doesn't take effect on operand details page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 4.7.0
Assignee: Jon Jackson
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-08 01:51 UTC by Yadan Pei
Modified: 2021-02-24 15:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Patch paths on some API calls were incorrect. Consequence: Some editable spec descriptor fields were not updating resource properties as expected. Fix: Update the logic for building a patch path from a descriptor to ensure it is correctly formatted. Result: Editable spec descriptor fields now work as expected.
Clone Of:
Environment:
Last Closed: 2021-02-24 15:17:26 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 6824 0 None closed Bug 1876701: Fix some spec descriptor widgets inline edit behavior 2021-02-17 20:50:23 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:17:46 UTC

Description Yadan Pei 2020-09-08 01:51:32 UTC 
Description of problem:
update podCount size on operand details page doesn't take effect 

Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-09-05-015624

How reproducible:
Always

Steps to Reproduce:
1. Install ArgoCD Operator 0.0.12 and check ArgoCD specDescriptors
# oc get csv argocd-operator.v0.0.12  -n yapei461 -o json | jq '.spec.customresourcedefinitions.owned[3].specDescriptors'  | grep prometheus -A 3
    "path": "prometheus.enabled",
    "x-descriptors": [
      "urn:alm:descriptor:com.tectonic.ui:fieldGroup:Prometheus",
      "urn:alm:descriptor:com.tectonic.ui:booleanSwitch"
--
    "path": "prometheus.host",
    "x-descriptors": [
      "urn:alm:descriptor:com.tectonic.ui:fieldGroup:Prometheus",
      "urn:alm:descriptor:com.tectonic.ui:text"
--
    "path": "prometheus.ingress",
    "x-descriptors": [
      "urn:alm:descriptor:com.tectonic.ui:fieldGroup:Prometheus",
      "urn:alm:descriptor:com.tectonic.ui:booleanSwitch"
--
    "path": "prometheus.route",
    "x-descriptors": [
      "urn:alm:descriptor:com.tectonic.ui:fieldGroup:Prometheus",
      "urn:alm:descriptor:com.tectonic.ui:booleanSwitch"
--
    "path": "prometheus.size",
    "x-descriptors": [
      "urn:alm:descriptor:com.tectonic.ui:fieldGroup:Prometheus",
      "urn:alm:descriptor:com.tectonic.ui:podCount"

2. Create ArgoCD instance with Form View, set Prometheus.Size with 2
3. Check spec fields on operand details page
4. Update the Prometheus.size to 1 by clicking edit pencil button -> Update Size on operand details page
5. Check Prometheu.size field again

Actual results:
5. The size is still 2

Expected results:
5. size should be updated to 1 successfully

Additional info:
Comment 1 Jakub Hadvig 2020-09-08 11:19:09 UTC 
@jon please evaluate if this needs to be moved to the DevConsole team.
Thanks!
Comment 2 Jon Jackson 2020-09-11 21:04:20 UTC 
I haven't had a chance to dig into this yet, will address in upcoming sprint.
Comment 3 Jon Jackson 2020-10-02 13:36:51 UTC 
Next in my queue.
Comment 5 Yanping Zhang 2020-10-13 09:23:09 UTC 
Checked on ocp 4.7 with payload 4.7.0-0.ci-2020-10-12-222453.
1.Install "ArgoCD Operator" from OperatorHub.
2.Create ArgoCD instance with Form View, set Prometheus.Size with 2.
3.Update Prometheus size to 1 by editing pencil button -> Update Size on operand details page, could update successfully, it shows 1 now.
The bug is fixed.
Comment 8 errata-xmlrpc 2021-02-24 15:17:26 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.7.0 security, bug fix, and enhancement 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-2020:5633
Note You need to log in before you can comment on or make changes to this bug.