- Devel - oVirt List Archives

Hard disk requirement
by Hetz Ben Hamo 13 Jan '19

13 Jan '19

Hi, The old oVirt (3.x?) ISO image wasn't requiring a big hard disk in order to install the node part on a physical machine, since the HE and other parts were running using NFS/iSCSI etc. oVirt 4.X if I understand correctly - does require hard disk on the node. Can this requirement be avoided and just use an SD Card? Whats the minimum storage for the local node? Thanks, Hetz

2 1

Can we drop fc27 jobs / rpms from CI/tested repos?
by Eyal Edri 13 Jan '19

13 Jan '19

5 8

[Ovirt] [CQ weekly status] [11-01-2019]
by Dafna Ron 11 Jan '19

11 Jan '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#3) we have not had any failures since before the holidays. *CQ-Master:* YELLOW (#2) - We had two different code regressions for ovirt-engine and vdsm both were reported and solved during the week. - we had missing packages which were fixed with this patch: https://gerrit.ovirt.org/#/c/96831/ Last successful build for vdsm and ovirt-engine was today (11th Jan). Current status for 4.2 [1] and master [2] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.0_rc)
by Tal Nisan 10 Jan '19

10 Jan '19

1 1

s390x repository closure issue
by Sandro Bonazzola 09 Jan '19

09 Jan '19

Hi, just an heads up that s390x repository is failing repository closure: *00:05:15.127* Problem 2: package ovirt-host-dependencies-4.3.0-0.2.master.20190109065452.gite6c98f4.fc28.s390x requires vdsm >= 4.30.3, but none of the providers can be installed*00:05:15.127* - package vdsm-4.30.3-1.fc28.s390x requires ovirt-imageio-daemon >= 1.2.0, but none of the providers can be installed*00:05:15.127* - conflicting requests*00:05:15.127* - nothing provides ovirt-imageio-common = 1.5.0 needed by ovirt-imageio-daemon-1.5.0-0.201901061027.gita4be4ca.fc28.noarch*00:05:15.127* - nothing provides libvirt-daemon-kvm >= 4.9.0-1 needed by vdsm-4.30.4-92.git2282ef29b.fc28.s390x*00:05:15.127* - nothing provides ovirt-imageio-common = 1.4.6 needed by ovirt-imageio-daemon-1.4.6-1.fc28.noarch*00:05:15.127* - nothing provides libvirt-daemon-kvm >= 4.9.0-1 needed by vdsm-4.30.4-1.fc28.s390x If you can provide missing dependencies please let me know. Thanks. -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

oVirt 4.3.0 RC build delay
by Sandro Bonazzola 08 Jan '19

08 Jan '19

As per subject, Jenkins is under maintenance so no build can be done till maintenance is completed. -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

2 1

Jenkins Jobs Are Not Always Triggered From Gerrit
by Anton Marchukov 08 Jan '19

08 Jan '19

Hello All. We noted that jenkins CI jobs are not always triggered for gerrit changes. While we are investigating this, I want to remind that you always can trigger / re-trigger check-patch jobs yourself. Just go to to the link [1], insert your change id and trigger it. Thanks. [1] https://jenkins.ovirt.org/gerrit_manual_trigger/ -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat

2 2

vdsm has been tagged (v4.30.5)
by Milan Zamazal 08 Jan '19

08 Jan '19

1 0

ovirt-engine has been tagged (ovirt-engine-4.2.8.2)
by Tal Nisan 07 Jan '19

07 Jan '19

1 0

vdsm has been tagged (v4.20.46)
by Milan Zamazal 07 Jan '19

07 Jan '19

1 0