date:20180820

Re: origin3.9 deployments

2018-08-20 Thread Daniel Comnea

Alan, Todd,

i think i kind of clarified few things in my response [1].

In the future will be good if for same issue we stick to same email thread
to not lose any info - bouncing between threads is getting a bit
unmanageable in my opinion.

Dani

[1]https://github.com/openshift/openshift-ansible/issues/9675#issuecomment
-414488090


On Mon, Aug 20, 2018 at 4:53 PM, Alan Christie <
achris...@informaticsmatters.com> wrote:

> Thanks Todd.
>
> It does appear to be a part of the 
> “openshift-ansible/playbooks/prerequisites.yml”
> playbook that is documented. It’s the one installing the repos. Everything
> was fine a week ago but broke for me last week.
>
> Alan Christie
> achris...@informaticsmatters.com
>
>
>
> > On 20 Aug 2018, at 16:50, Walters, Todd 
> wrote:
> >
> > Ok, good luck. We set our own repo versions. Never had luck and didn’t
> realize the playbooks installed repos. Thought that was a prereq. At least
> in enterprise it was.  Hope it works out for you.
> >
> > On 8/20/18, 10:47 AM, "Alan Christie" 
> wrote:
> >
> >Thanks,
> >
> >I’ve tried all sorts of things now and need a rest - I’ve been trying
> to understand this behaviour for the lat 7 hours and the working day’s
> approaching its end for me!
> >
> >In the meantime I’m raising this an an issue as requested as I
> shouldn’t need to tinker with repos that are being installed by the
> OpenShift playbooks. I use tagged releases and am using
> "openshift-ansible-3.9.40-1”. The rest of the details will go in the issue.
> >
> >In the meantime I’m just going to set “package_version” in the
> "openshift_disable_check” list in the inventory.
> >
> >Alan Christie
> >achris...@informaticsmatters.com
> >
> >
> >
> >> On 20 Aug 2018, at 16:33, Walters, Todd 
> wrote:
> >>
> >> I believe have the proper repos enabled is part of the node
> prerequisites.   So we get around this by running prereq playbook and
> disabling the origin release for latest (repo with no release number on
> end) and enabling 3.9 only
> >>
> >> - name: Install Specific Version of Openshift Origin
> >> yum:
> >>   name: centos-release-openshift-origin
> >>   state: absent
> >>
> >> - name: Install Specific Version of Openshift Origin
> >> yum:
> >>   name: centos-release-openshift-origin39
> >>   state: present
> >>
> >> Also, only git branch that’s supposed to work is release-3.9, which is
> what we always pull for playbooks.
> >>
> >> Thanks,
> >>
> >> Todd
> >>
> >> Today's Topics:
> >>
> >>  1. Re: Ansible/Origin 3.9 deployment now fails because
> >> "package(s) areavailable at a version that is higher than
> >> requested" (Alan Christie)
> >>  2. Re: Ansible/Origin 3.9 deployment now fails because
> >> "package(s) areavailable at a version that is higher than
> >> requested" (Alan Christie)
> >>
> >>
> >>   
> --
> >>
> >>   Message: 1
> >>   Date: Mon, 20 Aug 2018 16:11:50 +0100
> >>   From: Alan Christie 
> >>   To: Peter Heitman 
> >>   Cc: users 
> >>   Subject: Re: Ansible/Origin 3.9 deployment now fails because
> >>   "package(s) areavailable at a version that is higher than requested"
> >>   Message-ID:
> >>   
> >>   Content-Type: text/plain; charset="utf-8"
> >>
> >>   I?m doing pretty-much the same thing. Prior to ?prerequisites? I run
> the following play:
> >>
> >>   - hosts: nodes
> >> become: yes
> >>
> >> tasks:
> >>
> >> - name: Install origin39 repo
> >>   yum:
> >> name: centos-release-openshift-origin39
> >> state: present
> >>
> >>   The 3.9 repo appears in /etc/yum.repos.d/ but, after the
> prerequisites, so does "CentOS-OpenShift-Origin.repo? and the main
> ?deploy_cluster.yml? fails again. The only way through this for me to add
> ?package_version? to ?openshift_disable_check?.
> >>
> >>   Alan Christie
> >>   achris...@informaticsmatters.com
> >>
> >>
> >>
> >>
> >> 
> 
> >> 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
> >> 
> 
> >>
> >
> >
> >
> >
> > 
> > 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 contac

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

2018-08-20 Thread Alan Christie

OK, moved to `#9675`

https://github.com/openshift/openshift-ansible/issues/9675 



Thanks for your attention.

As I have said, I have a work-around for now, and that’s to disable package 
checks for my OpenStack and AWS deployments, which allow me to avoid the error 
and orchestrate operational 3.9 clusters.

Alan Christie
achris...@informaticsmatters.com



