- Infra - oVirt List Archives

[JIRA] (OVIRT-2182) Create timed jobs
by eyal edri (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2182?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2182: ----------------------------- Epic Link: OVIRT-2177 > Create timed jobs > ----------------- > > Key: OVIRT-2182 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2182 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gal Ben Haim > Assignee: infra > > The timed jobs should use fc28 mock, so we will also test ovirt engine SDK. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2182) Create timed jobs
by eyal edri (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2182?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2182: ----------------------------- Epic Link: OVIRT-2177 > Create timed jobs > ----------------- > > Key: OVIRT-2182 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2182 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gal Ben Haim > Assignee: infra > > The timed jobs should use fc28 mock, so we will also test ovirt engine SDK. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2182) Create timed jobs
by eyal edri (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2182?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2182: ----------------------------- Issue Type: Task (was: Sub-task) Parent: (was: OVIRT-2177) > Create timed jobs > ----------------- > > Key: OVIRT-2182 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2182 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gal Ben Haim > Assignee: infra > > The timed jobs should use fc28 mock, so we will also test ovirt engine SDK. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2181) Release lago-ovirt for fc28
by eyal edri (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2181?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2181: ----------------------------- Epic Link: OVIRT-2177 > Release lago-ovirt for fc28 > --------------------------- > > Key: OVIRT-2181 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2181 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2181) Release lago-ovirt for fc28
by eyal edri (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2181?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2181: ----------------------------- Epic Link: OVIRT-2177 > Release lago-ovirt for fc28 > --------------------------- > > Key: OVIRT-2181 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2181 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2181) Release lago-ovirt for fc28
by eyal edri (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2181?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2181: ----------------------------- Issue Type: Task (was: Sub-task) Parent: (was: OVIRT-2177) > Release lago-ovirt for fc28 > --------------------------- > > Key: OVIRT-2181 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2181 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2032) Mounting device files prevents using systemd-nspawn in mock
by Barak Korren (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2032?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2032: ------------------------------------- The fix was included in mock-1.4.10 which was already released to EPEL: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-28fdd00a4b > Mounting device files prevents using systemd-nspawn in mock > ----------------------------------------------------------- > > Key: OVIRT-2032 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2032 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: upstream-issue > > The systemd-nspawn functionality in mock is introduced in OVIRT-2031. > When using systemd-nspawn mock uses some kind of a layered FS that is created when it starts and removed when it exits. This is different from the way it works when using chroot where the directory that the chroot is configured in stays around until it is explicitly removed. > mock had an issue where if you tried to bind-mount something into the mock environment, you had to have the mount point ready for it. We worked around this in {{mock_runner}} by using the fact the chroot was persistent, going into it and setting up the mount points as needed before actually starting to use it to run the STDCI script. > Since the mock authors were aware of the issue when the implemented the systemd-nspawn functionality, they made mock pre-create mount point in the container as needed. However, they only supported directory mount points, so if we tried to bind-mount a socket we would get en error message failing to mount a socket file on a directory. > We reported this issue to the mock developers as issue [#87|https://github.com/rpm-software-management/mock/issues/87] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2166) Python's HTTP server is overloaded
by Gal Ben Haim (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2166?page=com.atlassian.jira.… ] Gal Ben Haim reassigned OVIRT-2166: ----------------------------------- Assignee: Gal Ben Haim (was: infra) > Python's HTTP server is overloaded > ---------------------------------- > > Key: OVIRT-2166 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2166 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: Gal Ben Haim > > When running `lago ovirt deploy` we experience the following error: > ``` > 08:23:24 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: Success (in 0:00:20) > 08:23:25 [basic-suit] Traceback (most recent call last): > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/SocketServer.py", line 295, in _handle_request_noblock > 08:23:25 [basic-suit] self.process_request(request, client_address) > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/SocketServer.py", line 321, in process_request > 08:23:25 [basic-suit] self.finish_request(request, client_address) > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/SocketServer.py", line 334, in finish_request > 08:23:25 [basic-suit] self.RequestHandlerClass(request, client_address, self) > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/SocketServer.py", line 651, in __init__ > 08:23:25 [basic-suit] self.finish() > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/SocketServer.py", line 710, in finish > 08:23:25 [basic-suit] self.wfile.close() > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/socket.py", line 279, in close > 08:23:25 [basic-suit] self.flush() > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/socket.py", line 303, in flush > 08:23:25 [basic-suit] self._sock.sendall(view[write_offset:write_offset+buffer_size]) > 08:23:25 [basic-suit] error: [Errno 32] Broken pipe > ``` > It seems like `yum` on the VMs close the connection to the internal repo because it's too slow. > This error doesn't fail OST, just pollute its log. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2166) Python's HTTP server is overloaded
by Gal Ben Haim (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2166?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2166: -------------------------------- Status: In Progress (was: To Do) > Python's HTTP server is overloaded > ---------------------------------- > > Key: OVIRT-2166 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2166 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > When running `lago ovirt deploy` we experience the following error: > ``` > 08:23:24 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: Success (in 0:00:20) > 08:23:25 [basic-suit] Traceback (most recent call last): > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/SocketServer.py", line 295, in _handle_request_noblock > 08:23:25 [basic-suit] self.process_request(request, client_address) > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/SocketServer.py", line 321, in process_request > 08:23:25 [basic-suit] self.finish_request(request, client_address) > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/SocketServer.py", line 334, in finish_request > 08:23:25 [basic-suit] self.RequestHandlerClass(request, client_address, self) > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/SocketServer.py", line 651, in __init__ > 08:23:25 [basic-suit] self.finish() > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/SocketServer.py", line 710, in finish > 08:23:25 [basic-suit] self.wfile.close() > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/socket.py", line 279, in close > 08:23:25 [basic-suit] self.flush() > 08:23:25 [basic-suit] File "/usr/lib64/python2.7/socket.py", line 303, in flush > 08:23:25 [basic-suit] self._sock.sendall(view[write_offset:write_offset+buffer_size]) > 08:23:25 [basic-suit] error: [Errno 32] Broken pipe > ``` > It seems like `yum` on the VMs close the connection to the internal repo because it's too slow. > This error doesn't fail OST, just pollute its log. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

CI fails on network.ip_address_test.TestAddressSetup
by Ala Hino 11 Jun '18

11 Jun '18

Is it a known issue? Below is the traceback: *07:52:14* ======================================================================*07:52:14* ERROR: test_add_ipv6_gateway_given_existing_ipv4_and_ipv6_gateways (network.ip_address_test.TestAddressSetup)*07:52:14* ----------------------------------------------------------------------*07:52:14* Traceback (most recent call last):*07:52:14* File "/home/jenkins/workspace/vdsm_master_check-patch-fc27-x86_64/vdsm/tests/network/ip_address_test.py", line 146, in test_add_ipv6_gateway_given_existing_ipv4_and_ipv6_gateways*07:52:14* address.add(nic, ipv4=None, ipv6=ipv6)*07:52:14* File "/home/jenkins/workspace/vdsm_master_check-patch-fc27-x86_64/vdsm/lib/vdsm/network/ip/address/__init__.py", line 278, in add*07:52:14* _add_ipv6_address(iface, ipv6)*07:52:14* File "/home/jenkins/workspace/vdsm_master_check-patch-fc27-x86_64/vdsm/lib/vdsm/network/ip/address/__init__.py", line 294, in _add_ipv6_address*07:52:14* ipwrapper.addrAdd(iface, ipv6addr, ipv6netmask, family=6)*07:52:14* File "/home/jenkins/workspace/vdsm_master_check-patch-fc27-x86_64/vdsm/lib/vdsm/network/ipwrapper.py", line 574, in addrAdd*07:52:14* _exec_cmd(command)*07:52:14* File "/home/jenkins/workspace/vdsm_master_check-patch-fc27-x86_64/vdsm/lib/vdsm/network/ipwrapper.py", line 495, in _exec_cmd*07:52:14* raise exc(returnCode, error.splitlines())*07:52:14* vdsm.network.ipwrapper.IPRoute2Error: (2, ['RTNETLINK answers: Permission denied']) Link to CI console: https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/3750/cons…

2 2

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

11 Jun '18

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

1 0

[JIRA] (OVIRT-2055) failure in suspend resume vm not related to reported change - need to investigate
by Dafna Ron (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2055?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2055: ---------------------------------- [~gbenhaim(a)redhat.com] > failure in suspend resume vm not related to reported change - need to investigate > --------------------------------------------------------------------------------- > > Key: OVIRT-2055 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2055 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > I think the issue is on qemu/libvirt changed queries: > https://pastebin.com/afyeUAcT > https://pastebin.com/va20Y5Hp > checking his with vdsm people. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2149) broken pipe error on lago
by Dafna Ron (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2149?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2149: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > broken pipe error on lago > ------------------------- > > Key: OVIRT-2149 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2149 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_lago > > I have been seeing his in several places and on my own laptop. I don't think it actully causes anything but [~gbenhaim(a)redhat.com] can you please take a look? > http://pastebin.test.redhat.com/600659 > you can see it here: http://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1143/c… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2149) broken pipe error on lago
by Dafna Ron (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2149?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2149: ---------------------------------- ticket was opened to track this issue in lago. closing > broken pipe error on lago > ------------------------- > > Key: OVIRT-2149 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2149 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_lago > > I have been seeing his in several places and on my own laptop. I don't think it actully causes anything but [~gbenhaim(a)redhat.com] can you please take a look? > http://pastebin.test.redhat.com/600659 > you can see it here: http://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1143/c… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2159) ovirt-ansible-manageiq build jobs not triggered
by Dafna Ron (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2159?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2159: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > ovirt-ansible-manageiq build jobs not triggered > ----------------------------------------------- > > Key: OVIRT-2159 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2159 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_build-arifacts, ost_failures, ost_infra > > https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-manageiq_standard-on-ghpu… > shows no build job triggered. Can you please fix it? > Thanks, -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2160) ovirt-ansible-disaster-recovery build jobs not triggered
by Dafna Ron (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2160?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2160: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > ovirt-ansible-disaster-recovery build jobs not triggered > -------------------------------------------------------- > > Key: OVIRT-2160 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2160 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_build-arifacts, ost_failures, ost_infra > > https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-disaster-recovery_standar… > shows no build job triggered. Can you please fix it? > Thanks, -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

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

11 Jun '18

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

1 0

[JIRA] (OVIRT-2180) Missing packages when trying to create reposync-config ovirt-master on Fedora 28
by Gal Ben Haim (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2180?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2180: ------------------------------------- [~sbonazzo(a)redhat.com] Any idea how to solve the deps issue? > Missing packages when trying to create reposync-config ovirt-master on Fedora 28 > -------------------------------------------------------------------------------- > > Key: OVIRT-2180 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2180 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > When trying to create reposync-config for ovirt-master on FC28 the following packges are missing: > {code:java} > Error: > Problem 1: conflicting requests > - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180308070539.git35a6428.fc28.x86_64 > - package ovirt-host-4.3.0-0.0.master.20180530065728.git836691d.fc28.s390x does not have a compatible architecture > - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180530070102.git836691d.fc28.x86_64 > - package ovirt-host-4.3.0-0.0.master.20180604121623.git6aeb275.fc28.s390x does not have a compatible architecture > - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180604121713.git6aeb275.fc28.x86_64 > - package ovirt-host-4.3.0-0.0.master.20180607122548.gitbdfe919.fc28.s390x does not have a compatible architecture > - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180607122828.gitbdfe919.fc28.x86_64 > Problem 2: conflicting requests > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180306070711.git2d3047c73c.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180530170515.git426823eb4a1.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601113423.git27f22ec3801.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601125541.gita6e87e15f8e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601151553.git588d48026c5.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603153247.git23ea19a71b9.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603185407.git60b31ae4ff6.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603200841.git0b63d547fb2.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604071126.git524908b0e26.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604084747.git8b9ad6a435e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604135226.git3e394fa5ef3.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180607083125.git21907ef1790.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608075105.gitff92e12aed8.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608115732.gita4bbacb7277.fc28.noarch > Problem 3: conflicting requests > - package ovirt-engine-extension-aaa-ldap-setup-1.3.8-0.0.master.gitf069cb9.fc28.noarch requires ovirt-engine >= 3.6, but none of the providers can be installed > - package ovirt-engine-extension-aaa-ldap-setup-1.3.8-0.0.master.gitff6678b.fc28.noarch requires ovirt-engine >= 3.6, but none of the providers can be installed > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180306070711.git2d3047c73c.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180530170515.git426823eb4a1.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601113423.git27f22ec3801.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601125541.gita6e87e15f8e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601151553.git588d48026c5.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603153247.git23ea19a71b9.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603185407.git60b31ae4ff6.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603200841.git0b63d547fb2.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604071126.git524908b0e26.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604084747.git8b9ad6a435e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604135226.git3e394fa5ef3.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180607083125.git21907ef1790.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608075105.gitff92e12aed8.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608115732.gita4bbacb7277.fc28.noarch > Problem 4: conflicting requests > - package ovirt-engine-extension-aaa-ldap-1.3.8-0.0.master.gitf069cb9.fc28.noarch requires ovirt-engine >= 3.5, but none of the providers can be installed > - package ovirt-engine-extension-aaa-ldap-1.3.8-0.0.master.gitff6678b.fc28.noarch requires ovirt-engine >= 3.5, but none of the providers can be installed > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180306070711.git2d3047c73c.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180530170515.git426823eb4a1.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601113423.git27f22ec3801.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601125541.gita6e87e15f8e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601151553.git588d48026c5.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603153247.git23ea19a71b9.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603185407.git60b31ae4ff6.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603200841.git0b63d547fb2.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604071126.git524908b0e26.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604084747.git8b9ad6a435e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604135226.git3e394fa5ef3.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180607083125.git21907ef1790.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608075105.gitff92e12aed8.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608115732.gita4bbacb7277.fc28.noarch > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2153) Fedora 28 ppc64le support
by Ondra Machacek (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2153?page=com.atlassian.jira.… ] Ondra Machacek commented on OVIRT-2153: --------------------------------------- I am not aware anyone using it, so I think we don't have to do it now. Let's do it once someone request it. > Fedora 28 ppc64le support > ------------------------- > > Key: OVIRT-2153 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2153 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: sbonazzo > Assignee: infra > > Hi, > I see python-ovirt-engine-sdk4 failing on ppc64le for fc28 due to: "Unable > to find mock env" error. > I tend to think we should have ppc64le for fedora 28 but I see that mock > config are missing in jenkins and also the mirroring of the repos for > fedora 28 ppc64le are missing. > We should either drop ppc64le jobs for fc28 or add support for it. Adding > Ondra to share his thoughts on this. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1880) Manage bare metals with beaker
by Barak Korren (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1880?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1880: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) We're not going to use Beaker directly, we'll use CentOS CI and Duffy instead. > Manage bare metals with beaker > ------------------------------ > > Key: OVIRT-1880 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1880 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > There are multiple reasons why we may want to manage our bare-metal slaves with [beaker|https://beaker-project.org/] > * It will allow us to have auto-reprovisioning for them, perhaps even after every job > * It will allow us to scale up to multiple jenkins masters while sharing host resources > * If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself. > There are probably multiple pieces of work to be carried out here, each will be tracked in a different ticket that will be set as a blocker to this ticket. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1885) Remove slave/resource management from Jenkins
by Barak Korren (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1885?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1885: ------------------------------------- Removing OVIRT-1880 as a blocker and adding OVIRT-2178 as we're probably not going to use beaker directly for B.M. slaves and instead rely on CentOS CI and Duffy. > Remove slave/resource management from Jenkins > --------------------------------------------- > > Key: OVIRT-1885 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1885 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > Labels: scale > > The way out infra is configure right now, resource allocation and management is done by Jenkins itself. This means that all resources need to pre-allocated to Jenkins in the form of slaves. > If we want to have separate Jenkins masters, our current configuration will force us to hard-split the resources between different Jenkins masters. > If we want to share our pool of resources between multiple masters, it means that resource allocation needs to move out of Jenkins to external tools. > Potential tools for different types of resources are: > * Beaker for managing physical hosts > * oVirt + a Jenkins could provider plugin for managing VMs > * OpenShift for managing containers (As a replacement for chroots). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2173) STDCI build summary to include details about the STDCI event
by Barak Korren (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2173?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2173: ------------------------------------- Need to be clearer on this - we need to show what was the exact event - was a commit pushed to the branch? Was a new PR submitted? Was a PR or a patch merged? Was it simpy a comment on the PR/patch? > STDCI build summary to include details about the STDCI event > ------------------------------------------------------------ > > Key: OVIRT-2173 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2173 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to have quick view of the event details such as who is the change owner, what branch it was pushed to, and etc so I won't have to extract this information from the SCM. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2186) Auto-update the distribution-gpg-keys package on the mirrors server
by Barak Korren (oVirt JIRA) 11 Jun '18

11 Jun '18

Barak Korren created OVIRT-2186: ----------------------------------- Summary: Auto-update the distribution-gpg-keys package on the mirrors server Key: OVIRT-2186 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2186 Project: oVirt - virtualization made easy Issue Type: Improvement Components: CI Mirrors Reporter: Barak Korren Assignee: infra Have the mirror sync job auto-update the distribution-gpg-keys package on the mirrors server so that issues like OVIRT-1298 do not occur. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 248 - Failure!
by jenkins＠jenkins.phx.ovirt.org 10 Jun '18

10 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/248/ Build Number: 248 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #248 [Eitan Raviv] network: introduce wait for 'powering up' or 'up' ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1448: -------------------------------- Epic Link: OVIRT-2184 (was: OVIRT-400) > Enable devs to specifiy patch dependencies for OST > -------------------------------------------------- > > Key: OVIRT-1448 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency. > What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged. > The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test. > The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies. > We would probably want to adopt OpenStack's convention here. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1448: -------------------------------- Epic Link: OVIRT-2184 (was: OVIRT-400) > Enable devs to specifiy patch dependencies for OST > -------------------------------------------------- > > Key: OVIRT-1448 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency. > What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged. > The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test. > The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies. > We would probably want to adopt OpenStack's convention here. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1462) Generate more detailed output from change-queue tests
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1462?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1462: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Generate more detailed output from change-queue tests > ----------------------------------------------------- > > Key: OVIRT-1462 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1462 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > The change-queue tester jobs can have some additional information that may be useful for understanding issues but is not reported anywhere ATM. > This information includes: > # If the test failed because a build job failed, and which build job made it fail. > # If the test failed during OST run, which suits failed. > This information should, at least, be presented in the test results screen, but may also be preserved and included in the email or Gerrit notifications about failing changes. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1462) Generate more detailed output from change-queue tests
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1462?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1462: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Generate more detailed output from change-queue tests > ----------------------------------------------------- > > Key: OVIRT-1462 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1462 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > The change-queue tester jobs can have some additional information that may be useful for understanding issues but is not reported anywhere ATM. > This information includes: > # If the test failed because a build job failed, and which build job made it fail. > # If the test failed during OST run, which suits failed. > This information should, at least, be presented in the test results screen, but may also be preserved and included in the email or Gerrit notifications about failing changes. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1504) Include more patch information in CQ jobs output
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1504?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1504: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Include more patch information in CQ jobs output > ------------------------------------------------ > > Key: OVIRT-1504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1504 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > It would be useful to include more information about checked patches in the UI of the CQ jobs and in email messages generated by them. > The information to include would be: > # The patch commit message > # The patch Git SHA > # The Gerrit change ID > The information should be included in: > # The email messages sent by the change queue > # As a popup text when clicking or hovering over an icon that will be displayed for the job build in the build history. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1504) Include more patch information in CQ jobs output
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1504?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1504: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Include more patch information in CQ jobs output > ------------------------------------------------ > > Key: OVIRT-1504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1504 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > It would be useful to include more information about checked patches in the UI of the CQ jobs and in email messages generated by them. > The information to include would be: > # The patch commit message > # The patch Git SHA > # The Gerrit change ID > The information should be included in: > # The email messages sent by the change queue > # As a popup text when clicking or hovering over an icon that will be displayed for the job build in the build history. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2185) Improve CQ output for faster debugging
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

Barak Korren created OVIRT-2185: ----------------------------------- Summary: Improve CQ output for faster debugging Key: OVIRT-2185 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2185 Project: oVirt - virtualization made easy Issue Type: Epic Components: Change Queue Reporter: Barak Korren Assignee: infra As a CI/Ovirt infra team member I want reports from the change-queue to include all the information that is required to analyse, report and track the issues that it detects. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1504) Include more patch information in CQ jobs output
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1504?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1504: -------------------------------- Component/s: (was: oVirt CI) Change Queue > Include more patch information in CQ jobs output > ------------------------------------------------ > > Key: OVIRT-1504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1504 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > It would be useful to include more information about checked patches in the UI of the CQ jobs and in email messages generated by them. > The information to include would be: > # The patch commit message > # The patch Git SHA > # The Gerrit change ID > The information should be included in: > # The email messages sent by the change queue > # As a popup text when clicking or hovering over an icon that will be displayed for the job build in the build history. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1427) Dependencies between ovirt-engine and vdsm-jsonrpc-java
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1427?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1427: -------------------------------- Component/s: Change Queue > Dependencies between ovirt-engine and vdsm-jsonrpc-java > ------------------------------------------------------- > > Key: OVIRT-1427 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1427 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue > Reporter: Piotr Kliczewski > Assignee: infra > > Recently we had and issue that newer version of vdsm-jsonrpc-java was > available but engine spec was not updated yet. Engine patch contained spec > and module.xml changes which provided dependencies required by new version > of jsonrpc. CI used the new version of jsonrpc without engine patch being > merged which caused several issues. > This ticket is open to track how we could mitigate similar issues in the > future. > Thanks, > Piotr -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1498) Gate lago versions with change-queue
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1498?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1498: -------------------------------- Component/s: Lago > Gate lago versions with change-queue > ------------------------------------ > > Key: OVIRT-1498 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1498 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue, Lago > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gating, lago, ost > > Lago should be considered an upstream dependency, like CentOS and libvirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1498) Gate lago versions with change-queue
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1498?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1498: -------------------------------- Component/s: (was: oVirt CI) Change Queue > Gate lago versions with change-queue > ------------------------------------ > > Key: OVIRT-1498 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1498 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gating, lago, ost > > Lago should be considered an upstream dependency, like CentOS and libvirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1498) Gate lago versions with change-queue
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1498?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1498: -------------------------------- Epic Link: OVIRT-2184 (was: OVIRT-400) > Gate lago versions with change-queue > ------------------------------------ > > Key: OVIRT-1498 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1498 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gating, lago, ost > > Lago should be considered an upstream dependency, like CentOS and libvirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1498) Gate lago versions with change-queue
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1498?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1498: -------------------------------- Epic Link: OVIRT-2184 (was: OVIRT-400) > Gate lago versions with change-queue > ------------------------------------ > > Key: OVIRT-1498 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1498 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gating, lago, ost > > Lago should be considered an upstream dependency, like CentOS and libvirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1427) Dependencies between ovirt-engine and vdsm-jsonrpc-java
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1427?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1427: -------------------------------- Epic Link: OVIRT-2184 (was: OVIRT-400) > Dependencies between ovirt-engine and vdsm-jsonrpc-java > ------------------------------------------------------- > > Key: OVIRT-1427 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1427 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Piotr Kliczewski > Assignee: infra > > Recently we had and issue that newer version of vdsm-jsonrpc-java was > available but engine spec was not updated yet. Engine patch contained spec > and module.xml changes which provided dependencies required by new version > of jsonrpc. CI used the new version of jsonrpc without engine patch being > merged which caused several issues. > This ticket is open to track how we could mitigate similar issues in the > future. > Thanks, > Piotr -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1427) Dependencies between ovirt-engine and vdsm-jsonrpc-java
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1427?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1427: -------------------------------- Epic Link: OVIRT-2184 (was: OVIRT-400) > Dependencies between ovirt-engine and vdsm-jsonrpc-java > ------------------------------------------------------- > > Key: OVIRT-1427 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1427 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Piotr Kliczewski > Assignee: infra > > Recently we had and issue that newer version of vdsm-jsonrpc-java was > available but engine spec was not updated yet. Engine patch contained spec > and module.xml changes which provided dependencies required by new version > of jsonrpc. CI used the new version of jsonrpc without engine patch being > merged which caused several issues. > This ticket is open to track how we could mitigate similar issues in the > future. > Thanks, > Piotr -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1162) Make sure cron failure email from resources.ovirt.org reach the infra list
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1162?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1162: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) Failures by the publisher cron jobs are now detected by the publisher Jenkins jobs > Make sure cron failure email from resources.ovirt.org reach the infra list > -------------------------------------------------------------------------- > > Key: OVIRT-1162 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1162 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: High > > There are quite a few things that run there with cron and we need to know when they fail. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2184) Full change isulation for CQ/OST
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

