- Devel - oVirt List Archives

Re: [Bug 1721581] Ansible 2.8 needed for ovirt-metrics
by Charles Thao 20 Jun '19

20 Jun '19

On Thu, Jun 20, 2019 at 6:53 AM <bugzilla(a)redhat.com> wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1721581 > > Shirly Radco <sradco(a)redhat.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|POST |MODIFIED > Flags|needinfo?(sradco(a)redhat.com | > |) | > > > > -- > You are receiving this mail because: > You reported the bug.

1 0

Test failure on Fedora 29
by Nir Soffer 19 Jun '19

19 Jun '19

We have new random failure in this test: [2019-06-18T16:05:56.576Z] =================================== FAILURES =================================== [2019-06-18T16:05:56.576Z] _________________ SSLTests.testConnectWithoutCertificateFails __________________ [2019-06-18T16:05:56.576Z] [2019-06-18T16:05:56.576Z] self = <ssl_test.SSLTests testMethod=testConnectWithoutCertificateFails> [2019-06-18T16:05:56.576Z] [2019-06-18T16:05:56.576Z] def testConnectWithoutCertificateFails(self): [2019-06-18T16:05:56.576Z] """ [2019-06-18T16:05:56.576Z] Verify that the connection without a client certificate [2019-06-18T16:05:56.576Z] fails. [2019-06-18T16:05:56.576Z] """ [2019-06-18T16:05:56.576Z] [2019-06-18T16:05:56.576Z] with self.assertRaises(cmdutils.Error): [2019-06-18T16:05:56.576Z] args = ["openssl", "s_client", "-connect", "%s:%d" % self.address] [2019-06-18T16:05:56.576Z] > commands.run(args) [2019-06-18T16:05:56.576Z] E AssertionError: Error not raised [2019-06-18T16:05:56.576Z] [2019-06-18T16:05:56.576Z] ssl_test.py:173: AssertionError The build: https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st… Marcin, can you look at it?

2 3

vdsm has been tagged (v4.30.20)
by Milan Zamazal 18 Jun '19

18 Jun '19

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.5.1)
by Tal Nisan 18 Jun '19

18 Jun '19

1 0

Low Performance Issue
by Akshita Jain 17 Jun '19

17 Jun '19

I've setup oVirt HCI over 3 servers. Each server has 1* 480 GB SSD, 5* 1.8 TB SAS HDD with oVirt version 4.3.3 But I am still able to get low performance. Can anyone suggest the tuning variables for Gluster volume. Remark :What should the value be set for network.remote-dio= enable / disable ?

2 2

[storage] isolating images
by Germano Veit Michel 17 Jun '19

17 Jun '19

Hello, When there are image chains problems, sometimes it is not possible to determine the correct chain due to lost information like rotated logs. For this cases, it is usually desirable to remove a volume from the chain but not from the storage until the user confirms the VM is healthy and contains the correct data. Currently this is done by moving files (file storage) or renaming LVM tags (block storage) so VDSM does not find the particular volume to be part of the chain. Ideally I would like to have this done by a vdsm-tool talking to VDSM api. The tool would be able to mark the volume to be ignored or not, list all ignored volumes and perhaps even delete them (to free space). How would you recommend proceeding with such tool? Some ideas: - Have a reserved image UUID which contains all ignored volumes, so they are not part of any chain. - Add an "ignore" metadata attribute to each volume. I like more the first option, but looking for opinions and ideas. Thanks, Germano

1 0

ovirt-system-tests_hc-basic-suite-master failing
by Gobinda Das 14 Jun '19

14 Jun '19

Hi, hc-basic-suite-master build is failing due to sanlock-python dependency issue. Error: Package: vdsm-4.40.0-338.gitaaf7f44.el7.x86_64 (alocalsync) Requires: sanlock-python >= 3.7.3 Installing: sanlock-python-3.6.0-1.el7.x86_64 (alocalsync) sanlock-python = 3.6.0-1.el7 Can anyone please help? -- Thanks, Gobinda

2 1

[Ovirt] [CQ weekly status] [14-06-2019]
by Dafna Ron 14 Jun '19

14 Jun '19

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) 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*: GREEN (#1) There were two main failures this week. 1. vdsm was failing due to the sos change which was causing metrics tests to fail as it was using vdsm sos plugin and that is no longer available. this was fix by mperina: https://gerrit.ovirt.org/100716 https://gerrit.ovirt.org/100809 2. there was a general failure due to packages. two patches were merged to fix the issue: https://gerrit.ovirt.org/#/c/100764/ https://gerrit.ovirt.org/#/c/100691/ *CQ-Master:* GREEN (#1) Master was failing on the same issues as in 4.3 which are now 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-qu… [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [3] 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

adding host to oVirt issue
by Hetz Ben Hamo 14 Jun '19

14 Jun '19

Hi, I have been checking oVirt latest (4.3.4) with adding various bare metal hosts with various CPU's: I'm asking on this mailing list if I should open a ticket and if so what ticket (bug? RFE?). - AMD Ryzen 5 - Xeon SP (first gen) - Xeon SP (second gen) - Upcoming unannounced Xeon CPU. The main oVirt machine (and the HE) is running on Xeon E3-1225 V3 CPU. The big problem is that when you add for example any AMD processor (whatever it's a low end Ryzen 5 or a high end 32 cores EPYC) to such a setup, it will fail because it tries to add the AMD machine to the default cluster which is defined as Intel based VT-X. If I'll try to add any non Xeon V3 CPU, it will succeed, but any live migration of VM's inside the cluster will fail since any Xeon chip version has various VT flags. So, my suggestion is that when adding nodes/hosts to oVirt, they will be added to a new "non clustered" place without any features allowed (live migration, for example) and after the admin will add the machines, he/she can assign nodes to a defined cluster (prepared or that he/she can create) Another problem with cluster defining is that the CPU type is too complicated for any admin who doesn't know the nuts and bolts of each CPU. For example - the Haswell CPU type got *6* CPU types. Do you really expect an admin to know which one to select? IMHO, a good solution would be to add some "detect" button to hosts, and the result from clicking this button should be a window with options like: - Add this host to an existing cluster (which has the same CPU type) - Auto create a new cluster with the CPU type detected from the node/host CPU I'll be happy to hear your thoughts about this issue. Thanks, Hetz

1 0

[ OST Failure Report ] [ oVirt Master (vdsm) ] [ 07-06-2019 ] [ 003_00_metrics_bootstrap.metrics_and_log_collector ]
by Dafna Ron 14 Jun '19

14 Jun '19

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

7 21