Re: CI automation location for RPMs is moving

2018-10-15 Thread Anton Hughes
> > 1. Are you on ansible 2.6 or earlier? > Im using ansible 2.6.5 > 2. If you access that machine and run 'yum install origin-node-3.11*' do > you get a result? > I get yum install origin-node-3.11 Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.ratiokon

Re: CI automation location for RPMs is moving

2018-10-15 Thread Clayton Coleman
A couple of things to check. 1. Are you on ansible 2.6 or earlier? 2. If you access that machine and run 'yum install origin-node-3.11*' do you get a result? 3. If you run yum clean on the machine, and then run, do you get the right outcome? 4. Did you add the repo to all nodes correctly (verify 2

Re: CI automation location for RPMs is moving

2018-10-15 Thread Anton Hughes
Ive tried both of the following - and get the same error: yum-config-manager --add-repo https://rpms.svc.ci.openshift.org/openshift-origin-v3.11.repo && yum update yum-config-manager --add-repo https://rpms.svc.ci.openshift.org/openshift-origin-v3.11/ && yum update Error Play: Configure n

Re: CI automation location for RPMs is moving

2018-10-15 Thread Daniel Comnea
Don't you need to build your repo file by setting the baseUrl to https://rpms.svc.ci.openshift.org/openshift-origin-v3.11/ and then give it a run ? On Mon, Oct 15, 2018 at 7:08 AM Anton Hughes wrote: > I'm trying to repo using ansible, like so: > > name: update yum repos > command: curl -O htt