[ovirt-devel] [ OST Failure Report ] [ oVirt Master (vdsm) ] [ 07-06-2019 ] [ 003_00_metrics_bootstrap.metrics_and_log_collector ]

2019-06-07 Thread Dafna Ron 
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
___
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/AGIX5H4EJQ66FULFJ6UL5OEDHZTLVMLO/

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

2019-06-07 Thread 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 05-06 for project ovirt-ansible-cluster-upgrade due to
failure in test 002_bootstrap.add_master_storage_domain.
The fix was created and merged 

*CQ-4.3*:  RED (#1)

vdsm is currently broken due to https://gerrit.ovirt.org/#/c/100576/ -
Remove SOS VDSM plugin
vdsm sos plugin will be available from centos 7.7 as part of sos-3.7-3.
however, the metrics tests are using sos-logcollector which s causing a
failure in ost.
We are waiting for Shirly to have a look at the tests and see how they can
be fixed.

*CQ-Master:*  RED (#1)

vdsm is currently broken due to https://gerrit.ovirt.org/#/c/100576/ -
Remove SOS VDSM plugin
vdsm sos plugin will be available from centos 7.7 as part of sos-3.7-3.
however, the metrics tests are using sos-logcollector which s causing a
failure in ost.
We are waiting for Shirly to have a look at the tests and see how they can
be fixed.

 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/QCT52YUDJANNZMTIRE5I23R32M56YR7C/