> On 20 Aug 2018, at 16:08, Daniel Comnea  wrote:
> 
> Just came across this email, and still not clear why the issue is still 
> taking place.
> 
> Can you please move this issue onto 
> https://github.com/openshift/openshift-ansible 
>  and provide following info:
> 
> openshift-ansible rpm (if you used that) or the tag used
> the gits output with the full trace error you get
> 
> I'll try and see if can help you out..
> 
> 
> 
> On Mon, Aug 20, 2018 at 3:20 PM, Peter Heitman  > wrote:
> I agree with you. I've hit this same error when previous versions were 
> released. I'm not sure why defining the version we want to install (and then 
> using that version of the openshift ansible git) isn't sufficient. As for 
> installing the repo, I do this before I run the prerequisite playbook, i.e. 
> ansible all -i  -m yum -a "name=centos-release-openshift-origin39 
> state=present"  --become. That seems to resolve the issue.
> 
> On Mon, Aug 20, 2018 at 10:10 AM Alan Christie 
> mailto:achris...@informaticsmatters.com>> 
> wrote:
> Thanks Peter.
> 
> Interestingly it looks like it’s Origin’s own “prerequisites.yml” playbook 
> that’s adding the repo that’s causing problems. My instances don’t have this 
> repo until I run that playbook.
> 
> Why do I have to remove something that’s being added by the prerequisite 
> playbook? Especially as my inventory explicitly states 
> "openshift_release=v3.9”?
> 
> If the answer is “do not run prerequisites.yml” what’s the point of it?
> 
> I still wonder why this specific issue is actually an error? Shouldn’t it be 
> installing specific version anyway? Shouldn’t it be error occur if there is 
> no 3.9 package, not if there’s a 3.10 package?
> 
> Incidentally, I’m using the ansible code from "openshift-ansible-3.9.40-1”.
> 
> Alan Christie
> achris...@informaticsmatters.com 
> 
> 
> 
>> On 18 Aug 2018, at 13:36, Peter Heitman > > wrote:
>> 
>> See the recent thread "How to avoid upgrading to 3.10". The bottom line is 
>> to install the 3.9 specific repo. For CentOS that is 
>> centos-release-openshift-origin39
>> 
>> On Sat, Aug 18, 2018, 2:44 AM Alan Christie 
>> mailto:achris...@informaticsmatters.com>> 
>> wrote:
>> HI,
>> 
>> I’ve been deploying new clusters of Origin v3.9 using the official Ansible 
>> playbook approach for a few weeks now, using what appear to be perfectly 
>> reasonable base images on OpenStack and AWS. Then, this week, with no other 
>> changes having been made, the deployment fails with this message: -
>> 
>> One or more checks failed
>>  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.
>> 
>> I can avoid the error, and deploy what appears to be a perfectly functional 
>> 3.9, if I add package_version to openshift_disable_check in the inventory 
>> the deployment. But this is not the right way to deal with this sort of 
>> error.
>> 
>> Q1) How does one correctly address this error?
>> 
>> Q2) Out of interest … why is this specific issue an error? I’ve instructed 
>> the playbook to instal v3.9. I don't care if there is a 3.10 release 
>> available - I do care if there is not a 3.9. Shouldn’t the error occur if 
>> there is no 3.9 package, not if there’s a 3.10 package?
>> 
>> Alan Christie
>> Informatics Matters Ltd.
>> 
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com 
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users 
>> 
> 
> 
> ___
> users mailing list
> users@lists.openshift.redhat.com 
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users 
> 
> 
> 

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: origin3.9 deployments

2018-08-20 Thread Alan Christie

Thanks Todd.

It does appear to be a part of the 
“openshift-ansible/playbooks/prerequisites.yml” playbook that is documented. 
It’s the one installing the repos. Everything was fine a week ago but broke for 
me last week.

Alan Christie
achris...@informaticsmatters.com



