``` [atomic-sig@slave01 ~]$ host cbs.centos.org cbs.centos.org has address 172.20.1.15 [atomic-sig@slave01 ~]$ curl https://cbs.centos.org/repos/virt7-docker-common-candidate/x86_64/os/ ^C ```
Just times out - I'm guessing there's some intermediate firewall, or perhaps IP conflict on the 172.19 subnet?
Using the external IP works:
``` [atomic-sig@slave01 ~]$ host cbs.centos.org 8.8.8.8 Using domain server: Name: 8.8.8.8 Address: 8.8.8.8#53 Aliases:
cbs.centos.org has address 66.187.224.194 [atomic-sig@slave01 ~]$ curl http://66.187.224.194/repos/virt7-docker-common-candidate/x86_64/os/ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> ```
On Tue, May 10, 2016, at 09:35 AM, Colin Walters wrote:
[atomic-sig@slave01 ~]$ host cbs.centos.org cbs.centos.org has address 172.20.1.15 [atomic-sig@slave01 ~]$ curl https://cbs.centos.org/repos/virt7-docker-common-candidate/x86_64/os/ ^CJust times out
Argh! It turns out it's https:// vs http://. I broke it with: https://github.com/CentOS/sig-atomic-buildscripts/pull/68
I can work around this for now by sed'ing the repo to use http just inside the CI infra.
On 10/05/16 15:38, Colin Walters wrote:
On Tue, May 10, 2016, at 09:35 AM, Colin Walters wrote:
[atomic-sig@slave01 ~]$ host cbs.centos.org cbs.centos.org has address 172.20.1.15 [atomic-sig@slave01 ~]$ curl https://cbs.centos.org/repos/virt7-docker-common-candidate/x86_64/os/ ^CJust times out
Argh! It turns out it's https:// vs http://. I broke it with: https://github.com/CentOS/sig-atomic-buildscripts/pull/68
I can work around this for now by sed'ing the repo to use http just inside the CI infra.
CI environment is located in the same DC as cbs, but in a different subnet/vlan and with ip/port filtering at the gw level. Initially we only opened http from ci to cbs, but I now added https too.
On Tue, May 10, 2016, at 09:47 AM, Fabian Arrotin wrote:
CI environment is located in the same DC as cbs, but in a different subnet/vlan and with ip/port filtering at the gw level. Initially we only opened http from ci to cbs, but I now added https too.
Thanks for the quick response, [confirmed] the fix works.
FWIW it's quite important to use https:// for CBS because the RPMs are unsigned. (And even if they were signed one would want to use https:// anyways due to https://isis.poly.edu/%7Ejcappos/papers/cappos_mirror_ccs_08.pdf )
On Tue, May 10, 2016 at 6:47 AM, Fabian Arrotin arrfab@centos.org wrote:
On 10/05/16 15:38, Colin Walters wrote:
On Tue, May 10, 2016, at 09:35 AM, Colin Walters wrote:
[atomic-sig@slave01 ~]$ host cbs.centos.org cbs.centos.org has address 172.20.1.15 [atomic-sig@slave01 ~]$ curl https://cbs.centos.org/repos/virt7-docker-common-candidate/x86_64/os/ ^CJust times out
Argh! It turns out it's https:// vs http://. I broke it with: https://github.com/CentOS/sig-atomic-buildscripts/pull/68
I can work around this for now by sed'ing the repo to use http just inside the CI infra.
CI environment is located in the same DC as cbs, but in a different subnet/vlan and with ip/port filtering at the gw level. Initially we only opened http from ci to cbs, but I now added https too.
I'm getting a similar-looking issue w/ https from the ci artifacts location:
https://ci.centos.org/artifacts/sig-atomic/rdgo/centos-continuous/build/
I'm trying to pull pkgs built in the ci and stored there in another ci job...
Jason
-- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
On 10/05/16 20:37, Jason Brooks wrote:
On Tue, May 10, 2016 at 6:47 AM, Fabian Arrotin arrfab@centos.org wrote:
On 10/05/16 15:38, Colin Walters wrote:
On Tue, May 10, 2016, at 09:35 AM, Colin Walters wrote:
[atomic-sig@slave01 ~]$ host cbs.centos.org cbs.centos.org has address 172.20.1.15 [atomic-sig@slave01 ~]$ curl https://cbs.centos.org/repos/virt7-docker-common-candidate/x86_64/os/ ^CJust times out
Argh! It turns out it's https:// vs http://. I broke it with: https://github.com/CentOS/sig-atomic-buildscripts/pull/68
I can work around this for now by sed'ing the repo to use http just inside the CI infra.
CI environment is located in the same DC as cbs, but in a different subnet/vlan and with ip/port filtering at the gw level. Initially we only opened http from ci to cbs, but I now added https too.
I'm getting a similar-looking issue w/ https from the ci artifacts location:
https://ci.centos.org/artifacts/sig-atomic/rdgo/centos-continuous/build/
I'm trying to pull pkgs built in the ci and stored there in another ci job...
Jason
Different issue as artifact node is internal and that has been discussed some time ago : https://lists.centos.org/pipermail/ci-users/2016-January/000093.html (and people confirmed that the solution worked for them) And the wiki/doc was also adapted to only show one url that works both internally and externally : https://wiki.centos.org/QaWiki/CI/GettingStarted#head-a46ee49e8818ef9b50225c... http://artifacts.ci.centos.org/
On Tue, May 10, 2016, at 02:43 PM, Fabian Arrotin wrote:
That URL is currently only accessible via insecure HTTP (presented cert's CN is just ci.centos.org), so I don't think it's a good idea to point users or systems at it.
On Tue, May 10, 2016 at 11:53 AM, Colin Walters walters@verbum.org wrote:
On Tue, May 10, 2016, at 02:43 PM, Fabian Arrotin wrote:
That URL is currently only accessible via insecure HTTP (presented cert's CN is just ci.centos.org), so I don't think it's a good idea to point users or systems at it.
OK, for now I'm going to work around this in the ci job definition w/ some sed.
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
On 10/05/16 19:43, Fabian Arrotin wrote:
On 10/05/16 20:37, Jason Brooks wrote:
On Tue, May 10, 2016 at 6:47 AM, Fabian Arrotin arrfab@centos.org wrote:
On 10/05/16 15:38, Colin Walters wrote:
On Tue, May 10, 2016, at 09:35 AM, Colin Walters wrote:
[atomic-sig@slave01 ~]$ host cbs.centos.org cbs.centos.org has address 172.20.1.15 [atomic-sig@slave01 ~]$ curl https://cbs.centos.org/repos/virt7-docker-common-candidate/x86_64/os/ ^CJust times out
Argh! It turns out it's https:// vs http://. I broke it with: https://github.com/CentOS/sig-atomic-buildscripts/pull/68
I can work around this for now by sed'ing the repo to use http just inside the CI infra.
CI environment is located in the same DC as cbs, but in a different subnet/vlan and with ip/port filtering at the gw level. Initially we only opened http from ci to cbs, but I now added https too.
I'm getting a similar-looking issue w/ https from the ci artifacts location:
https://ci.centos.org/artifacts/sig-atomic/rdgo/centos-continuous/build/
I'm trying to pull pkgs built in the ci and stored there in another ci job...
Jason
Different issue as artifact node is internal and that has been discussed some time ago : https://lists.centos.org/pipermail/ci-users/2016-January/000093.html (and people confirmed that the solution worked for them) And the wiki/doc was also adapted to only show one url that works both internally and externally : https://wiki.centos.org/QaWiki/CI/GettingStarted#head-a46ee49e8818ef9b50225c... http://artifacts.ci.centos.org/
options on how the https:// might work on the CDN for buildlogs ?
On 11/05/16 15:12, Karanbir Singh wrote:
On 10/05/16 19:43, Fabian Arrotin wrote:
On 10/05/16 20:37, Jason Brooks wrote:
On Tue, May 10, 2016 at 6:47 AM, Fabian Arrotin arrfab@centos.org wrote:
On 10/05/16 15:38, Colin Walters wrote:
On Tue, May 10, 2016, at 09:35 AM, Colin Walters wrote:
[atomic-sig@slave01 ~]$ host cbs.centos.org cbs.centos.org has address 172.20.1.15 [atomic-sig@slave01 ~]$ curl https://cbs.centos.org/repos/virt7-docker-common-candidate/x86_64/os/ ^CJust times out
Argh! It turns out it's https:// vs http://. I broke it with: https://github.com/CentOS/sig-atomic-buildscripts/pull/68
I can work around this for now by sed'ing the repo to use http just inside the CI infra.
CI environment is located in the same DC as cbs, but in a different subnet/vlan and with ip/port filtering at the gw level. Initially we only opened http from ci to cbs, but I now added https too.
I'm getting a similar-looking issue w/ https from the ci artifacts location:
https://ci.centos.org/artifacts/sig-atomic/rdgo/centos-continuous/build/
I'm trying to pull pkgs built in the ci and stored there in another ci job...
Jason
Different issue as artifact node is internal and that has been discussed some time ago : https://lists.centos.org/pipermail/ci-users/2016-January/000093.html (and people confirmed that the solution worked for them) And the wiki/doc was also adapted to only show one url that works both internally and externally : https://wiki.centos.org/QaWiki/CI/GettingStarted#head-a46ee49e8818ef9b50225c... http://artifacts.ci.centos.org/
options on how the https:// might work on the CDN for buildlogs ?
Well, buildlogs is external but also internal copy (yeah ....) but we'd be able to setup proper https support for that, but the automatic http->https redirection is what needs to be tested and how yum follows the redirection for the repomd.xml file (if that works) Something added on the TODO list, but not priority #1 this week though
OTOH, it's true that it was also discussed that people needing a lot of artifacts file should ask those to be published on the CDN, and not retrieved from CI network at all (but can be problematic if people want the same test to work inside and outside too)
-
Colin Walters -
Fabian Arrotin -
Jason Brooks -
Karanbir Singh