Bug 1666231
| Summary: | The content of CURRENT PAYLOAD is missing on Cluster Settings page | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | XiaochuanWang <xiaocwan> | ||||
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | XiaochuanWang <xiaocwan> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.1.0 | CC: | aos-bugs, jhadvig, jokerman, mmccomas, wsun | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.1.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: | 2019-02-18 14:02:56 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: |
|
||||||
Created attachment 1520705 [details]
CURRENT PAYLOAD field visibility
Was trying to reproduce the issue using:
[jhadvig@dhcp-0-147 frontend]$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.0.0-9 True False 1d Cluster version is 4.0.0-9
but I've seen the `CURRENT PAYLOAD` field
Fix merged to master Checked the PR, the value of CURRENT PAYLOAD is got from 'status.desired.payload', but literally it should get from 'status.history'. (Also the CURRENT VERSION is the same issue.) It'll be a risk when the current version is old and it doesn't match the desired version any more before upgrading. It's better to match the current status. Could you please to take a look into this, thanks! https://github.com/openshift/console/pull/1100 We now show "Desired Release Image" for `status.desired.image` and added a history table to make update status more clear. The version and state now is in the new table "Update History".
Also the content of "Desired Version" field (which is same as `oc get clusterversion`) could be found in one of the history versions.
the "Desired Release Image" is same as `oc get po -n openshift-cluster-version -o yaml |grep 'release-image'`
This is fixed.
Verified on OCP 4.0 as below detail:
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.0.0-0.alpha-2019-02-11-201342 True False 132m Cluster version is 4.0.0-0.alpha-2019-02-11-201342
$ oc get po -n openshift-cluster-version -o yaml |grep 'release-image'
- --release-image=registry.svc.ci.openshift.org/openshift/origin-release@sha256:5d87e5ecc0751494e7cc4cb428b409a76b7249189d5faec3fa09f685672d851e
|
Description of problem: Cluster admin check cluster settings page, here is a CURRENT PAYLOAD field but the content is missing. Version-Release number of selected component (if applicable): $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-01-15-010905 True False 11m Cluster version is 4.0.0-0.nightly-2019-01-15-010905 $ sudo podman inspect <console_image_id> "version": "v4.0.0" "release": "0.139.0.0", "io.openshift.source-repo-commit": "a62eaa43f2aab9a817a3fb66e1c8b88d5ef100da", How reproducible: Always Steps to Reproduce: 1. Cluster admin login and check cluster settings page Actual results: Here is a CURRENT PAYLOAD field but the content is missing. Expected results: Since the request can get the payload, it should display the correct content. Eg. Current payload: $oc get po -n openshift-cluster-version -o yaml |grep 'release-image' - --release-image=registry.svc.ci.openshift.org/ocp/release@sha256:bcfba3a40b8c30738475aa71743348df38df5a59820c7f6aaaea0644e830ed54 or $ oc get clusterversion -o yaml | grep -B2 payload Additional info: