CI-users January 2020

ci-users@lists.centos.org

8 participants
6 discussions

URGENT - https://ci.centos.org/ is down
by Maor Friedman 26 Jan '20

26 Jan '20

Hello, https://ci.centos.org/ is returning a 502 Bad Gateway. Is there anyone that can look into this? Thanks, -- Maor Friedman Senior Software Engineer, Application SRE team, Service Delivery Red Hat maor(a)redhat.com

2 4

Dirty nodes
by Katerina Foniok 24 Jan '20

24 Jan '20

Hello guys, it seems that data are not cleaned correctly from the nodes. Some of our tests are failing on that. E.g. https://ci.centos.org/view/Devtools/job/devtools-rh-che-periodic-prod-2aPro… where the folder with the logs already exists. This job was run on devtools-ci-slave04. Thank you for your time. Have a nice day! Katka Foniok

4 9

CentOS 7/8 OpenSSL / FIPS 140-2 / FedRAMP
by Salman Baset 19 Jan '20

19 Jan '20

Hello, I was wondering if the source code for OpenSSL (1.1.*) in CentOS 7 and 8 is exactly the same as Red Hat and thus would be considered equivalent from a FIPS 140-2 cert standpoint. See the RHEL 7.0 OpenSSL FIPS certificate below. https://csrc.nist.gov/Projects/cryptographic-module-validation-program/Cert… Also, has anyone recently used Cent OS 7 with OpenSSL EL rpm (1.1.*) to successfully obtain FedRAMP Moderate authorization or was it necessary to switch to Red Hat? Thanks Salman

1 0

using ci.centos.org for quarkus opensource project builds ?
by Max Andersen 13 Jan '20

13 Jan '20

Hi, I was chatting with Paul Bergene if it was possible to use ci.centos.org for off-loading some of Quarkus opensource project builds. We got two kind of builds we would be interested in "offloading". First are regular jobs which would be easy to setup via jenkins. Question here is if docker builds and runs are allowed in the nodes ? I remember there being some limitations earlier on this ? The other is if it is in any way possible to use ci.centos.org as target for github actions ? Is that something that have been considered enabling? Thanks, -- /max https://about.me/maxandersen

3 2

Install & enable NTP on Duffy nodes
by František Šumšal 13 Jan '20

13 Jan '20

Hello! After recent struggles with compilation under Vagrant over NFS, I'd like to ask if it would be possible to automatically sync all machines provided by Duffy using NTP. We encountered several nasty race conditions caused by system time discrepancies between a Duffy host and a VM, which I managed to mitigate by installing & enabling chrony. Unfortunately, it's not perfect, as the time synchronization apparently takes some time, so the race condition is present, but it's much less probable. Going through Jenkins logs it looks that all machines have their time significantly off: ● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-12 16:06:53 GMT; 5h 51min left Docs: man:chronyd(8) man:chrony.conf(5) Main PID: 1992 (chronyd) CGroup: /system.slice/chronyd.service └─1992 /usr/sbin/chronyd Jan 12 16:06:53 n15.pufty systemd[1]: Starting NTP client/server... Jan 12 16:06:53 n15.pufty chronyd[1992]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 +DEBUG) Jan 12 16:06:53 n15.pufty systemd[1]: Started NTP client/server. Jan 12 16:07:01 n15.pufty chronyd[1992]: Selected source xx.xx.xx.xx Jan 12 16:07:01 n15.pufty chronyd[1992]: System clock wrong by -21251.336765 seconds, adjustment started Jan 12 10:12:50 n15.pufty chronyd[1992]: System clock was stepped by -21251.336765 seconds I suspect waiting for the synchronization to fully complete using chrony's CLI utilities would help, but having this to be handled automatically by each machine would be much better. Thanks! Frantisek -- PGP Key ID: 0xFB738CE27B634E4B

2 1

Duffy seems to be out of CentOS 7 nodes
by František Šumšal 03 Jan '20

03 Jan '20

Hello! Sorry to bother you during holidays, but is looks like Duffy has a trouble provisioning CentOS 7 nodes: ``` 2019-12-26 07:36:18,171 [agent-control/allocate_node] INFO: Attempting to allocate a node (7 x86_64) ... 2019-12-26 07:52:19,680 [agent-control/allocate_node] INFO: Waiting 1800 seconds before another retry 2019-12-26 08:22:19,757 [agent-control/_execute_api_command] INFO: Duffy request URL: xxx 2019-12-26 08:22:19,759 [connectionpool/_new_conn] INFO: Starting new HTTP connection (1): xxx 2019-12-26 08:22:20,029 [agent-control/allocate_node] ERROR: Received unexpected response from the server: Insufficient Nodes in READY State 2019-12-26 08:22:20,029 [agent-control/allocate_node] INFO: Waiting 3600 seconds before another retry 2019-12-26 09:22:20,126 [agent-control/allocate_node] ERROR: Failed to allocated a node 2019-12-26 09:22:20,126 [agent-control/<module>] CRITICAL: Can't continue without a valid node ``` -- Frantisek Sumsal GPG key ID: 0xFB738CE27B634E4B

2 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

CI-users January 2020