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 <nsoffer(a)redhat.com&gt; wrote: > I had 3 failures with OST master: > > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_m... > > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_m... > > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_m... > > 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_m... > > 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 > > >

you're right. its 7.6.7 instead of 7.6.6 :) On Mon, Jul 8, 2019 at 8:25 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; wrote: > > > Il giorno ven 5 lug 2019 alle ore 12:35 Dafna Ron <dron(a)redhat.com&gt; ha > scritto: > >> 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 >> > > No, packages are not from 7.7. They are from 7.6 (el7_6) > Errata is here: > https://lists.centos.org/pipermail/centos-announce/2019-July/023356.html > They were released in RHEL 7.6 batch #5 on June 4th. Sad it took a month > to get into OST. > > >> >> 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 <nsoffer(a)redhat.com&gt; wrote: >> >>> I had 3 failures with OST master: >>> >>> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_m... >>> >>> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_m... >>> >>> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_m... >>> >>> 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_m... >>> >>> 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 >>> >>> >>> > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com > <https://www.redhat.com/> >

On Mon, Jul 8, 2019, 10:28 Dafna Ron <dron(a)redhat.com&gt; wrote: > sorry, it has 7.6.7 packages instead of 7.6.6 packages and in order to > resolve this in ost we either need to add rhel update to all machines in > all suites (not just for engine in upgrade suites) or Galit has to do a new > image which she is doing now > This block merging in master, we don't merge without passing OST. How can we prevent this from happening in the next update (7.6.8)? > > On Mon, Jul 8, 2019 at 8:26 AM Dafna Ron <dron(a)redhat.com&gt; wrote: > >> you're right. its 7.6.7 instead of 7.6.6 :) >> >> On Mon, Jul 8, 2019 at 8:25 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; >> wrote: >> >>> >>> >>> Il giorno ven 5 lug 2019 alle ore 12:35 Dafna Ron <dron(a)redhat.com&gt; ha >>> scritto: >>> >>>> 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 >>>> >>> >>> No, packages are not from 7.7. They are from 7.6 (el7_6) >>> Errata is here: >>> https://lists.centos.org/pipermail/centos-announce/2019-July/023356.html >>> They were released in RHEL 7.6 batch #5 on June 4th. Sad it took a >>> month to get into OST. >>> >>> >>>> >>>> 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 <nsoffer(a)redhat.com&gt; wrote: >>>> >>>>> I had 3 failures with OST master: >>>>> >>>>> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_m... >>>>> >>>>> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_m... >>>>> >>>>> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_m... >>>>> >>>>> 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_m... >>>>> >>>>> 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 >>>>> >>>>> >>>>> >>> >>> -- >>> >>> Sandro Bonazzola >>> >>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>> >>> Red Hat EMEA <https://www.redhat.com/> >>> >>> sbonazzo(a)redhat.com >>> <https://www.redhat.com/> >>> >>

Galit merged the patch and jobs are now passing. you can try to run ost again On Mon, Jul 8, 2019 at 1:10 PM Dafna Ron <dron(a)redhat.com&gt; wrote: > you can fix the tests and add a rhel update to all engine and hosts > deployment > > On Mon, Jul 8, 2019 at 1:09 PM Nir Soffer <nsoffer(a)redhat.com&gt; wrote: > >> >> >> On Mon, Jul 8, 2019, 10:28 Dafna Ron <dron(a)redhat.com&gt; wrote: >> >>> sorry, it has 7.6.7 packages instead of 7.6.6 packages and in order to >>> resolve this in ost we either need to add rhel update to all machines in >>> all suites (not just for engine in upgrade suites) or Galit has to do a new >>> image which she is doing now >>> >> >> This block merging in master, we don't merge without passing OST. >> >> How can we prevent this from happening in the next update (7.6.8)? >> >> >>> >>> On Mon, Jul 8, 2019 at 8:26 AM Dafna Ron <dron(a)redhat.com&gt; wrote: >>> >>>> you're right. its 7.6.7 instead of 7.6.6 :) >>>> >>>> On Mon, Jul 8, 2019 at 8:25 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; >>>> wrote: >>>> >>>>> >>>>> >>>>> Il giorno ven 5 lug 2019 alle ore 12:35 Dafna Ron <dron(a)redhat.com&gt; >>>>> ha scritto: >>>>> >>>>>> 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 >>>>>> >>>>> >>>>> No, packages are not from 7.7. They are from 7.6 (el7_6) >>>>> Errata is here: >>>>> https://lists.centos.org/pipermail/centos-announce/2019-July/023356.html >>>>> They were released in RHEL 7.6 batch #5 on June 4th. Sad it took a >>>>> month to get into OST. >>>>> >>>>> >>>>>> >>>>>> 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 <nsoffer(a)redhat.com&gt; >>>>>> wrote: >>>>>> >>>>>>> I had 3 failures with OST master: >>>>>>> >>>>>>> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_m... >>>>>>> >>>>>>> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_m... >>>>>>> >>>>>>> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_m... >>>>>>> >>>>>>> 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_m... >>>>>>> >>>>>>> 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 >>>>>>> >>>>>>> >>>>>>> >>>>> >>>>> -- >>>>> >>>>> Sandro Bonazzola >>>>> >>>>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>>>> >>>>> Red Hat EMEA <https://www.redhat.com/> >>>>> >>>>> sbonazzo(a)redhat.com >>>>> <https://www.redhat.com/> >>>>> >>>>