[ovirt-devel] [Ovirt] [CQ weekly status] [05-07-2019]

[Dafna Ron]

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 (#1)

Last failure was on 02-07 for ovirt-provider-ovm due to failed test:
098_ovirt_provider_ovn.use_ovn_provide.
This was a code regression and was fixed by patch
https://gerrit.ovirt.org/#/c/97072/

*CQ-4.3*:  RED (#1)

We are failing because our ost image is centos 7.6 and we now have 7.7
packages.
Galit will need to create a new image to fix the failing tests.

*CQ-Master:*  RED (#1)

We are failing because our ost image is centos 7.6 and we now have 7.7
packages.
Galit will need to create a new image to fix the failing tests.

 Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found
here:

[1]
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-queue-tester/

[2]
https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-queue-tester/

[3]
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change-queue-tester/

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 failuresYELLOW (#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)
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/65Y52U4DML4CPQLYEPJYWIIPBZQVIKQM/

[ovirt-devel] Re: OST fail to install hosts: ​requires: device-mapper = 7:1.02.149-10.el7_6.8 installed: ​device-mapper-1.02.149-10.el7_6.7.x86_64

[Dafna Ron]

The issue is that the images installed by ost are 7.6 which means the
packages are 7.6 packages

templates:
  engine: el7.6-base-4
  host: el7.6-base-4

however, the packages coming from the repo are 7.7

Repository google-chrome is listed more than once in the configuration
pcp-pmda-systemd-0:4.1.0-5.el7_6.x86_64
systemd-0:219-62.el7_6.7.x86_64
systemd-devel-0:219-62.el7_6.7.i686
systemd-devel-0:219-62.el7_6.7.x86_64
systemd-journal-gateway-0:219-62.el7_6.7.x86_64
systemd-libs-0:219-62.el7_6.7.i686
systemd-libs-0:219-62.el7_6.7.x86_64
systemd-networkd-0:219-62.el7_6.7.x86_64
systemd-python-0:219-62.el7_6.7.x86_64
systemd-resolved-0:219-62.el7_6.7.i686
systemd-resolved-0:219-62.el7_6.7.x86_64
systemd-sysv-0:219-62.el7_6.7.x86_64
[dron@dron ovirt-system-tests]$

so if there is a new centos 7.7 now, we should update the ost image to 7.7

Another solution to avoid such failures in the future is to add a yum
update to the test suite and a reboot to the vm, that case we will not fail
on new os version in initialize engine

Adding Galit as she needs to create a new image

Thanks,
Dafna


On Thu, Jul 4, 2019 at 8:41 PM Nir Soffer  wrote:

> I had 3 failures with OST master:
>
> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_manual/detail/ovirt-system-tests_manual/5061/pipeline/
>
> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_manual/detail/ovirt-system-tests_manual/5062/pipeline
>
> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_manual/detail/ovirt-system-tests_manual/5063/pipeline
>
> First 2 builds are mostly logging fixes in vdsm and removing dead code,
> unrelated to the failures.
> Last build is from master, same patch passed OST today here:
>
> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_manual/detail/ovirt-system-tests_manual/5059/pipeline/
>
> Looks like some required packages are missing.
>
> + yum -y install ovirt-host
>
> Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.8.x86_64
> (alocalsync)
>
>Requires: device-mapper = 7:1.02.149-10.el7_6.8
>
>Installed: 7:device-mapper-1.02.149-10.el7_6.7.x86_64
> (installed)
>
>device-mapper = 7:1.02.149-10.el7_6.7
>
> Error: Package: systemd-python-219-62.el7_6.7.x86_64 (alocalsync)
>
>Requires: systemd-libs = 219-62.el7_6.7
>
>Installed: systemd-libs-219-62.el7_6.6.x86_64 (installed)
>
>systemd-libs = 219-62.el7_6.6
>
> Error: Package: systemd-python-219-62.el7_6.7.x86_64 (alocalsync)
>
>Requires: systemd = 219-62.el7_6.7
>
>Installed: systemd-219-62.el7_6.6.x86_64 (installed)
>
>systemd = 219-62.el7_6.6
>
> Error: Package: libgudev1-219-62.el7_6.7.x86_64 (alocalsync)
>
>Requires: systemd-libs = 219-62.el7_6.7
>
>Installed: systemd-libs-219-62.el7_6.6.x86_64 (installed)
>
>systemd-libs = 219-62.el7_6.6
>
>
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/AI4DJMH4QFBJARAR6LSDRIKKRI2FD7PP/