Bug 1713263
Summary: | "--force" did not take effect when work with "--to-latest" when do upgrade with cli | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | liujia <jiajliu> |
Component: | Cluster Version Operator | Assignee: | Abhinav Dahiya <adahiya> |
Status: | CLOSED ERRATA | QA Contact: | liujia <jiajliu> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 4.1.0 | CC: | aos-bugs, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | 4.3.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: | 2020-01-23 11:04:11 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: |
Description
liujia
2019-05-23 09:44:33 UTC
Change the priority to "M" due to qe can not test "--to-latest" item with "--force". But "--force" is a must for prerelease nightly build. Fixes need to be merged to 4.2 first, we will open a backport BZ if this was needed for 4.1 too. Version: 4.3.0-0.nightly-2019-11-18-175710 # ./oc version Client Version: openshift-clients-4.3.0-201910250623-62-g1cfe371d # ./oc adm upgrade Cluster version is 4.3.0-0.nightly-2019-11-18-123403 Updates: VERSION IMAGE 4.3.0-0.nightly-2019-11-18-175710 registry.svc.ci.openshift.org/ocp/release@sha256:ca53dc5affac0979fc2fa5480dab43c4b77ee216221fbbcef99eea601d7ab785 4.3.0-0.nightly-2019-11-18-201425 registry.svc.ci.openshift.org/ocp/release@sha256:69d87efc70d108c2292c258d9d7108a4e432de74083a857a34ddd6531b654e92 # ./oc adm upgrade --to-latest=true --force Updating to latest version 4.3.0-0.nightly-2019-11-18-201425 # ./oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.3.0-0.nightly-2019-11-18-201425 True False 5m3s Cluster version is 4.3.0-0.nightly-2019-11-18-201425 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, 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/RHBA-2020:0062 |