April 2020 - Infra - oVirt List Archives

[CQ]: 108654,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 29 Apr '20

29 Apr '20

Change 108654,3 (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/108654/3 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23407/

1 0

[JIRA] (OVIRT-2917) Vagrant VM container
by Ales Musil (oVirt JIRA) 29 Apr '20

29 Apr '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.… ] Ales Musil commented on OVIRT-2917: ----------------------------------- No, vagrant is not going to be used. The original question was if we can use CI container that runs vagrant VM. Because this option is not good idea as we were told, we would like to have privileged container running directly on CI. As requested here is list of services that we run in container: UNIT LOAD ACTIVE SUB DESCRIPTION dbus.service loaded active running D-Bus System Message Bus NetworkManager.service loaded active running Network Manager selinux-autorelabel-mark.service loaded active exited Mark the need to relabel after reboot systemd-journald.service loaded active running Journal Service systemd-resolved.service loaded active running Network Name Resolution systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories systemd-udevd.service loaded active running udev Kernel Device Manager LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 7 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. > Vagrant VM container > -------------------- > > Key: OVIRT-2917 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Ales Musil > Assignee: infra > > Hi, > is there any documentation on how to use the new container backend with the > CI container that spawns VM for privileged operations? > Thank you. > Regards, > Ales > -- > Ales Musil > Software Engineer - RHV Network > Red Hat EMEA <https://www.redhat.com> > amusil(a)redhat.com IM: amusil > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125)

1 0

[JIRA] (OVIRT-2917) Vagrant VM container
by Evgheni Dereveanchin (oVirt JIRA) 29 Apr '20

29 Apr '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2917: --------------------------------------------- I’m not sure why the container would need these features if Vagrant is also going to be used: I would expect all tests to run inside the Vagrant VM, not on the container. The privileged part is only needed to start the VM. Please correct me if I’m wrong. > Vagrant VM container > -------------------- > > Key: OVIRT-2917 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Ales Musil > Assignee: infra > > Hi, > is there any documentation on how to use the new container backend with the > CI container that spawns VM for privileged operations? > Thank you. > Regards, > Ales > -- > Ales Musil > Software Engineer - RHV Network > Red Hat EMEA <https://www.redhat.com> > amusil(a)redhat.com IM: amusil > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125)

1 0

[JIRA] (OVIRT-2917) Vagrant VM container
by Anton Marchukov (oVirt JIRA) 29 Apr '20

29 Apr '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2917: ---------------------------------------- [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] any updates here? Seems like we do not have any evident side effect but as usual we can have it unexpectedly by some system component such as firewalld or so? I think if we can filter out all known causes of modules being unloaded and make sure they do not have it we can go ahead and try. This is because we do not have any alternative solution yet unfortunately. > Vagrant VM container > -------------------- > > Key: OVIRT-2917 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2917 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Ales Musil > Assignee: infra > > Hi, > is there any documentation on how to use the new container backend with the > CI container that spawns VM for privileged operations? > Thank you. > Regards, > Ales > -- > Ales Musil > Software Engineer - RHV Network > Red Hat EMEA <https://www.redhat.com> > amusil(a)redhat.com IM: amusil > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125)

1 0

[CQ]: 108665, 2 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Apr '20

29 Apr '20

A system test invoked by the "ovirt-4.3" change queue including change 108665,2 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 108560,4 (ovirt-system-tests) 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 108560,4 (ovirt-system-tests) 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/108665/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108560/4 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3320/

1 0

[CQ]: 108661, 4 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Apr '20

29 Apr '20

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

1 0

[CQ]: 108686, 2 (ovirt-engine-nodejs-modules) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Apr '20

29 Apr '20

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

1 0

[CQ]: 108659, 1 (ovirt-engine-nodejs-modules) failed "ovirt-4.3" system tests
by oVirt Jenkins 29 Apr '20

29 Apr '20

Change 108659,1 (ovirt-engine-nodejs-modules) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/108659/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3315/

1 0

[oVirt Jenkins] cleanup-gated-dummy-master - Build #130 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Apr '20

29 Apr '20

Build: https://jenkins.ovirt.org/job/cleanup-gated-dummy-master/130/ Build Name: #130 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

oVirt infra daily report - unstable production jobs - 1175
by jenkins＠jenkins.phx.ovirt.org 29 Apr '20

29 Apr '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1175//artifact/exported… Cheers, Jenkins

1 0