> On 20 Aug 2018, at 16:50, Walters, Todd  wrote:
> 
> Ok, good luck. We set our own repo versions. Never had luck and didn’t 
> realize the playbooks installed repos. Thought that was a prereq. At least in 
> enterprise it was.  Hope it works out for you.
> 
> On 8/20/18, 10:47 AM, "Alan Christie"  
> wrote:
> 
>Thanks,
> 
>I’ve tried all sorts of things now and need a rest - I’ve been trying to 
> understand this behaviour for the lat 7 hours and the working day’s 
> approaching its end for me!
> 
>In the meantime I’m raising this an an issue as requested as I shouldn’t 
> need to tinker with repos that are being installed by the OpenShift 
> playbooks. I use tagged releases and am using "openshift-ansible-3.9.40-1”. 
> The rest of the details will go in the issue.
> 
>In the meantime I’m just going to set “package_version” in the 
> "openshift_disable_check” list in the inventory.
> 
>Alan Christie
>achris...@informaticsmatters.com
> 
> 
> 
>> On 20 Aug 2018, at 16:33, Walters, Todd  wrote:
>> 
>> I believe have the proper repos enabled is part of the node prerequisites.   
>> So we get around this by running prereq playbook and disabling the origin 
>> release for latest (repo with no release number on end) and enabling 3.9 only
>> 
>> - name: Install Specific Version of Openshift Origin
>> yum:
>>   name: centos-release-openshift-origin
>>   state: absent
>> 
>> - name: Install Specific Version of Openshift Origin
>> yum:
>>   name: centos-release-openshift-origin39
>>   state: present
>> 
>> Also, only git branch that’s supposed to work is release-3.9, which is what 
>> we always pull for playbooks.
>> 
>> Thanks,
>> 
>> Todd
>> 
>> Today's Topics:
>> 
>>  1. Re: Ansible/Origin 3.9 deployment now fails because
>> "package(s) areavailable at a version that is higher than
>> requested" (Alan Christie)
>>  2. Re: Ansible/Origin 3.9 deployment now fails because
>> "package(s) areavailable at a version that is higher than
>> requested" (Alan Christie)
>> 
>> 
>>   --
>> 
>>   Message: 1
>>   Date: Mon, 20 Aug 2018 16:11:50 +0100
>>   From: Alan Christie 
>>   To: Peter Heitman 
>>   Cc: users 
>>   Subject: Re: Ansible/Origin 3.9 deployment now fails because
>>   "package(s) areavailable at a version that is higher than requested"
>>   Message-ID:
>>   
>>   Content-Type: text/plain; charset="utf-8"
>> 
>>   I?m doing pretty-much the same thing. Prior to ?prerequisites? I run the 
>> following play:
>> 
>>   - hosts: nodes
>> become: yes
>> 
>> tasks:
>> 
>> - name: Install origin39 repo
>>   yum:
>> name: centos-release-openshift-origin39
>> state: present
>> 
>>   The 3.9 repo appears in /etc/yum.repos.d/ but, after the prerequisites, so 
>> does "CentOS-OpenShift-Origin.repo? and the main ?deploy_cluster.yml? fails 
>> again. The only way through this for me to add ?package_version? to 
>> ?openshift_disable_check?.
>> 
>>   Alan Christie
>>   achris...@informaticsmatters.com
>> 
>> 
>> 
>> 
>> 
>> 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
>> 
>> 
> 
> 
> 
> 
> 
> 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

Re: origin3.9 deployments

2018-08-20 Thread Walters, Todd

Ok, good luck. We set our own repo versions. Never had luck and didn’t realize 
the playbooks installed repos. Thought that was a prereq. At least in 
enterprise it was.  Hope it works out for you.

On 8/20/18, 10:47 AM, "Alan Christie"  wrote:

Thanks,

I’ve tried all sorts of things now and need a rest - I’ve been trying to 
understand this behaviour for the lat 7 hours and the working day’s approaching 
its end for me!

In the meantime I’m raising this an an issue as requested as I shouldn’t 
need to tinker with repos that are being installed by the OpenShift playbooks. 
I use tagged releases and am using "openshift-ansible-3.9.40-1”. The rest of 
the details will go in the issue.

In the meantime I’m just going to set “package_version” in the 
"openshift_disable_check” list in the inventory.

Alan Christie
achris...@informaticsmatters.com

> On 20 Aug 2018, at 16:33, Walters, Todd  wrote:
>
> I believe have the proper repos enabled is part of the node 
prerequisites.   So we get around this by running prereq playbook and disabling 
the origin release for latest (repo with no release number on end) and enabling 
3.9 only
>
> - name: Install Specific Version of Openshift Origin
>  yum:
>name: centos-release-openshift-origin
>state: absent
>
> - name: Install Specific Version of Openshift Origin
>  yum:
>name: centos-release-openshift-origin39
>state: present
>
> Also, only git branch that’s supposed to work is release-3.9, which is 
what we always pull for playbooks.
>
> Thanks,
>
> Todd
>
> Today's Topics:
>
>   1. Re: Ansible/Origin 3.9 deployment now fails because
>  "package(s) areavailable at a version that is higher than
>  requested" (Alan Christie)
>   2. Re: Ansible/Origin 3.9 deployment now fails because
>  "package(s) areavailable at a version that is higher than
>  requested" (Alan Christie)
>
>
>--
>
>Message: 1
>Date: Mon, 20 Aug 2018 16:11:50 +0100
>From: Alan Christie 
>To: Peter Heitman 
>Cc: users 
>Subject: Re: Ansible/Origin 3.9 deployment now fails because
>"package(s) areavailable at a version that is higher than requested"
>Message-ID:
>
>Content-Type: text/plain; charset="utf-8"
>
>I?m doing pretty-much the same thing. Prior to ?prerequisites? I run 
the following play:
>
>- hosts: nodes
>  become: yes
>
>  tasks:
>
>  - name: Install origin39 repo
>yum:
>  name: centos-release-openshift-origin39
>  state: present
>
>The 3.9 repo appears in /etc/yum.repos.d/ but, after the 
prerequisites, so does "CentOS-OpenShift-Origin.repo? and the main 
?deploy_cluster.yml? fails again. The only way through this for me to add 
?package_version? to ?openshift_disable_check?.
>
>Alan Christie
>achris...@informaticsmatters.com
>
>
>
>
> 
> 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
> 
>

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

