November 2017 - Infra - oVirt List Archives

Mailing-Lists upgrade
by Marc Dequènes (Duck) 10 May '18

10 May '18

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --IfGqXrbgT9wNNdIsvS8kI8WdhEQHlgkiq Content-Type: multipart/mixed; boundary="AUFHCWPQQknM84fF2kF4uGjIv4blC9bMv"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com> To: oVirt Infra <infra(a)ovirt.org>, users <users(a)ovirt.org>, devel <devel(a)ovirt.org> Message-ID: <c5c71fce-0290-e97a-ddd0-eab0e6fccea4(a)redhat.com> Subject: Mailing-Lists upgrade --AUFHCWPQQknM84fF2kF4uGjIv4blC9bMv Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Quack, On behalf of the oVirt infra team, I'd like to announce the current Mailing-Lists system is going to be upgraded to a brand new Mailman 3 installation on Monday during the slot 11:00-12:00 JST. It should not take a full hour to migrate as we already made incremental synchronization with the current system but better keep some margin. The system will then take over delivery of the mails but might be a bit slow at first as it needs to reindex all the archived mails (which might take a few hours). To manage your subscriptions and delivery settings you can do this easily on the much nicer web interface (https://lists.ovirt.org) There is a notion of account so you don't need to login separately for each ML.= You can Sign In using Fedora, GitHub or Google or create a local account if you prefer. Please keep in mind signing in with a different method would create separate accounts (which cannot be merged at the moment). But you can easily link your account to other authentication methods in your settings (click on you name in the up-right corner -> Account -> Account Connections). As for the original mail archives, because the previous system did not have stable URLs, we cannot create mappings to the new pages. We decided to keep the old archives around on the same URL (/pipermail), so the Internet links would still work fine. Hope you'd be happy with the new system. \_o< --AUFHCWPQQknM84fF2kF4uGjIv4blC9bMv-- --IfGqXrbgT9wNNdIsvS8kI8WdhEQHlgkiq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAlmwx0MACgkQVen596wc RD9LTQ/+LtUncsq9K8D/LX8wqUTd6VyPwAD5UnAk5c3H/2tmyVA0u7FIfhEyPsXs Z//LE9FEneTDqDVRi1Dw9I54K0ZwxPBemi71dXfwgBI7Ay0ezkbLWrA168Mt9spE tHAODEuxPt2to2aqaS4ujogrkp/gvEP8ILoxPEqoTPCJ/eDTPAu/I1a2JzjMPK3n 2BBS6D8z0TLAf7w1n72TsgX2QzJW57ig/0HELyjvat2/K8V3HSrkwiKlsdULQDWe zB+aMde7r6UoyVKHqlu4asTl2tU/lGZ+e31Hd9Bnx1/oZOJdzslGOhEo9Qoz6763 AHWU9LKiK4NtxYHj2UQTWhndr8PiTtTmR73eIDmkb0cuRXxzjl9VQbwYJ0Kbrmfp attTqpc2CnEojTNXUUNSmNxotZoYXZiX8ZvjPfSgRVr15TUYujzlOfG+lUynbQMV 9rQ9/m58wgwYUymMpOIsRGaIcAKzjm+WpuuVnO+bS2AfmcBkGMQRoIhfV+3SkS8q kT9cDXgcDZOzVFcnZZB4EjbycMcPgZDcoHxU88VdYH+jFJYvvb21esgswVF/wJ2Z uEI/chp4+ADaQhl8ehZNWMSZq125v6SeirPhBNgLG7zFVZI1S9Tm/6qFmH+ajQY7 nCk1X9HZlB1ubex1X+HibRz9QKOilkMgkADyJ4yMDckwYj93sx0= =l6uN -----END PGP SIGNATURE----- --IfGqXrbgT9wNNdIsvS8kI8WdhEQHlgkiq--

5 11

OST Networking suite -- artifacts aren't collected.
by Leon Goldberg 13 Dec '17

13 Dec '17

Hey guys, I have a weird problem with our new OST suite. Although I copy certain directories to ../ovirt-system-tests/exported-artifacts (i.e. root dir/exported-artifacts), they are not being collected. Running the suite via mock, I can see that the directory is present with the logs (plus some other files/directories), however in CI they are not. I've tried running both run_suite.sh and check-patch.sh. Locally I see the artifacts in both. Here's the patch [1]. It's unfinished work. I am familiar with lago's abstraction, and although is super ugly, the relative path in _collect_artifacts seems correct. Thanks for any help! [1] https://gerrit.ovirt.org/#/c/84567/

2 3

Default assignee for bugzilla component
by Sahina Bose 06 Dec '17

06 Dec '17

Hi! Could you change the default assignee on Product: cockpit-ovirt Component:gdeploy to godas(a)redhat.com? thanks sahina

3 3

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 109 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Dec '17

01 Dec '17

------=_Part_177_1970059064.1512056396706 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build Number: 109 Build Status: Failure Triggered By: Started by user Sandro Bonazzola ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #109 [Yuval Turgeman] automation: install vm from iso ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_177_1970059064.1512056396706--

1 1

[CQ]: 84977, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Nov '17

30 Nov '17

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

1 0

[CQ]: 84976, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Nov '17

30 Nov '17

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

1 0

[CQ]: 84970,1 (ovirt-live) failed "ovirt-4.1" system tests
by oVirt Jenkins 30 Nov '17

30 Nov '17

Change 84970,1 (ovirt-live) is probably the reason behind recent system test failures in the "ovirt-4.1" 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/84970/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1416/

1 0

[CQ]: 84870, 2 (ovirt-optimizer) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Nov '17

30 Nov '17

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

1 0

[oVirt Jenkins] standard-enqueue - Build #7672 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 30 Nov '17

30 Nov '17

------=_Part_183_1844004221.1512067091106 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Build: http://jenkins.ovirt.org/job/standard-enqueue/7672/ Build Name: #7672 Build Description: Gerrit: 84870 - ovirt-optimizer (4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/84870 - title: Preparing for next development iteration - project: ovirt-optimizer - branch: master - author: Martin Siv=C3=A1k <msivak(a)redhat.com> ------=_Part_183_1844004221.1512067091106--

1 0

[CQ]: 84970,1 (ovirt-live) failed "ovirt-4.1" system tests
by oVirt Jenkins 30 Nov '17

30 Nov '17

Change 84970,1 (ovirt-live) is probably the reason behind recent system test failures in the "ovirt-4.1" 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/84970/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1413/

1 0