Thanks Troy & Scott. I was able to run the upgrade from 1.4 to 1.5 w/o issues. One thing that didn't work though is when I ran `atomic-openshift-installer upgrade` I was presented with two options: 1) Upgrade to the latest 1.4 and 2) Upgrade to 1.5. When I selected 1), I got a stack trace at [1] because 1.4 is not a supported version anymore at [2]. [1] https://github.com/openshift/openshift-ansible/blob/d1c04dd6c5a2b58013371f4c3865ddb30433573c/utils/src/ooinstall/openshift_ansible.py#L140-L141 [2] https://github.com/openshift/openshift-ansible/blob/d1c04dd6c5a2b58013371f4c3865ddb30433573c/utils/src/ooinstall/variants.py#L49-L51 Thanks, Jean-Francois C. On Tue, Jun 20, 2017 at 4:54 PM, Troy Dawson <tdawson at redhat.com> wrote: > I have built one of the later 3.5 openshift-ansibles, and applied this > patch to it. > openshift-ansible-3.5.82-1.git.1.f658b01.el7 > > I've tagged it into testing, that might take up to 2 hours to get > there. But when it does, you should be able to do > > yum --enablerepo=centos-openshift-origin15-testing clean all > yum --enablerepo=centos-openshift-origin15-testing update > atomic-openshift-utils openshift-ansible\* > > After that, give it a try and let us know if allowed you to update. > > Troy > > > On Tue, Jun 20, 2017 at 8:01 AM, Scott Dodson <sdodson at redhat.com> wrote: > > Can you try this? > > > > https://github.com/openshift/openshift-ansible/pull/4508 > > > > On Tue, Jun 20, 2017 at 10:01 AM, Troy Dawson <tdawson at redhat.com> > wrote: > >> > >> On Tue, Jun 20, 2017 at 6:53 AM, Jean-Francois Chevrette > >> <jchevret at redhat.com> wrote: > >> > Hi, > >> > > >> > 3 months ago I have used atomic-openshift-utils/installer to setup > two > >> > OpenShift origin 1.4 clusters. Today I discovered that I am unable to > >> > upgrade from 1.4 to 1.5 because atomic-openshift-installer states that > >> > "No > >> > upgrades available for origin 1.4" > >> > > >> > atomic-openshift-utils-3.5.71-1.git.1.640cb7d.el7.noarch > >> > centos-release-openshift-origin15-1-1.el7.centos.noarch > >> > openshift-ansible-3.5.71-1.git.1.640cb7d.el7.noarch > >> > openshift-ansible-callback-plugins-3.5.71-1.git.1.640cb7d.el7.noarch > >> > openshift-ansible-docs-3.5.71-1.git.1.640cb7d.el7.noarch > >> > openshift-ansible-filter-plugins-3.5.71-1.git.1.640cb7d.el7.noarch > >> > openshift-ansible-lookup-plugins-3.5.71-1.git.1.640cb7d.el7.noarch > >> > openshift-ansible-playbooks-3.5.71-1.git.1.640cb7d.el7.noarch > >> > openshift-ansible-roles-3.5.71-1.git.1.640cb7d.el7.noarch > >> > > >> > 1.5 is in the list of supported install variants here: > >> > /usr/lib/python2.7/site-packages/ooinstall/variants.py > >> > > >> > However the UPGRADE_MAPPINGS list in > >> > /usr/lib/python2.7/site-packages/ooinstall/cli_installer.py only has > >> > upgrade > >> > paths for 3.4 and 3.5 > >> > > >> > Is upgrading between origin releases simply not supported/possible? > >> > > >> > > >> > Thanks, > >> > Jean-Francois C. > >> > > >> > >> Sounds like a bug to me. > >> Maybe we need to do a few more tweeks to atomic-openshift than I > thought. > >> I'm cc'ing Scott Dodson on this to see what the official stance is on > >> this. > >> > >> Troy > > > > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20170621/4a2edb1b/attachment-0008.html>