- Infra - oVirt List Archives

[JIRA] (OVIRT-2053) show release_branches information as part of STDCIv2 conf checker
by Emil Natan (oVirt JIRA) 24 May '18

24 May '18

Emil Natan created OVIRT-2053: --------------------------------- Summary: show release_branches information as part of STDCIv2 conf checker Key: OVIRT-2053 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2053 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Emil Natan Assignee: infra Show release_branches information as part of STDCIv2 configuration check utility -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: 91409, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 May '18

24 May '18

A system test invoked by the "ovirt-master" change queue including change 91409,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 89293,19 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91409/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7716/

1 0

[CQ]: 91365, 9 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 May '18

23 May '18

A system test invoked by the "ovirt-master" change queue including change 91365,9 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 89293,19 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91365/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7711/

1 0

[CQ]: 91333, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 May '18

23 May '18

A system test invoked by the "ovirt-master" change queue including change 91333,11 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 89293,19 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91333/11 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7706/

1 0

[CQ]: 91444, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 May '18

23 May '18

A system test invoked by the "ovirt-master" change queue including change 91444,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 89293,19 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91444/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7701/

1 0

oVirt infra weekly meeting notes 23.05.2018
by Evgheni Dereveanchin 23 May '18

23 May '18

Hi everyone, Please find the topics of this week's infra meeting below: *PHX DC: - CVE-2018-3639 OVIRT-2045 <https://ovirt-jira.atlassian.net/browse/OVIRT-2045>- Jenkins patched- Gerrit patched- Resources patched- Website patched- Jenkins core updated- SSL enabled on JenkinsMailMan: - Archive was incomplete - fixed by re-running cron job- UI issues - some settings not exposedAI: - Add links to https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> on our services- Create user for trello integration * -- Regards, Evgheni Dereveanchin

1 0

[CQ]: 91442, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 May '18

23 May '18

A system test invoked by the "ovirt-master" change queue including change 91442,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 89293,19 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91442/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7696/

1 0

[JIRA] (OVIRT-2052) Updated SSL Stores on resources.ovirt.org
by Anton Marchukov (oVirt JIRA) 23 May '18

23 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2052?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2052: -------------------------------------- Assignee: Anton Marchukov (was: infra) > Updated SSL Stores on resources.ovirt.org > ----------------------------------------- > > Key: OVIRT-2052 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2052 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: Anton Marchukov > > resources.ovirt.org has old SSL stores and does not consider lets > encrypt certs as valid: > ovpn-205-70:~ amarchuk$ ssh http://resources.ovirt.org > ssh: Could not resolve hostname http://resources.ovirt.org: nodename > nor servname provided, or not known > ovpn-205-70:~ amarchuk$ ssh resources.ovirt.org > Last login: Thu May 10 14:19:17 2018 from monitoring.ovirt.org > [amarchuk@resources02 ~]$ curl https://jenkins.ovirt.org/ > curl: (60) Peer's Certificate issuer is not recognized. > More details here: http://curl.haxx.se/docs/sslcerts.html > curl performs SSL certificate verification by default, using a "bundle" > of Certificate Authority (CA) public keys (CA certs). If the default > bundle file isn't adequate, you can specify an alternate file > using the --cacert option. > If this HTTPS server uses a certificate signed by a CA represented in > the bundle, the certificate verification probably failed due to a > problem with the certificate (it might be expired, or the name might > not match the domain name in the URL). > If you'd like to turn off curl's verification of the certificate, use > the -k (or --insecure) option. > We also have a python utility called repoman that uses the bundle > certs inside “python-requests” library so we need to make sure it is > updated too along with the system certs. > We might have the same problem on other servers, e.g. on Jenkins and > it’s slaves so might make sense to analyse the situation and extend > this ticket. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2052) Updated SSL Stores on resources.ovirt.org
by Anton Marchukov (oVirt JIRA) 23 May '18

23 May '18

Anton Marchukov created OVIRT-2052: -------------------------------------- Summary: Updated SSL Stores on resources.ovirt.org Key: OVIRT-2052 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2052 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Anton Marchukov Assignee: infra resources.ovirt.org has old SSL stores and does not consider lets encrypt certs as valid: ovpn-205-70:~ amarchuk$ ssh http://resources.ovirt.org ssh: Could not resolve hostname http://resources.ovirt.org: nodename nor servname provided, or not known ovpn-205-70:~ amarchuk$ ssh resources.ovirt.org Last login: Thu May 10 14:19:17 2018 from monitoring.ovirt.org [amarchuk@resources02 ~]$ curl https://jenkins.ovirt.org/ curl: (60) Peer's Certificate issuer is not recognized. More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. We also have a python utility called repoman that uses the bundle certs inside “python-requests” library so we need to make sure it is updated too along with the system certs. We might have the same problem on other servers, e.g. on Jenkins and it’s slaves so might make sense to analyse the situation and extend this ticket. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[CQ]: 91441, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 May '18

23 May '18

A system test invoked by the "ovirt-master" change queue including change 91441,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 89293,19 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91441/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7691/

1 0