-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.18, 4.19
-
None
-
False
-
the newly introduced (OCPBUGS-8259 fix) ability to apply force to multi-arch transition by means of oc adm upgrade --to-multi-arch --force is currently errors out if previously applied without force, even in situations where previous non-forced request has been blocked, for example by unsigned payload
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-2024-11-08-135543
How reproducible:
100%
Steps to Reproduce:
1. with cvo being expected to block its own version without force, such as being an unsigned nightly, apply to-multi-arch without force
$ oc adm upgrade --to-multi-arch
2. observe ReleaseAccepted=False and Progressing=False in cvo status
3. reapply to-multi-arch with force
$ oc adm upgrade --to-multi-arch --force
Actual results:
oc client blocks the command as already requested, despite cvo being unable to fulfill the request ❯ oc adm upgrade --to-multi-arch --force error: info: Update to multi cluster architecture has already been requested
Expected results:
oc detects the unforced update being rejected, and accepts the forced command
Additional info:
oc adm upgrade --clear followed by oc adm upgrade --to-multi-arch --force works as a workaround
- relates to
-
-
- Verified
-