Barak Korren created OVIRT-2184: ----------------------------------- Summary: Full change isulation for CQ/OST Key: OVIRT-2184 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2184 Project: oVirt - virtualization made easy Issue Type: Epic Components: Change Queue Reporter: Barak Korren Assignee: infra As an ovirt developer i want to know that failures in OST can be narrowed down to a single change regardless of the source this change came from. h3. Acceptance Criteria # All change sources that can affect OST outcome are monitored and can be isolated by CQ including: ## Patches to oVirt packages ## Patches to OST ## Changes to Lago ## Changes to platform (non-oVirt) packages ## Changes to the CI infrastructure -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1396) Add a new 'test-system-artifacts' Standard-CI stage
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1396?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1396: ---------------------------------- probably need grooming and updating to match current oVirt CI capabilities. > Add a new 'test-system-artifacts' Standard-CI stage > --------------------------------------------------- > > Key: OVIRT-1396 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1396 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > An order to allow building and testing processes for containers to be triggered after package that are needed for them are built, we will introduce the "{{test-system-artifacts}}" standard-CI stage. > This stage will be invoked from the 'experimental' or 'change-queue-tester' pipelines jost like the existing OST-based flows. > In order to provide package and repo information to the std-CI script invoked by this stage we well need to implement OVIRT-1391 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1396) Add a new 'test-system-artifacts' Standard-CI stage
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1396?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1396: ----------------------------- Priority: Medium (was: High) > Add a new 'test-system-artifacts' Standard-CI stage > --------------------------------------------------- > > Key: OVIRT-1396 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1396 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > An order to allow building and testing processes for containers to be triggered after package that are needed for them are built, we will introduce the "{{test-system-artifacts}}" standard-CI stage. > This stage will be invoked from the 'experimental' or 'change-queue-tester' pipelines jost like the existing OST-based flows. > In order to provide package and repo information to the std-CI script invoked by this stage we well need to implement OVIRT-1391 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1162) Make sure cron failure email from resources.ovirt.org reach the infra list
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1162?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1162: ---------------------------------- [~bkorren(a)redhat.com] can we close this? > Make sure cron failure email from resources.ovirt.org reach the infra list > -------------------------------------------------------------------------- > > Key: OVIRT-1162 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1162 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: High > > There are quite a few things that run there with cron and we need to know when they fail. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-682) Improve CI logging and reporting to Gerrit
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-682: ------------------------------- Resolution: Won't Fix Status: Done (was: To Do) This ticket is overly broad and generic, closing it as we now have more specific tickets for specific aspects of this. > Improve CI logging and reporting to Gerrit > ------------------------------------------ > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: eyal edri > Assignee: infra > Priority: Low > Labels: standard-ci > > On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > Lately vdsm builds are failing in the install packages stage with > > this unhelpful error: > > > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > > 13:59:53 ERROR: Command failed. See logs for output. > > > > I downloaded the logs.tgz file from > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/artifact/exported-artifacts/logs.tgz > > > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > > root.log > > I found found this error: > > > > DEBUG util.py:421: Error: Package: > > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > > (ovirt-snapshot) > > DEBUG util.py:421: Requires: ioprocess = > > 0.17.0-1.201608111609.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.16.1-1.fc24.x86_64 (updates) > > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201607121058.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201608111129.gitbd272f2.fc24 > > > > So we have 2 issues here: > > > > 1. We need *all* errors in the console > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/console > Not sure its possible or easy to do, these errors usually come from mock > and are not relevant to the code running on the console. > I've cc'd infra-support and updated topic to track it and check our options. > Going foward, we might want to install a log collector like logstash and > then searching errors there should be much easier. > > > > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > > the missing ioprocess > > package. > > Maybe the project xml is not correct? > > > > Nir > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-682) Improve CI logging and reporting to Gerrit
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-682: ------------------------------- Summary: Improve CI logging and reporting to Gerrit (was: Improve CI logging and reporting to Gerrit (v2)) > Improve CI logging and reporting to Gerrit > ------------------------------------------ > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: eyal edri > Assignee: infra > Priority: Low > Labels: standard-ci > > On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > Lately vdsm builds are failing in the install packages stage with > > this unhelpful error: > > > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > > 13:59:53 ERROR: Command failed. See logs for output. > > > > I downloaded the logs.tgz file from > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/artifact/exported-artifacts/logs.tgz > > > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > > root.log > > I found found this error: > > > > DEBUG util.py:421: Error: Package: > > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > > (ovirt-snapshot) > > DEBUG util.py:421: Requires: ioprocess = > > 0.17.0-1.201608111609.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.16.1-1.fc24.x86_64 (updates) > > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201607121058.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201608111129.gitbd272f2.fc24 > > > > So we have 2 issues here: > > > > 1. We need *all* errors in the console > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/console > Not sure its possible or easy to do, these errors usually come from mock > and are not relevant to the code running on the console. > I've cc'd infra-support and updated topic to track it and check our options. > Going foward, we might want to install a log collector like logstash and > then searching errors there should be much easier. > > > > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > > the missing ioprocess > > package. > > Maybe the project xml is not correct? > > > > Nir > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1197) Re-factor the standard-CI publishers file
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1197?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1197: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) Since STDCI had been re-implemented with pipeline jobs it no longer makes sense to re-factor the code for FreeStyle jobs. > Re-factor the standard-CI publishers file > ----------------------------------------- > > Key: OVIRT-1197 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1197 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Thi has already been improved as part of OVIRT-988 (in [Gerrit 69194|https://gerrit.ovirt.org/#/c/69194] But there is more work to do. > We can probably have the same publishers macro for all Standard-CI jobs, and add conditional steps to: > # Collect test results if any (OVIRT-449) > # Improve output to Gerrit (OVIRT-682) > # Launch deploy-to-experimental if this is a build-artifacts job and the patch was merged > This way we can finally stop having to have a separate entry for the build-artifacts jobs and simplify the project YAML files. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2183) Automate creation of "poll" jobs
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2183?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2183: -------------------------------- Epic Link: OVIRT-1013 > Automate creation of "poll" jobs > -------------------------------- > > Key: OVIRT-2183 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2183 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: infra > > As a developer I would like to be able to configure upstream source polling jobs (In other works jobs that execute the "poll-upstream-sources" STDCI stage) from the STDCI YAML file in my project so that I never have to deal with JJB or the 'jenkins' repository. > h3. Acceptance Criteria > # To get "poll-upstream-sources" jobs working for a certain branch developers should only configure some setting in the STDCI YAML file of that project. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2183) Automate creation of "poll" jobs
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

Barak Korren created OVIRT-2183: ----------------------------------- Summary: Automate creation of "poll" jobs Key: OVIRT-2183 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2183 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Standard CI (Pipelines) Reporter: Barak Korren Assignee: infra As a developer I would like to be able to configure upstream source polling jobs (In other works jobs that execute the "poll-upstream-sources" STDCI stage) from the STDCI YAML file in my project so that I never have to deal with JJB or the 'jenkins' repository. h3. Acceptance Criteria # To get "poll-upstream-sources" jobs working for a certain branch developers should only configure some setting in the STDCI YAML file of that project. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Description: The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: 1. The platforms a certain project needs to be built and tested on. 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. h3. Acceptance criteria: # The only JJB YAML needed to be written on a per-project basis for full support of all STDCI features is few details to basically enable STDCI support for the project # For most projects the code to be added should be one line with just the project name was: The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: 1. The platforms a certain project needs to be built and tested on. 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. > Automate standard-CI job creation > --------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. > But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. > The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: > 1. The platforms a certain project needs to be built and tested on. > 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. > We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. > h3. Acceptance criteria: > # The only JJB YAML needed to be written on a per-project basis for full support of all STDCI features is few details to basically enable STDCI support for the project > # For most projects the code to be added should be one line with just the project name -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0