On 09/02, Scott Dodson wrote:
> Can you try openshift_release=v3.7 ? that variable is intended to indicate
> just the major.minor you wish to use.
It doesn't work with that. Here's the error:
> Hope this helps,
> On Fri, Feb 9, 2018 at 12:03 AM, Dharmit Shah <ds...@redhat.com> wrote:
> > Hi,
> > I'm trying to upgrade my OpenShift cluster from v3.6 to v3.7. But it
> > fails with the error "openshift_release is 3.7.0 which is not a valid
> > release for a 3.7 upgrade" .
> > OpenShift cluster I have was brought up off the "release-3.6" branch of
> > openshift-ansible repo . Ansible hosts file I am using is . For
> > doing v3.6 deployment, I had set `openshift_release=v3.6.0` in the same
> > ansible hosts file.
> > Command I'm using to do upgrade is:
> > $ ansible-playbook
> > openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_7/upgrade.yml
> > -vvv
> > I executed above command after switching to "release-3.7" branch in the
> > openshift-ansible directory.
> > Not sure what I'm missing here. Do I need to use a different value for
> > release?
> > Regards,
> >  http://pastebin.centos.org/538756/
> >  https://github.com/openshift/openshift-ansible
> >  http://pastebin.centos.org/538746/
> > --
> > Dharmit Shah
> > Red Hat Developer Tools (https://developers.redhat.com/)
> > irc: dharmit (#devtools, #centos, #pune)
> > _______________________________________________
> > users mailing list
> > firstname.lastname@example.org
> > http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Red Hat Developer Tools (https://developers.redhat.com/)
irc, mattermost: dharmit
users mailing list