January 2019 - Infra - oVirt List Archives

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 31 Jan '19

31 Jan '19

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.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 31 Jan '19

31 Jan '19

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.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 31 Jan '19

31 Jan '19

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.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 31 Jan '19

31 Jan '19

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.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 31 Jan '19

31 Jan '19

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.

1 0

[CQ]: 97391,4 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 31 Jan '19

31 Jan '19

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/

1 0

[JIRA] (OVIRT-2665) certbot broken on engine-phx
by Evgheni Dereveanchin (oVirt JIRA) 31 Jan '19

31 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2665?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-2665) certbot broken on engine-phx
by Evgheni Dereveanchin (oVirt JIRA) 31 Jan '19

31 Jan '19

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)

1 0

[JIRA] (OVIRT-2664) OST runs engine 4.2 by default, misleading developers
by Eyal Edri (oVirt JIRA) 31 Jan '19

31 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2664?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-2664) OST runs engine 4.2 by default, misleading developers
by Eyal Edri (oVirt JIRA) 31 Jan '19

31 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2664?page=com.atlassian.jira.… ] 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-… > 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)

1 0