Anton,

if you set your inventory like below it should get you going.

[OSEv3:vars]
(...)
openshift_additional_repos=[{'id': 'centos-okd-ci', 'name':
'centos-okd-ci', 'baseurl'
:'https://rpms.svc.ci.openshift.org/openshift-origin-v3.11',
'gpgcheck' :'0', 'enabled' :'1'}]

On a different note the OKD v3.11 rpms on CentOS will become available
hopefully this week for testing at least at which point i rely on you
and others in the community to help out with testing.

Thanks.


On Tue, Oct 16, 2018 at 7:31 AM Anton Hughes <anton.c.hug...@gmail.com>
wrote:

> 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.ratiokontakt.de
>  * epel: mirror.wiuwiu.de
>  * extras: mirror.ratiokontakt.de
>  * updates: mirror.checkdomain.de
> No package origin-node-3.11 available.
> Error: Nothing to do
>
> 3. If you run yum clean on the machine, and then run, do you get the right
>> outcome?
>>
>
> No
>
>
>> 4. Did you add the repo to all nodes correctly (verify 2-3 on each)?
>>
>
> I'm trying to install on a single node (master and worker on same host)
> until I can get it to install correctly.
>
> On Tue, 16 Oct 2018 at 03:46, Clayton Coleman <ccole...@redhat.com> wrote:
>
>> 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-3 on each)?
>>
>> On Mon, Oct 15, 2018 at 6:04 AM Anton Hughes <anton.c.hug...@gmail.com>
>> wrote:
>>
>>> 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 nodes
>>>      Task:     Install node, clients, and conntrack packages
>>>      Message:  No package matching 'origin-node-3.11' found available,
>>> installed or update
>>>
>>> On Mon, 15 Oct 2018 at 21:24, Daniel Comnea <comnea.d...@gmail.com>
>>> wrote:
>>>
>>>> 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 <anton.c.hug...@gmail.com>
>>>> wrote:
>>>>
>>>>> I'm trying to repo using ansible, like so:
>>>>>
>>>>> name: update yum repos
>>>>> command: curl -O
>>>>> https://rpms.svc.ci.openshift.org/openshift-origin-v3.11/ >
>>>>> /etc/yum.repos.d/openshift-origin-3.11.repo && yum update
>>>>> But I am getting the following error:
>>>>>
>>>>> FAILED! => {"changed": true, "cmd": ["curl", "-O", "
>>>>> https://rpms.svc.ci.openshift.org/openshift-origin-v3.11/";, ">",
>>>>> "/etc/yum.repos.d/openshift-origin-3.11.repo", "&&", "yum", "update"],
>>>>> "delta": "0:00:00.108763", "end": "2018-10-15 08:02:53.835727", "msg":
>>>>> "non-zero return code", "rc": 7, "start": "2018-10-15 08:02:53.726964",
>>>>> "stderr": "curl: Remote file name has no length!\ncurl: try 'curl --help'
>>>>> or 'curl --manual' for more information\n  % Total    % Received % Xferd
>>>>> Average Speed   Time    Time     Time  Current\n
>>>>>      Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0
>>>>>   0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could 
>>>>> not
>>>>> resolve host: >; Unknown error\ncurl: (3) <url> malformed\ncurl: (6) Could
>>>>> not resolve host: &&; Unknown error\ncurl: (7) Failed connect to yum:80;
>>>>> Connection refused\ncurl: (7) Failed connect to update:80; Connection
>>>>> refused", "stderr_lines": ["curl: Remote file name has no length!", "curl:
>>>>> try 'curl --help' or 'curl --manual' for more information", "  % Total    
>>>>> %
>>>>> Received % Xferd  Average Speed   Time    Time     Time  Current", "
>>>>>                          Dload  Upload   Total   Spent    Left  Speed", 
>>>>> "",
>>>>> "  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--
>>>>>    0curl: (6) Could not resolve host: >; Unknown error", "curl: (3) <url>
>>>>> malformed", "curl: (6) Could not resolve host: &&; Unknown error", "curl:
>>>>> (7) Failed connect to yum:80; Connection refused", "curl: (7) Failed
>>>>> connect to update:80; Connection refused"], "stdout": "", "stdout_lines":
>>>>> []}
>>>>>
>>>>>
>>>>> Can someone tell me what I am doing wrong?
>>>>>
>>>>> Thanks and kind regards
>>>>>
>>>>> On Wed, 10 Oct 2018 at 16:03, Rich Megginson <rmegg...@redhat.com>
>>>>> wrote:
>>>>>
>>>>>> On 10/9/18 8:14 PM, Clayton Coleman wrote:
>>>>>> > What website?
>>>>>>
>>>>>> curl -Lvsk https://rpms.svc.ci.openshift.org/openshift-origin-v3.11
>>>>>> just hangs
>>>>>>
>>>>>> > Just use a slash at the end - all the CI jobs look like
>>>>>> > their working
>>>>>>
>>>>>>
>>>>>> Yep - curl -Lvsk
>>>>>> https://rpms.svc.ci.openshift.org/openshift-origin-v3.11/ works fine.
>>>>>>
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>>
>>>>>> >> On Oct 9, 2018, at 10:10 PM, Rich Megginson <rmegg...@redhat.com>
>>>>>> wrote:
>>>>>> >>
>>>>>> >> Was this ever fixed?  Is this the cause of the website being
>>>>>> currently unresponsive?
>>>>>> >>
>>>>>> >>
>>>>>> >>> On 9/10/18 2:33 PM, Clayton Coleman wrote:
>>>>>> >>> Interesting, might be an HAProxy router bug.  Can you file one?
>>>>>> >>>
>>>>>> >>> On Mon, Sep 10, 2018 at 3:08 PM Seth Jennings <
>>>>>> sjenn...@redhat.com <mailto:sjenn...@redhat.com>> wrote:
>>>>>> >>>
>>>>>> >>>     There is a bug in the webserver configuration.  Main page
>>>>>> links to https://rpms.svc.ci.openshift.org/openshift-origin-v3.11
>>>>>> which gets redirected to
>>>>>> >>>     http://rpms.svc.ci.openshift.org:8080/openshift-origin-v3.11/
>>>>>> (drops https and adds port number).
>>>>>> >>>
>>>>>> >>>     On Sat, Sep 8, 2018 at 9:27 PM Clayton Coleman <
>>>>>> ccole...@redhat.com <mailto:ccole...@redhat.com>> wrote:
>>>>>> >>>
>>>>>> >>>         Previously, all RPMs used by PR and the test automation
>>>>>> or Origin were located in GCS.  Starting with 3.11 and continuing 
>>>>>> forward,
>>>>>> RPMs will be served from the api.ci <http://api.ci>
>>>>>> >>>         cluster at:
>>>>>> >>>
>>>>>> >>>         https://rpms.svc.ci.openshift.org
>>>>>> >>>
>>>>>> >>>         You can get an rpm repo file for a release by clicking on
>>>>>> one of the links on the page above or via curling the name directly:
>>>>>> >>>
>>>>>> >>>             $ curl
>>>>>> https://rpms.svc.ci.openshift.org/openshift-origin-v3.11.repo >
>>>>>> /etc/yum.repos.d/openshift-origin-3.11.repo
>>>>>> >>>
>>>>>> >>>         The contents of this repo will be the same as the
>>>>>> contents of the image:
>>>>>> >>>
>>>>>> >>>         docker.io/openshift/origin-artifacts:v3.11 <
>>>>>> http://docker.io/openshift/origin-artifacts:v3.11>
>>>>>> >>>
>>>>>> >>>         in the /srv/repo dir.
>>>>>> >>>
>>>>>> >>>         PR jobs for 3.11 and onwards will now use this URL to
>>>>>> fetch content.  The old location on GCS will no longer be updated as we 
>>>>>> are
>>>>>> sunsetting the jobs that generated and used that content
>>>>>> >>>         _______________________________________________
>>>>>> >>>         dev mailing list
>>>>>> >>>         dev@lists.openshift.redhat.com <mailto:
>>>>>> dev@lists.openshift.redhat.com>
>>>>>> >>>
>>>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>>>> >>>
>>>>>> >>>
>>>>>> >>> _______________________________________________
>>>>>> >>> dev mailing list
>>>>>> >>> dev@lists.openshift.redhat.com
>>>>>> >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>>>> >>
>>>>>> >> _______________________________________________
>>>>>> >> dev mailing list
>>>>>> >> dev@lists.openshift.redhat.com
>>>>>> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> dev mailing list
>>>>>> dev@lists.openshift.redhat.com
>>>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>>>>
>>>>> _______________________________________________
>>>>> dev mailing list
>>>>> dev@lists.openshift.redhat.com
>>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>>>
>>>> _______________________________________________
>>> dev mailing list
>>> dev@lists.openshift.redhat.com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>
>>
_______________________________________________
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev

Reply via email to