Re: origin3.9 deployments

2018-08-20 Thread Alan Christie

Thanks,

I’ve tried all sorts of things now and need a rest - I’ve been trying to 
understand this behaviour for the lat 7 hours and the working day’s approaching 
its end for me!

In the meantime I’m raising this an an issue as requested as I shouldn’t need 
to tinker with repos that are being installed by the OpenShift playbooks. I use 
tagged releases and am using "openshift-ansible-3.9.40-1”. The rest of the 
details will go in the issue.

In the meantime I’m just going to set “package_version” in the 
"openshift_disable_check” list in the inventory.

Alan Christie
achris...@informaticsmatters.com



> On 20 Aug 2018, at 16:33, Walters, Todd  wrote:
> 
> I believe have the proper repos enabled is part of the node prerequisites.   
> So we get around this by running prereq playbook and disabling the origin 
> release for latest (repo with no release number on end) and enabling 3.9 only
> 
> - name: Install Specific Version of Openshift Origin
>  yum:
>name: centos-release-openshift-origin
>state: absent
> 
> - name: Install Specific Version of Openshift Origin
>  yum:
>name: centos-release-openshift-origin39
>state: present
> 
> Also, only git branch that’s supposed to work is release-3.9, which is what 
> we always pull for playbooks.
> 
> Thanks,
> 
> Todd
> 
> Today's Topics:
> 
>   1. Re: Ansible/Origin 3.9 deployment now fails because
>  "package(s) areavailable at a version that is higher than
>  requested" (Alan Christie)
>   2. Re: Ansible/Origin 3.9 deployment now fails because
>  "package(s) areavailable at a version that is higher than
>  requested" (Alan Christie)
> 
> 
>--
> 
>Message: 1
>Date: Mon, 20 Aug 2018 16:11:50 +0100
>From: Alan Christie 
>To: Peter Heitman 
>Cc: users 
>Subject: Re: Ansible/Origin 3.9 deployment now fails because
>"package(s) areavailable at a version that is higher than requested"
>Message-ID:
>
>Content-Type: text/plain; charset="utf-8"
> 
>I?m doing pretty-much the same thing. Prior to ?prerequisites? I run the 
> following play:
> 
>- hosts: nodes
>  become: yes
> 
>  tasks:
> 
>  - name: Install origin39 repo
>yum:
>  name: centos-release-openshift-origin39
>  state: present
> 
>The 3.9 repo appears in /etc/yum.repos.d/ but, after the prerequisites, so 
> does "CentOS-OpenShift-Origin.repo? and the main ?deploy_cluster.yml? fails 
> again. The only way through this for me to add ?package_version? to 
> ?openshift_disable_check?.
> 
>Alan Christie
>achris...@informaticsmatters.com
> 
> 
> 
> 
> 
> 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

Re: origin3.9 deployments

2018-08-20 Thread Walters, Todd

I believe have the proper repos enabled is part of the node prerequisites.   So 
we get around this by running prereq playbook and disabling the origin release 
for latest (repo with no release number on end) and enabling 3.9 only

- name: Install Specific Version of Openshift Origin
  yum:
name: centos-release-openshift-origin
state: absent

- name: Install Specific Version of Openshift Origin
  yum:
name: centos-release-openshift-origin39
state: present

Also, only git branch that’s supposed to work is release-3.9, which is what we 
always pull for playbooks.

Thanks,

Todd

Today's Topics:

   1. Re: Ansible/Origin 3.9 deployment now fails because
  "package(s) areavailable at a version that is higher than
  requested" (Alan Christie)
   2. Re: Ansible/Origin 3.9 deployment now fails because
  "package(s) areavailable at a version that is higher than
  requested" (Alan Christie)


--

Message: 1
Date: Mon, 20 Aug 2018 16:11:50 +0100
From: Alan Christie 
To: Peter Heitman 
Cc: users 
Subject: Re: Ansible/Origin 3.9 deployment now fails because
"package(s) areavailable at a version that is higher than requested"
Message-ID:

Content-Type: text/plain; charset="utf-8"

I?m doing pretty-much the same thing. Prior to ?prerequisites? I run the 
following play:

- hosts: nodes
  become: yes

  tasks:

  - name: Install origin39 repo
yum:
  name: centos-release-openshift-origin39
  state: present

The 3.9 repo appears in /etc/yum.repos.d/ but, after the prerequisites, so 
does "CentOS-OpenShift-Origin.repo? and the main ?deploy_cluster.yml? fails 
again. The only way through this for me to add ?package_version? to 
?openshift_disable_check?.

Alan Christie
achris...@informaticsmatters.com





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

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

2018-08-20 Thread Alan Christie

But first, quest question…

Is it essential to define all of these?

openshift_release
openshift_image_tag
openshift_pkg_version

I have just noticed that only the first is defined.

Alan Christie
achris...@informaticsmatters.com



> On 20 Aug 2018, at 16:08, Daniel Comnea  wrote:
> 
> Just came across this email, and still not clear why the issue is still 
> taking place.
> 
> Can you please move this issue onto 
> https://github.com/openshift/openshift-ansible 
>  and provide following info:
> 
> openshift-ansible rpm (if you used that) or the tag used
> the gits output with the full trace error you get
> 
> I'll try and see if can help you out..
> 
> 
> 
> On Mon, Aug 20, 2018 at 3:20 PM, Peter Heitman  > wrote:
> I agree with you. I've hit this same error when previous versions were 
> released. I'm not sure why defining the version we want to install (and then 
> using that version of the openshift ansible git) isn't sufficient. As for 
> installing the repo, I do this before I run the prerequisite playbook, i.e. 
> ansible all -i  -m yum -a "name=centos-release-openshift-origin39 
> state=present"  --become. That seems to resolve the issue.
> 
> On Mon, Aug 20, 2018 at 10:10 AM Alan Christie 
> mailto:achris...@informaticsmatters.com>> 
> wrote:
> Thanks Peter.
> 
> Interestingly it looks like it’s Origin’s own “prerequisites.yml” playbook 
> that’s adding the repo that’s causing problems. My instances don’t have this 
> repo until I run that playbook.
> 
> Why do I have to remove something that’s being added by the prerequisite 
> playbook? Especially as my inventory explicitly states 
> "openshift_release=v3.9”?
> 
> If the answer is “do not run prerequisites.yml” what’s the point of it?
> 
> I still wonder why this specific issue is actually an error? Shouldn’t it be 
> installing specific version anyway? Shouldn’t it be error occur if there is 
> no 3.9 package, not if there’s a 3.10 package?
> 
> Incidentally, I’m using the ansible code from "openshift-ansible-3.9.40-1”.
> 
> Alan Christie
> achris...@informaticsmatters.com 
> 
> 
> 
>> On 18 Aug 2018, at 13:36, Peter Heitman > > wrote:
>> 
>> See the recent thread "How to avoid upgrading to 3.10". The bottom line is 
>> to install the 3.9 specific repo. For CentOS that is 
>> centos-release-openshift-origin39
>> 
>> On Sat, Aug 18, 2018, 2:44 AM Alan Christie 
>> mailto:achris...@informaticsmatters.com>> 
>> wrote:
>> HI,
>> 
>> I’ve been deploying new clusters of Origin v3.9 using the official Ansible 
>> playbook approach for a few weeks now, using what appear to be perfectly 
>> reasonable base images on OpenStack and AWS. Then, this week, with no other 
>> changes having been made, the deployment fails with this message: -
>> 
>> One or more checks failed
>>  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.
>> 
>> I can avoid the error, and deploy what appears to be a perfectly functional 
>> 3.9, if I add package_version to openshift_disable_check in the inventory 
>> the deployment. But this is not the right way to deal with this sort of 
>> error.
>> 
>> Q1) How does one correctly address this error?
>> 
>> Q2) Out of interest … why is this specific issue an error? I’ve instructed 
>> the playbook to instal v3.9. I don't care if there is a 3.10 release 
>> available - I do care if there is not a 3.9. Shouldn’t the error occur if 
>> there is no 3.9 package, not if there’s a 3.10 package?
>> 
>> Alan Christie
>> Informatics Matters Ltd.
>> 
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com 
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users 
>> 
> 
> 
> ___
> users mailing list
> users@lists.openshift.redhat.com 
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users 
> 
> 
> 

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

2018-08-20 Thread Alan Christie

Will do

Alan Christie
achris...@informaticsmatters.com



