Bug 1706245
| Summary: | upgrade won't allow user to run upgrade again if a user forgot to use --force=true the first time. | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Peter Ruan <pruan> |
| Component: | Master | Assignee: | Mike Dame <mdame> |
| Status: | CLOSED ERRATA | QA Contact: | Peter Ruan <pruan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.0 | CC: | aos-bugs, bleanhar, gblomqui, jokerman, mmccomas, wsun, xxia, yapei |
| 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-06-19 06:45:34 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
Peter Ruan
2019-05-03 21:30:43 UTC
I found that I was able to work around this by running `oc adm upgrade --clear` after the first attempt, then trying again with --force. Regardless, I think it makes sense that --force should push through an update even if the image matches, so I opened a PR for this: https://github.com/openshift/origin/pull/22786 PR merged, setting to on_qa Peter, could you continue checking the bug (comment 2)? As to 4.2, currently I didn't see 4.2 build. Not sure if https://console.svc.ci.openshift.org/k8s/ns/ocp/imagestreams could help. I see there is e.g. https://console.svc.ci.openshift.org/k8s/ns/ocp/imagestreams/4.2-2019-05-16-065650 which displays registry.svc.ci.openshift.org/ocp/4.2-2019-05-16-065650 . Thanks. Checked the commit message and below git log, it means the fix landed in 4.1 too. Peter said he will verify it later. [xxia@xxia-pc local_ose_repo]$ git log --date=local upstream/enterprise-4.1 --pretty="%h %an %cd - %s" | grep "Allow oc adm upgrade with --force even" 56d908bd9d Mike Dame Tue May 7 04:39:52 2019 - Allow oc adm upgrade with --force even if versions match verified with
Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.0-201905191700+82e7b55-dirty", GitCommit:"82e7b55", GitTreeState:"dirty", BuildDate:"2019-05-20T00:17:47Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+838b4fa", GitCommit:"838b4fa", GitTreeState:"clean", BuildDate:"2019-05-19T23:51:04Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
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-2019:1382 |