you could also add the 3.8 repo too On Wed, Aug 15, 2018 at 12:16 PM Walters, Todd <todd_walt...@unigroup.com> wrote:
> > Today's Topics: > > 1. Re: How to avoid upgrading to 3.10? (David Conde) > 2. Re: How to avoid upgrading to 3.10? (Scott Dodson) > > > For upgrades from 3.7 to 3.9 for example you can’t use the origin3.9 repo > at http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin39/ > because it does not contain the required 3.8 rpms for upgrade process. You > need to specify the openshift-origin repo without version listed as shown > below and located here: > http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/ > > We also specifically set the repo we’re using on all ‘hosts’ by running a > pretask ansible playbook such as below. > > - name: Install Specific Version of Openshift Origin > yum: > name: centos-release-openshift-origin39 > state: absent > > - name: Install Specific Version of Openshift Origin > yum: > name: centos-release-openshift-origin > state: present > > This allows us to change repo from which ever version we’re on. > > We’ve had no issue, after upgrade from 3.7 > 3.9 , changing the repo to > the 3.9 origin repo. Only caveat, the repos aren’t immediately available > from CentOS for a few days after new release. > > Thanks, > > Todd > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 15 Aug 2018 09:20:24 +0100 > From: David Conde <da...@donedeal.ie> > To: pe...@heitman.us > Cc: users <users@lists.openshift.redhat.com> > Subject: Re: How to avoid upgrading to 3.10? > Message-ID: > <CA+AQPyEa_ykEVE+cdsPfw0Ok2=qw6ev1sax5mwt7ocrcdql...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > 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 <da...@donedeal.ie> 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 <pe...@heitman.us> > 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenshift%2Fopenshift-ansible&data=01%7C01%7Ctodd_walters%40unigroup.com%7C4e600a64a6124bac1d5c08d602c82d9f%7C259bdc2f86d3477b8cb34eee64289142%7C1&sdata=a%2BPTyT56wh2cORL6sJz15GLv7dOLc423n7dCkIGPwjY%3D&reserved=0 > >> 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 > >> users@lists.openshift.redhat.com > >> > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.openshift.redhat.com%2Fopenshiftmm%2Flistinfo%2Fusers&data=01%7C01%7Ctodd_walters%40unigroup.com%7C4e600a64a6124bac1d5c08d602c82d9f%7C259bdc2f86d3477b8cb34eee64289142%7C1&sdata=jEioME9NJ0NB5dlNtbFXG6IalRmG7ZtFgP411%2Ff7%2BMA%3D&reserved=0 > >> > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.openshift.redhat.com%2Fopenshift-archives%2Fusers%2Fattachments%2F20180815%2Fe681c77d%2Fattachment.html&data=01%7C01%7Ctodd_walters%40unigroup.com%7C4e600a64a6124bac1d5c08d602c82d9f%7C259bdc2f86d3477b8cb34eee64289142%7C1&sdata=bYZDcMNQVx2Sz8LEjmsjjxLTBZ3ORtfR%2FAOAgXcrmOs%3D&reserved=0 > > > > ------------------------------ > > Message: 2 > Date: Wed, 15 Aug 2018 08:11:35 -0400 > From: Scott Dodson <sdod...@redhat.com> > To: da...@donedeal.ie > Cc: users <users@lists.openshift.redhat.com> > Subject: Re: How to avoid upgrading to 3.10? > Message-ID: > <CAMGf98F3srkcTQZ4j3KhNvA3+24YgZs8Mbx5tKPDsZvccC8=v...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > The packages that the installer uses come from the CentOS PaaS SIG. By > default they point at a repo that includes all releases unless we have > a > repo specific for the release you're using defined in > openshift-ansible. > > @DanyC97 added a 3.9 repo to the 3.9 branch a day or two ago, you can > use > this to replace your existing yum repo file and it will continue to > track > 3.9. > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenshift%2Fopenshift-ansible%2Fpull%2F9549&data=01%7C01%7Ctodd_walters%40unigroup.com%7C4e600a64a6124bac1d5c08d602c82d9f%7C259bdc2f86d3477b8cb34eee64289142%7C1&sdata=9tb%2Fbkk%2BG5pAxaTTHG1YF5aagQEokio%2FTOzGK91kFFw%3D&reserved=0 > > On Wed, Aug 15, 2018 at 4:21 AM David Conde <da...@donedeal.ie> wrote: > > > I also have to remove openshift_pkg_version and > > set openshift_release=3.9.0 Hope this helps > > > > > > > ######################################################################## > The information contained in this message, and any attachments thereto, > is intended solely for the use of the addressee(s) and may contain > confidential and/or privileged material. Any review, retransmission, > dissemination, copying, or other use of the transmitted information is > prohibited. If you received this in error, please contact the sender > and delete the material from any computer. UNIGROUP.COM > ######################################################################## > >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
