Re: CI automation location for RPMs is moving

2018-10-16 Thread Daniel Comnea
That's expected since i missed a / at the end. if you use the below it should all work for you [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'}]

Re: CI automation location for RPMs is moving

2018-10-16 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:

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

Re: CI automation location for RPMs is moving

2018-10-09 Thread Rich Megginson
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

Re: CI automation location for RPMs is moving

2018-10-09 Thread Clayton Coleman
What website? Just use a slash at the end - all the CI jobs look like their working > On Oct 9, 2018, at 10:10 PM, Rich Megginson 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,

Re: CI automation location for RPMs is moving

2018-10-09 Thread Rich Megginson
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 mailto:sjenn...@redhat.com>> wrote: There is a

Re: CI automation location for RPMs is moving

2018-09-10 Thread Clayton Coleman
Interesting, might be an HAProxy router bug. Can you file one? On Mon, Sep 10, 2018 at 3:08 PM Seth Jennings 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 >

Re: CI automation location for RPMs is moving

2018-09-10 Thread Seth Jennings
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

Re: CI automation location for RPMs is moving

2018-09-10 Thread Clayton Coleman
It’s used for all Origin CI. Post release, any hotfixes will be in that location. These are not signed RPMs nor will they be preserved - they’re just a convenient place to get the build output. On Sep 10, 2018, at 8:49 AM, Daniel Comnea wrote: Clayton, Is the url

Re: CI automation location for RPMs is moving

2018-09-10 Thread Daniel Comnea
Clayton, Is the url https://rpms.svc.ci.openshift.org meant to be public available or is only available internally for your own deployments ? In addition, is the plan that everyone deploying OCP/ OKD on RHEL/ CentOS to use the above common repo (assuming is going to be public accessible ) ?