-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.6.0
-
None
-
No
-
False
-
Description of problem:
created a 4.6.62 cluster with profile 32_Disconnected UPI on GCP with RHCOS FIPS on & private cluster & Etcd Encryption on&enabled worker machineset, then upgraded it to 4.6.0-0.nightly-2023-07-10-071314, but failed. show version and can see
"could not download the update" log
Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2023-07-10-071314
How reproducible:
just tested for one time, will try to reproduce it later
Steps to Reproduce:
1.
% oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.6.62 True False 75m Cluster version is 4.6.62
2. try to update the cluster to 4.6.0-0.nightly-2023-07-10-071314 by the oc adm upgrade command
% oc patch clusterversion/version --patch '{"spec":{"upstream":"https://amd64.ocp.releases.ci.openshift.org/graph"}}' --type=merge
clusterversion.config.openshift.io/version patched
%
% oc adm upgrade --to-image=registry.ci.openshift.org/ocp/release:4.6.0-0.nightly-2023-07-10-071314 --allow-explicit-upgrade=true --force
warning: Using by-tag pull specs is dangerous, and while we still allow it in combination with --force for backward compatibility, it would be much safer to pass a by-digest pull spec instead
warning: The requested upgrade image is not one of the available updates.You have used --allow-explicit-upgrade for the update to proceed anyway
warning: --force overrides cluster verification of your supplied release image and waives any update precondition failures.
Updating to release image registry.ci.openshift.org/ocp/release:4.6.0-0.nightly-2023-07-10-071314
%
3. show the clusterversion from time to time
% oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.6.62 True True 36m Working towards registry.ci.openshift.org/ocp/release:4.6.0-0.nightly-2023-07-10-071314: downloading update
%
% oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.6.62 True True 64m Unable to apply registry.ci.openshift.org/ocp/release:4.6.0-0.nightly-2023-07-10-071314: could not download the update
%
4. more than 3 hours had passed, the cluster wasn't upgraded successfully, "could not download the update" could still be seen
% oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.6.62 True True 3h15m Working towards registry.ci.openshift.org/ocp/release:4.6.0-0.nightly-2023-07-10-071314: downloading update
%
% oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.6.62 True True 3h26m Unable to apply registry.ci.openshift.org/ocp/release:4.6.0-0.nightly-2023-07-10-071314: could not download the update
%
Actual results:
the upgrade was always in progress due to could not download the update
Expected results:
upgraded to 4.6.0-0.nightly-2023-07-10-071314 successfully
Additional info: