- Infra - oVirt List Archives

[CQ]: 103019, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Sep '19

02 Sep '19

A system test invoked by the "ovirt-master" change queue including change 103019,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (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 101913,10 (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/103019/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101913/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15667/

1 0

[CQ]: 102981, 2 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests
by oVirt Jenkins 02 Sep '19

02 Sep '19

Change 102981,2 (ovirt-engine-nodejs-modules) 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/102981/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15664/

1 0

[CQ]: 102939, 7 (ovirt-host-deploy) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Sep '19

02 Sep '19

A system test invoked by the "ovirt-master" change queue including change 102939,7 (ovirt-host-deploy) failed. However, this change seems not to be the root cause for this failure. Change 102372,4 (ovirt-host-deploy) 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 102372,4 (ovirt-host-deploy) 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/102939/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102372/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15661/

1 0

[CQ]: 102838, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Sep '19

02 Sep '19

A system test invoked by the "ovirt-master" change queue including change 102838,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (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 101913,10 (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/102838/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101913/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15657/

1 0

[CQ]: 102235,24 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 02 Sep '19

02 Sep '19

Change 102235,24 (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/102235/24 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15653/

1 0

[CQ]: 66bcd08 (ovirt-web-ui) failed "ovirt-4.2" system tests
by oVirt Jenkins 02 Sep '19

02 Sep '19

Change 66bcd08 (ovirt-web-ui) is probably the reason behind recent system test failures in the "ovirt-4.2" 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://github.com/oVirt/ovirt-web-ui/commit/66bcd087851d4c49f0c7037d599888… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4766/

1 0

[CQ]: 102348, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Sep '19

02 Sep '19

A system test invoked by the "ovirt-master" change queue including change 102348,8 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (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 101913,10 (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/102348/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101913/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15648/

1 0

[JIRA] (OVIRT-2787) connecting to ci slave as developer account
by Eyal Edri (oVirt JIRA) 02 Sep '19

02 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2787?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2787: ---------------------------------- I’m not sure it's possible with the current implementation of Jenkins in KubeVirt. [~accountid:557058:f57f4f3d-a7d2-40b5-8ef1-94b6bbbf8dc7] [~accountid:557058:c4a3432b-f1c1-4620-b53b-c398d6d3a5c2] ? Do you have a link to example job also that you were debugging? > connecting to ci slave as developer account > ------------------------------------------- > > Key: OVIRT-2787 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2787 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Or Shoval > Assignee: infra > > Hi Infra, > sometimes in CNV we are using CI, > and stuff fails, > it would be awesome if we can get a developer profile > that allows to connect in a restricted shell / rbash (idea by Dafna) > in order to execute commands like get pods and describe pods, > that will give hint about the problems > is it possible please ? what it involves > it can reduce lot of time and effort > thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2787) connecting to ci slave as developer account
by Or Shoval (oVirt JIRA) 02 Sep '19

02 Sep '19

Or Shoval created OVIRT-2787: -------------------------------- Summary: connecting to ci slave as developer account Key: OVIRT-2787 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2787 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Or Shoval Assignee: infra Hi Infra, sometimes in CNV we are using CI, and stuff fails, it would be awesome if we can get a developer profile that allows to connect in a restricted shell / rbash (idea by Dafna) in order to execute commands like get pods and describe pods, that will give hint about the problems is it possible please ? what it involves it can reduce lot of time and effort thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[CQ]: 102981, 2 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Sep '19

02 Sep '19

A system test invoked by the "ovirt-4.2" change queue including change 102981,2 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 102923,3 (ovirt-engine-nodejs-modules) 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 102923,3 (ovirt-engine-nodejs- modules) 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/102981/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102923/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4764/

1 0