New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Registry and router image version mangled during upgrade #1072
Comments
|
@cooktheryan The upgrade scripts do some version checking of packages that are currently installed and those that are available. |
|
The update was ran on the system pre-openshift-ansible Jun 29 19:09:27 Installed: openshift-3.0.0.0-0.git.25.235b0e7.el7ose.x86_64 Script ran was /home/rcook/git/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_0_to_v3_1/upgrade.yml Running on a clean cluster without yum update being ran first. Will post output once completed |
|
Registry started correctly this time. Registry version openshift3/ose-docker-registry:v3.1.0.4 yum output |
|
|
Simplest fix might be to just add a |
|
@abutcher agreed, we should probably use the yum/dnf api for gathering the info rather than attempting to parse the output of yum list. That said, a quick workaround for |
|
|
|
We've made many advances in version detection recently so I am going to close this issue. Please update and reopen this issue if this is still a priority you would like to see action on. |
Seems like two different folks have run into this.
First case
Error: image openshift3/ose-docker-registry:vmanager 3.1.0.4 not found
Error: image openshift3/ose-haproxy-router:vmanager 3.1.0.4 not found
Second case from @cooktheryan yielded
Error: image openshift3/ose-docker-registry:vsystem 3.1.0.4 not found
The text was updated successfully, but these errors were encountered: