I also have to remove openshift_pkg_version and set openshift_release=3.9.0 Hope this helps
On Wed, Aug 15, 2018 at 9:10 AM David Conde <[email protected]> wrote: > This caught me out yesterday also, a fix is on the 3.9 branch now so > updating from there should help. If using AWS you will have to rebuild your > AMI also as far as I know so that the new yum repo files are picked up. > > On Tue, Aug 14, 2018 at 9:12 PM Peter Heitman <[email protected]> wrote: > >> I use ansible to deploy OpenShift. All of my current deployments are 3.9 >> and I'd like to stay on 3.9 until we can do enough testing on 3.10 to be >> comfortable upgrading. >> >> Can someone point me to any documentation on how to avoid the forced >> upgrade to 3.10 when I deploy a new instance of OpenShift? I currently >> checkout release-3.9 of the ansible scripts: >> >> git clone https://github.com/openshift/openshift-ansible >> cd openshift-ansible >> git checkout release-3.9 >> >> My inventory has the variables >> >> openshift_release=v3.9 >> openshift_pkg_version=-3.9.0 >> >> and yet I get the error below. How do I stay on 3.9? >> >> Failure summary: >> >> >> 1. Hosts: ph-dev-pshtest-master.pdx.hcl.com, >> ph-dev-pshtest-minion1.pdx.hcl.com, ph-dev-pshtest-minion2.pdx.hcl.com, >> ph-dev-pshtest-minion3.pdx.hcl.com >> Play: OpenShift Health Checks >> Task: Run health checks (install) - EL >> Message: One or more checks failed >> Details: check "package_version": >> Some required package(s) are available at a version >> that is higher than requested >> origin-3.10.0 >> origin-node-3.10.0 >> origin-master-3.10.0 >> This will prevent installing the version you requested. >> Please check your enabled repositories or adjust >> openshift_release. >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
