-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.14
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Install 4.14.0-rc.0 and patch below graph:
oc414 patch clusterversion/version --patch '{"spec":{"upstream":"https://raw.githubusercontent.com/JianLi-RH/ota/main/OCP-38474.json"}}' --type=merge
{
"nodes": [
{
"version": "4.14.0-rc.0",
"payload": "example.com@sha256:1d2cc38cbd94c532dc822ff793f46b23a93b76b400f7d92b13c1e1da042c88fe",
"metadata": {
"io.openshift.upgrades.graph.release.channels": "channel-a,channel-b,stable-4.14"
}
},
{
"version": "4.14.0-rc.1",
"payload": "quay.io/openshift-release-dev/ocp-release@sha256:e3ba11bd1e5e8ea5a0b36a75791c90f29afb0fdbe4125be4e48f69c76a5c47a0",
"metadata": {
"io.openshift.upgrades.graph.release.channels": "channel-a,channel-b,stable-4.14"
}
}
],
"edges": [
[0,1]
]
}
Then upgrade to 4.14.0-rc.1:
oc414 adm upgrade --to-image example.com@sha256:e3ba11bd1e5e8ea5a0b36a75791c90f29afb0fdbe4125be4e48f69c76a5c47a0
Upgrade should successfully but actually not, upgrade process should be able to recognize example.com as quay.io/openshift-release-dev/ocp-release
Version-Release number of selected component (if applicable):
4.14.0-rc.0
How reproducible:
Always
Steps to Reproduce:
1. install 4.14.0-rc.0
2. oc patch clusterversion/version --patch '{"spec":{"upstream":"https://raw.githubusercontent.com/JianLi-RH/ota/main/OCP-38474.json"}}' --type=merge
3. Wait some minutes, check desired:
oc414 get -o json clusterversion version | jq .status.desired
4. Check recommended:
[root@localhost ~]# oc414 adm upgrade
Cluster version is 4.14.0-rc.0
Upstream: https://raw.githubusercontent.com/JianLi-RH/ota/main/OCP-38474.json
Channel: stable-4.14 (available channels: channel-a, channel-b, stable-4.14)
Recommended updates:
VERSION IMAGE
4.14.0-rc.1 quay.io/openshift-release-dev/ocp-release@sha256:e3ba11bd1e5e8ea5a0b36a75791c90f29afb0fdbe4125be4e48f69c76a5c47a0
5. Upgrade:
[root@localhost ~]# oc414 adm upgrade --to-image example.com@sha256:e3ba11bd1e5e8ea5a0b36a75791c90f29afb0fdbe4125be4e48f69c76a5c47a0
Requested update to 4.14.0-rc.1
Actual results:
Upgrade not started: [root@localhost ~]# oc adm upgrade Cluster version is 4.14.0-rc.0 ReleaseAccepted=False Reason: RetrievePayload Message: Retrieving payload failed version="4.14.0-rc.1" image="example.com@sha256:e3ba11bd1e5e8ea5a0b36a75791c90f29afb0fdbe4125be4e48f69c76a5c47a0" failure=Unable to download and prepare the update: deadline exceeded, reason: "DeadlineExceeded", message: "Job was active longer than specified deadline" Upstream: https://raw.githubusercontent.com/JianLi-RH/ota/main/OCP-38474.json Channel: stable-4.14 (available channels: channel-a, channel-b, stable-4.14) Recommended updates: VERSION IMAGE 4.14.0-rc.1 quay.io/openshift-release-dev/ocp-release@sha256:e3ba11bd1e5e8ea5a0b36a75791c90f29afb0fdbe4125be4e48f69c76a5c47a0 [root@localhost ~]#
Expected results:
1. Upgrade should successful even we use an invalid payload domain name, here is example.com 2. The payload domain name in Recommended updates should be example.com even it is not in the graph json.
Additional info:
