On Tue, Jun 11, 2019 at 11:58 AM Milan Zamazal <mzama...@redhat.com> wrote:
> Dafna Ron <d...@redhat.com> writes: > > > Hi, > > > > Please note vdsm has been broken since Fri the 7th > > > > to summarize again, vdsm has a patch to remove sos plugin which is what > > metrics is using in its ost tests > > due to that, vdsm is failing the metrics tests and in order to solve it > we > > need to make a choice: > > 1. fix the metrics tests to not use sos > > 2. disable the metrics tests > > 3. revert the sos patch until a decision is made on ^^ > > #3 is not an option, it would make Vdsm uninstallable on newer RHEL > versions. > I've posted a patch https://gerrit.ovirt.org/100716 which is trying to install vdsm sos plugin if it's not installed either by vdsm nor sos. Currenlty waiting for CI, if run is successfull, I will extend the patch also for 4.3 basic suite. > > Thanks, > > Dafna > > > > > > ---------- Forwarded message --------- > > From: Dafna Ron <d...@redhat.com> > > Date: Mon, Jun 10, 2019 at 1:30 PM > > Subject: Re: [ OST Failure Report ] [ oVirt Master (vdsm) ] [ 07-06-2019 > ] > > [ 003_00_metrics_bootstrap.metrics_and_log_collector ] > > To: Martin Perina <mper...@redhat.com>, Milan Zamazal < > mzama...@redhat.com>, > > Shirly Radco <sra...@redhat.com> > > Cc: devel <devel@ovirt.org>, infra <in...@ovirt.org> > > > > > > Shirly? any update on this? > > > > On Fri, Jun 7, 2019 at 11:54 AM Dafna Ron <d...@redhat.com> wrote: > > > >> Hi, > >> > >> We have a failure in vdsm project on master. > >> > >> The issue is change: > >> https://gerrit.ovirt.org/#/c/100576/ - Remove SOS VDSM plugin > >> > >> which is failing on metrics as metrics is calling sos-logcollector. > >> > >> The patch cannot be changed as until centos 7.7 when sos-3.7-3, which > >> contains vdsm plugin will come out. > >> so until then, we are left with no sos plugin, which is causing the > >> metrics test to fail. > >> > >> Shirly, can you please take a look and see if we can change the test to > >> not call sos-logcollector? > >> Please note, that we are expecting 4.3 to fail on same issue very soon. > >> > >> failed job can be found here: > >> > >> https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14452/ > >> > >> > >> ERROR from test: > >> > >> lago.ssh: DEBUG: Command 8626fe70 on lago-basic-suite-master-engine > errors: > >> ERROR: Failed to get a sosreport from: lago-basic-suite-master-host-1; > Could not parse sosreport output > >> ERROR: Failed to get a sosreport from: lago-basic-suite-master-host-0; > Could not parse sosreport output > >> > >> lago.utils: DEBUG: Error while running thread Thread-3 > >> Traceback (most recent call last): > >> File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in > _ret_via_queue > >> queue.put({'return': func()}) > >> File > "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test-scenarios/003_00_metrics_bootstrap.py", > line 97, in run_log_collector > >> 'log collector failed. Exit code is %s' % result.code > >> File "/usr/lib64/python2.7/unittest/case.py", line 462, in assertTrue > >> raise self.failureException(msg) > >> AssertionError: log collector failed. Exit code is 1 > >> --------------------- >> end captured logging << ---------- > >> > >> Thanks, > >> Dafna > >> > -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.
_______________________________________________ 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/SQJDJHHQR52QTGRZBIOLBWWVGUX3ZPNW/