> On 20 Aug 2018, at 16:08, Daniel Comnea  wrote:
> 
> Just came across this email, and still not clear why the issue is still 
> taking place.
> 
> Can you please move this issue onto 
> https://github.com/openshift/openshift-ansible 
>  and provide following info:
> 
> openshift-ansible rpm (if you used that) or the tag used
> the gits output with the full trace error you get
> 
> I'll try and see if can help you out..
> 
> 
> 
> On Mon, Aug 20, 2018 at 3:20 PM, Peter Heitman  > wrote:
> I agree with you. I've hit this same error when previous versions were 
> released. I'm not sure why defining the version we want to install (and then 
> using that version of the openshift ansible git) isn't sufficient. As for 
> installing the repo, I do this before I run the prerequisite playbook, i.e. 
> ansible all -i  -m yum -a "name=centos-release-openshift-origin39 
> state=present"  --become. That seems to resolve the issue.
> 
> On Mon, Aug 20, 2018 at 10:10 AM Alan Christie 
> mailto:achris...@informaticsmatters.com>> 
> wrote:
> Thanks Peter.
> 
> Interestingly it looks like it’s Origin’s own “prerequisites.yml” playbook 
> that’s adding the repo that’s causing problems. My instances don’t have this 
> repo until I run that playbook.
> 
> Why do I have to remove something that’s being added by the prerequisite 
> playbook? Especially as my inventory explicitly states 
> "openshift_release=v3.9”?
> 
> If the answer is “do not run prerequisites.yml” what’s the point of it?
> 
> I still wonder why this specific issue is actually an error? Shouldn’t it be 
> installing specific version anyway? Shouldn’t it be error occur if there is 
> no 3.9 package, not if there’s a 3.10 package?
> 
> Incidentally, I’m using the ansible code from "openshift-ansible-3.9.40-1”.
> 
> Alan Christie
> achris...@informaticsmatters.com 
> 
> 
> 
>> On 18 Aug 2018, at 13:36, Peter Heitman > > wrote:
>> 
>> See the recent thread "How to avoid upgrading to 3.10". The bottom line is 
>> to install the 3.9 specific repo. For CentOS that is 
>> centos-release-openshift-origin39
>> 
>> On Sat, Aug 18, 2018, 2:44 AM Alan Christie 
>> mailto:achris...@informaticsmatters.com>> 
>> wrote:
>> HI,
>> 
>> I’ve been deploying new clusters of Origin v3.9 using the official Ansible 
>> playbook approach for a few weeks now, using what appear to be perfectly 
>> reasonable base images on OpenStack and AWS. Then, this week, with no other 
>> changes having been made, the deployment fails with this message: -
>> 
>> One or more checks failed
>>  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.
>> 
>> I can avoid the error, and deploy what appears to be a perfectly functional 
>> 3.9, if I add package_version to openshift_disable_check in the inventory 
>> the deployment. But this is not the right way to deal with this sort of 
>> error.
>> 
>> Q1) How does one correctly address this error?
>> 
>> Q2) Out of interest … why is this specific issue an error? I’ve instructed 
>> the playbook to instal v3.9. I don't care if there is a 3.10 release 
>> available - I do care if there is not a 3.9. Shouldn’t the error occur if 
>> there is no 3.9 package, not if there’s a 3.10 package?
>> 
>> Alan Christie
>> Informatics Matters Ltd.
>> 
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com 
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users 
>> 
> 
> 
> ___
> users mailing list
> users@lists.openshift.redhat.com 
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users 
> 
> 
> 

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

2018-08-20 Thread Alan Christie

I’m doing pretty-much the same thing. Prior to “prerequisites” I run the 
following play: 

- hosts: nodes
  become: yes

  tasks:

  - name: Install origin39 repo
yum:
  name: centos-release-openshift-origin39
  state: present

The 3.9 repo appears in /etc/yum.repos.d/ but, after the prerequisites, so does 
"CentOS-OpenShift-Origin.repo” and the main “deploy_cluster.yml” fails again. 
The only way through this for me to add “package_version” to 
“openshift_disable_check”.

Alan Christie
achris...@informaticsmatters.com



> On 20 Aug 2018, at 15:20, Peter Heitman  wrote:
> 
> I agree with you. I've hit this same error when previous versions were 
> released. I'm not sure why defining the version we want to install (and then 
> using that version of the openshift ansible git) isn't sufficient. As for 
> installing the repo, I do this before I run the prerequisite playbook, i.e. 
> ansible all -i  -m yum -a "name=centos-release-openshift-origin39 
> state=present"  --become. That seems to resolve the issue.
> 
> On Mon, Aug 20, 2018 at 10:10 AM Alan Christie 
> mailto:achris...@informaticsmatters.com>> 
> wrote:
> Thanks Peter.
> 
> Interestingly it looks like it’s Origin’s own “prerequisites.yml” playbook 
> that’s adding the repo that’s causing problems. My instances don’t have this 
> repo until I run that playbook.
> 
> Why do I have to remove something that’s being added by the prerequisite 
> playbook? Especially as my inventory explicitly states 
> "openshift_release=v3.9”?
> 
> If the answer is “do not run prerequisites.yml” what’s the point of it?
> 
> I still wonder why this specific issue is actually an error? Shouldn’t it be 
> installing specific version anyway? Shouldn’t it be error occur if there is 
> no 3.9 package, not if there’s a 3.10 package?
> 
> Incidentally, I’m using the ansible code from "openshift-ansible-3.9.40-1”.
> 
> Alan Christie
> achris...@informaticsmatters.com 
> 
> 
> 
>> On 18 Aug 2018, at 13:36, Peter Heitman > > wrote:
>> 
>> See the recent thread "How to avoid upgrading to 3.10". The bottom line is 
>> to install the 3.9 specific repo. For CentOS that is 
>> centos-release-openshift-origin39
>> 
>> On Sat, Aug 18, 2018, 2:44 AM Alan Christie 
>> mailto:achris...@informaticsmatters.com>> 
>> wrote:
>> HI,
>> 
>> I’ve been deploying new clusters of Origin v3.9 using the official Ansible 
>> playbook approach for a few weeks now, using what appear to be perfectly 
>> reasonable base images on OpenStack and AWS. Then, this week, with no other 
>> changes having been made, the deployment fails with this message: -
>> 
>> One or more checks failed
>>  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.
>> 
>> I can avoid the error, and deploy what appears to be a perfectly functional 
>> 3.9, if I add package_version to openshift_disable_check in the inventory 
>> the deployment. But this is not the right way to deal with this sort of 
>> error.
>> 
>> Q1) How does one correctly address this error?
>> 
>> Q2) Out of interest … why is this specific issue an error? I’ve instructed 
>> the playbook to instal v3.9. I don't care if there is a 3.10 release 
>> available - I do care if there is not a 3.9. Shouldn’t the error occur if 
>> there is no 3.9 package, not if there’s a 3.10 package?
>> 
>> Alan Christie
>> Informatics Matters Ltd.
>> 
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com 
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users 
>> 
> 

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

