[CQ]: 97397,7 (vdsm) failed "ovirt-master" system tests
Change 97397,7 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97397/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12617/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/OX2F5RT4G62ACTEK3ABYUHOMZHL5DP3O/
oVirt infra daily report - unstable production jobs - 722
Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/722//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins RHEVM CI Jenkins Daily Report - 31/01/2019 00 Unstable Critical ovirt-node-ng-image_master_build-artifacts-fc28-x86_64 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_hc-basic-suite-4.2 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_he-basic-iscsi-suite-master This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_network-suite-4.2 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_openshift-on-ovirt-suite-4.2 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/KMP3SJSG5VAWM4SLIAVWOGXSQKBHQCYN/
[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
Failed to run project_setup.sh for: #3402 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-77p5l.___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/2CNIKBUZHTQVRDABD5BJBDP3V6RRJVGD/
[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
Failed to run project_setup.sh for: #3401 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-2f4nn.___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GDKHVIRNTGOBBJ4DUWANXHA24IKRS62I/
[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
Failed to run project_setup.sh for: #3398 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-chplw.___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EKYZDB7VNY6V2N6LWV34RLL6W24HN2AM/
[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
Failed to run project_setup.sh for: #3398 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-trzjs.___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/H6UI7KKVHUA6YBMS2D7N7UMHYZYDZOAR/
[CQ]: 97452,5 (py2exe-py2.7) failed "ovirt-master" system tests
Change 97452,5 (py2exe-py2.7) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97452/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12616/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/AENNTF2GJ6XMQXAEROFAG45AQDYSOD3A/
[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
Failed to run project_setup.sh for: #3397 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-dcqcz.___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/4DVXU56QY4LAJRBTUTIYZJYR5BT3O57X/
[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
Failed to run project_setup.sh for: #1187 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-16wh5.___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GXOCP3I4QGV5POBTW2CAHUQF7VA2XAW5/
[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
Failed to run project_setup.sh for: #3395 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-4cbz7.___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/Q6QDKSBONMO4CU5UKHJDWF4QYCWDPA7J/
[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
Failed to run project_setup.sh for: #3395 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-g7v68.___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/QPL3WATGC3N5C3M2JTH2NAKC62AHAPD2/
[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
Failed to run project_setup.sh for: #3394 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-535z1.___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/PSCCFRB5R6WGKXXQLESDLDZTMEK6LOA7/
[CQ]: 97391,4 (vdsm) failed "ovirt-master" system tests
Change 97391,4 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97391/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12609/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/IUWMFMJVN5N2KF6W44RYJJNFKOWLKZFB/
[JIRA] (OVIRT-2665) certbot broken on engine-phx
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgheni Dereveanchin reassigned OVIRT-2665:
---
Assignee: Evgheni Dereveanchin (was: infra)
> certbot broken on engine-phx
>
>
> Key: OVIRT-2665
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2665
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Evgheni Dereveanchin
>Assignee: Evgheni Dereveanchin
>
> The PHX engine has a Let'sEncrypt certificate deployed and uses certbot to
> renew it.
> Currently it's broken and displaying a missing requirement for cryptography:
> pkg_resources.ContextualVersionConflict: (cryptography 1.7.2
> (/usr/lib64/python2.7/site-packages), Requirement.parse('cryptography>=1.9'),
> set(['PyOpenSSL'])
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/OMMZAD37HC7YRPWPYX3YMXGBCMGKXWJC/
[JIRA] (OVIRT-2665) certbot broken on engine-phx
Evgheni Dereveanchin created OVIRT-2665:
---
Summary: certbot broken on engine-phx
Key: OVIRT-2665
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2665
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: Evgheni Dereveanchin
Assignee: infra
The PHX engine has a Let'sEncrypt certificate deployed and uses certbot to
renew it.
Currently it's broken and displaying a missing requirement for cryptography:
pkg_resources.ContextualVersionConflict: (cryptography 1.7.2
(/usr/lib64/python2.7/site-packages), Requirement.parse('cryptography>=1.9'),
set(['PyOpenSSL'])
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/FFVLQBQHFZIDEJLQYJCQYWMVYZ4DF4P6/
[JIRA] (OVIRT-2664) OST runs engine 4.2 by default, misleading developers
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri updated OVIRT-2664: - Resolution: Fixed Status: Done (was: To Do) > OST runs engine 4.2 by default, misleading developers > - > > Key: OVIRT-2664 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2664 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Nir Soffer >Assignee: infra > > When creating OST manual job, the UI select engine version 4.2 by default: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/build?delay=0sec > A developer that want to test engine master must change the version > manually. > I you forget to change the version, or just do not notice that there is > engine > version to choose, your job may succeed when it actually fail with engine > master. > Watching other developers start OST jobs, they do not notice that engine > version must be selected, and treat it as the other options that most people > do not care about. > This is probably the reason why OST was broken for a week, and nobody > complained about it, since default build used engine 4.2. > How to fix: > - The UI must be changed to require engine version selection. You cannot > have default for this. > The UI should show something like: > ENGINE_VERSION: [select version] *required > - The "Build" button must be disabled if no version was selected. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EWOXBF4YFLW7UO55CKN7MSRHHMHD3CAN/
[JIRA] (OVIRT-2664) OST runs engine 4.2 by default, misleading developers
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38915#comment-38915 ] Eyal Edri commented on OVIRT-2664: -- I'm not sure I agree with the reason for not finding regressions due to the job, the failure was reported on rhev-devel list, with specific relevant people in the 'to' field, including you Nir, on the 23/1. Also, developers are often capable and mindful people and should be aware which version they are testing, regardless of the default values. The default is usually set for the last stable release, hence it was 4.2, I agree it should be the master if its much more common now ( probably 4.3 more relevant once its out ). I sent a patch to update the default to 'master' https://gerrit.ovirt.org/#/c/97451/1/jobs/confs/yaml/parmeters/ost-version-selector-ovirt.yaml > OST runs engine 4.2 by default, misleading developers > - > > Key: OVIRT-2664 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2664 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Nir Soffer >Assignee: infra > > When creating OST manual job, the UI select engine version 4.2 by default: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/build?delay=0sec > A developer that want to test engine master must change the version > manually. > I you forget to change the version, or just do not notice that there is > engine > version to choose, your job may succeed when it actually fail with engine > master. > Watching other developers start OST jobs, they do not notice that engine > version must be selected, and treat it as the other options that most people > do not care about. > This is probably the reason why OST was broken for a week, and nobody > complained about it, since default build used engine 4.2. > How to fix: > - The UI must be changed to require engine version selection. You cannot > have default for this. > The UI should show something like: > ENGINE_VERSION: [select version] *required > - The "Build" button must be disabled if no version was selected. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/BUMHS47FLAL4FXADYLKZ6IYGMTQ4ARBN/