2018-08-20 Thread Daniel Comnea

Just came across this email, and still not clear why the issue is still
taking place.

Can you please move this issue onto
https://github.com/openshift/openshift-ansible and provide following info:


   - openshift-ansible rpm (if you used that) or the tag used
   - the gits output with the full trace error you get


I'll try and see if can help you out..



On Mon, Aug 20, 2018 at 3:20 PM, Peter Heitman  wrote:

> I agree with you. I've hit this same error when previous versions were
> released. I'm not sure why defining the version we want to install (and
> then using that version of the openshift ansible git) isn't sufficient. As
> for installing the repo, I do this before I run the prerequisite playbook,
> i.e. ansible all -i  -m yum -a 
> "name=centos-release-openshift-origin39
> state=present"  --become. That seems to resolve the issue.
>
> On Mon, Aug 20, 2018 at 10:10 AM Alan Christie <
> achris...@informaticsmatters.com> wrote:
>
>> Thanks Peter.
>>
>> Interestingly it looks like it’s Origin’s own “prerequisites.yml”
>> playbook that’s adding the repo that’s causing problems. My instances don’t
>> have this repo until I run that playbook.
>>
>> Why do I have to remove something that’s being added by the prerequisite
>> playbook? Especially as my inventory explicitly states
>> "openshift_release=v3.9”?
>>
>> If the answer is “do not run prerequisites.yml” what’s the point of it?
>>
>> I still wonder why this specific issue is actually an error? Shouldn’t it
>> be installing specific version anyway? Shouldn’t it be error occur if there
>> is no 3.9 package, not if there’s a 3.10 package?
>>
>> Incidentally, I’m using the ansible code from
>> "openshift-ansible-3.9.40-1”.
>>
>> Alan Christie
>> achris...@informaticsmatters.com
>>
>>
>>
>> On 18 Aug 2018, at 13:36, Peter Heitman  wrote:
>>
>> See the recent thread "How to avoid upgrading to 3.10". The bottom line
>> is to install the 3.9 specific repo. For CentOS that is
>> centos-release-openshift-origin39
>>
>> On Sat, Aug 18, 2018, 2:44 AM Alan Christie <
>> achris...@informaticsmatters.com> wrote:
>>
>>> HI,
>>>
>>> I’ve been deploying new clusters of Origin v3.9 using the official
>>> Ansible playbook approach for a few weeks now, using what appear to be
>>> perfectly reasonable base images on OpenStack and AWS. Then, this week,
>>> with no other changes having been made, the deployment fails with this
>>> message: -
>>>
>>> One or more checks failed
>>>  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.
>>>
>>> I can avoid the error, and deploy what appears to be a perfectly
>>> functional 3.9, if I add *package_version* to *openshift_disable_check*
>>> in the inventory the deployment. But this is not the right way to deal with
>>> this sort of error.
>>>
>>> Q1) How does one correctly address this error?
>>>
>>> Q2) Out of interest … why is this specific issue an error? I’ve
>>> instructed the playbook to instal v3.9. I don't care if there is a 3.10
>>> release available - I do care if there is not a 3.9. Shouldn’t the error
>>> occur if there is no 3.9 package, not if there’s a 3.10 package?
>>>
>>> Alan Christie
>>> Informatics Matters Ltd.
>>>
>>> ___
>>> users mailing list
>>> users@lists.openshift.redhat.com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>
>>
>>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

2018-08-20 Thread Peter Heitman

I agree with you. I've hit this same error when previous versions were
released. I'm not sure why defining the version we want to install (and
then using that version of the openshift ansible git) isn't sufficient. As
for installing the repo, I do this before I run the prerequisite playbook,
i.e. ansible all -i  -m yum -a
"name=centos-release-openshift-origin39 state=present"  --become. That
seems to resolve the issue.

On Mon, Aug 20, 2018 at 10:10 AM Alan Christie <
achris...@informaticsmatters.com> wrote:

> Thanks Peter.
>
> Interestingly it looks like it’s Origin’s own “prerequisites.yml” playbook
> that’s adding the repo that’s causing problems. My instances don’t have
> this repo until I run that playbook.
>
> Why do I have to remove something that’s being added by the prerequisite
> playbook? Especially as my inventory explicitly states
> "openshift_release=v3.9”?
>
> If the answer is “do not run prerequisites.yml” what’s the point of it?
>
> I still wonder why this specific issue is actually an error? Shouldn’t it
> be installing specific version anyway? Shouldn’t it be error occur if there
> is no 3.9 package, not if there’s a 3.10 package?
>
> Incidentally, I’m using the ansible code from "openshift-ansible-3.9.40-1”.
>
> Alan Christie
> achris...@informaticsmatters.com
>
>
>
> On 18 Aug 2018, at 13:36, Peter Heitman  wrote:
>
> See the recent thread "How to avoid upgrading to 3.10". The bottom line is
> to install the 3.9 specific repo. For CentOS that is
> centos-release-openshift-origin39
>
> On Sat, Aug 18, 2018, 2:44 AM Alan Christie <
> achris...@informaticsmatters.com> wrote:
>
>> HI,
>>
>> I’ve been deploying new clusters of Origin v3.9 using the official
>> Ansible playbook approach for a few weeks now, using what appear to be
>> perfectly reasonable base images on OpenStack and AWS. Then, this week,
>> with no other changes having been made, the deployment fails with this
>> message: -
>>
>> One or more checks failed
>>  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.
>>
>> I can avoid the error, and deploy what appears to be a perfectly
>> functional 3.9, if I add *package_version* to *openshift_disable_check*
>> in the inventory the deployment. But this is not the right way to deal with
>> this sort of error.
>>
>> Q1) How does one correctly address this error?
>>
>> Q2) Out of interest … why is this specific issue an error? I’ve
>> instructed the playbook to instal v3.9. I don't care if there is a 3.10
>> release available - I do care if there is not a 3.9. Shouldn’t the error
>> occur if there is no 3.9 package, not if there’s a 3.10 package?
>>
>> Alan Christie
>> Informatics Matters Ltd.
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

2018-08-20 Thread Alan Christie

Thanks Peter.

Interestingly it looks like it’s Origin’s own “prerequisites.yml” playbook 
that’s adding the repo that’s causing problems. My instances don’t have this 
repo until I run that playbook.

Why do I have to remove something that’s being added by the prerequisite 
playbook? Especially as my inventory explicitly states "openshift_release=v3.9”?

If the answer is “do not run prerequisites.yml” what’s the point of it?

I still wonder why this specific issue is actually an error? Shouldn’t it be 
installing specific version anyway? Shouldn’t it be error occur if there is no 
3.9 package, not if there’s a 3.10 package?

Incidentally, I’m using the ansible code from "openshift-ansible-3.9.40-1”.

Alan Christie
achris...@informaticsmatters.com



> On 18 Aug 2018, at 13:36, Peter Heitman  wrote:
> 
> See the recent thread "How to avoid upgrading to 3.10". The bottom line is to 
> install the 3.9 specific repo. For CentOS that is 
> centos-release-openshift-origin39
> 
> On Sat, Aug 18, 2018, 2:44 AM Alan Christie  > wrote:
> HI,
> 
> I’ve been deploying new clusters of Origin v3.9 using the official Ansible 
> playbook approach for a few weeks now, using what appear to be perfectly 
> reasonable base images on OpenStack and AWS. Then, this week, with no other 
> changes having been made, the deployment fails with this message: -
> 
> One or more checks failed
>  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.
> 
> I can avoid the error, and deploy what appears to be a perfectly functional 
> 3.9, if I add package_version to openshift_disable_check in the inventory the 
> deployment. But this is not the right way to deal with this sort of error.
> 
> Q1) How does one correctly address this error?
> 
> Q2) Out of interest … why is this specific issue an error? I’ve instructed 
> the playbook to instal v3.9. I don't care if there is a 3.10 release 
> available - I do care if there is not a 3.9. Shouldn’t the error occur if 
> there is no 3.9 package, not if there’s a 3.10 package?
> 
> Alan Christie
> Informatics Matters Ltd.
> 
> ___
> users mailing list
> users@lists.openshift.redhat.com 
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users 
> 

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: origin3.9 deployments

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

Re: origin3.9 deployments

Re: origin3.9 deployments

Re: origin3.9 deployments

Re: origin3.9 deployments

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

Re: Ansible/Origin 3.9 deployment now fails because "package(s) are available at a version that is higher than requested"

12 matches

Site Navigation

Mail list logo

Footer information