- Devel - oVirt List Archives

[ACTION REQUIRED] clear browser cache
by Greg Sheremeta 08 Aug '17

08 Aug '17

Next time you rebase on ovirt-engine master, please clear your browser cache to pick up changes required by the new blue theme [1][2]. Best wishes, Greg [1] https://gerrit.ovirt.org/#/c/79973 [2] http://imgur.com/a/H7ad6 -- Greg Sheremeta, MBA Sr. Software Engineer Red Hat, Inc. gshereme(a)redhat.com

1 0

oVirt on Fedora 26 is broken
by Yedidyah Bar David 08 Aug '17

08 Aug '17

Hi all, As some of you probably noticed, the support for Fedora since 23 or so was considered "tech preview", and required some manual workarounds, mainly installing python2-dnf. I now spent some time on yet another workaround, as I got a report that above is not enough for Fedora 26, and eventually concluded this will require quite a lot more work, which was already decided to be postponed to oVirt 4.3. So for now, you should consider that $subject. See also: https://bugzilla.redhat.com/show_bug.cgi?id=1416854 https://gerrit.ovirt.org/80347 Best, -- Didi

1 0

[ACTION REQUIRED] update ovirt-js-dependencies
by Greg Sheremeta 08 Aug '17

08 Aug '17

Hi, Please `sudo dnf update ovirt-js-dependencies` to line up with branding changes soon to be merged to master. The latest version is ovirt-js-dependencies-1.2.0-3.1 It's in the repos [1], but let me know if you have issues installing it. Best wishes, Greg [1] http://plain.resources.ovirt.org/repos/ovirt/tested/master/rpm/fc26/noarch/… -- Greg Sheremeta, MBA Sr. Software Engineer Red Hat, Inc. gshereme(a)redhat.com

1 0

[ OST Failure Report ] [ oVirt Master ] [ Aug. 8th 2017 ] [ 001_upgrade_engine.test_initialize_engine ]
by Dafna Ron 08 Aug '17

08 Aug '17

This is a multi-part message in MIME format. --------------578D3CF4C53C01FCD1265694 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit ** *Hi, * * ** We see a sporadic failure in the upgrade test. from what I can see from the log it is related to the firewalD package. Test failed: *001_upgrade_engine.test_initialize_engine* Link to suspected patches: Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1684/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1684/artifact/ Error snippet from the log: <error> * *2017-08-08 04:09:11,006-0400 DEBUG otopi.plugins.otopi.network.firewalld plugin.execute:926 execute-output: ('/bin/firewall-cmd', '--zone', u'public', '--permanent', '--add-service', 'ovirt-postgres') stderr: ESC[91mError: Action org.fedoraproject.FirewallD1.all is not registeredESC[00m 2017-08-08 04:09:11,007-0400 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/otopi/plugins/otopi/network/firewalld.py", line 334, in _closeup '--add-service', service, File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 931, in execute command=args[0], RuntimeError: Command '/bin/firewall-cmd' failed to execute </error> * --------------578D3CF4C53C01FCD1265694 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Hi, <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">We see a sporadic failure in the upgrade test. from what I can see from the log it is related to the firewalD package. <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Test failed: 001_upgrade_engine.test_initialize_engine <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to suspected patches: <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to Job: <a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1684/">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1684/</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to all logs: <a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1684/artifact/">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1684/artifact/</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Error snippet from the log: <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"><error> 2017-08-08 04:09:11,006-0400 DEBUG otopi.plugins.otopi.network.firewalld plugin.execute:926 execute-output: ('/bin/firewall-cmd', '--zone', u'public', '--permanent', '--add-service', 'ovirt-postgres') stderr: ESC[91mError: Action org.fedoraproject.FirewallD1.all is not registeredESC[00m 2017-08-08 04:09:11,007-0400 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/otopi/plugins/otopi/network/firewalld.py", line 334, in _closeup '--add-service', service, File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 931, in execute command=args[0], RuntimeError: Command '/bin/firewall-cmd' failed to execute <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></error> </body> </html> --------------578D3CF4C53C01FCD1265694--

3 3

OST: A good way to test cluster compatibility version upgrade?
by Milan Zamazal 08 Aug '17

08 Aug '17

Hi, we'd like to test cluster compatibility version upgrades in OST and we're thinking whether there is a good way to do that without putting much burden on OST. We want to test that the cluster updates without errors, as well as the VMs in it. A safe way would be to create a new data center for that purpose and run the test on it. But some operations, such as adding a host or a storage, are slow. Maybe we could initialize the data center in parallel with the current test data center but then we'd need an additional Lago host, which might increase memory requirements, already high enough. We might create a new data center and cluster without running hosts and running VMs but then the test would be limited in its extent. Another possibility is to reuse the current test data center. We could create it with the oldest support compatibility version, rather than current compatibility version, and perform upgrades on it up to the current compatibility version. Then we would continue with the tests normally. The overhead, besides testing the upgrades themselves, could be minimal. The disadvantage would be that we wouldn't test the current-compatibility-version creation process directly. We could also make a separate test suite for that test, but is it desirable and would anybody run it regularly? So what do you recommend as a good way to test cluster compatibility version upgrades? Thanks, Milan

3 4

[ OST Failure Report ] [ oVirt master ] [ 06/08/2017 ] [template_update]
by Barak Korren 07 Aug '17

07 Aug '17

Test failed: [ 004_basic_sanity.template_update ] Link to suspected patches: https://gerrit.ovirt.org/#/c/80222 Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1668/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1668/artifact… Error snippet from log: <error> Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 78, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test-scenarios/004_basic_sanity.py", line 635, in template_update nt.assert_true(templates_service.list(search=TEMPLATE_CIRROS)[0].comment == new_comment) File "/usr/lib64/python2.7/unittest/case.py", line 462, in assertTrue raise self.failureException(msg) AssertionError: False is not true </error> -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 1

[ OST Failure Report ] [ oVirt master ] [ 03/08/2017 ] [reattach_storage_domain]
by Barak Korren 03 Aug '17

03 Aug '17

Test failed: [ 007_sd_reattach.reattach_storage_domain ] Link to suspected patches: https://gerrit.ovirt.org/#/c/80152 (Patch does not seem to be directly related but test only included it) Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1627/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1627/artifact… Error snippet from log: <error> Error: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400. </error> -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 1

ovirt-setup-lib missing for Fedora 26
by Jakub Niedermertl 02 Aug '17

02 Aug '17

Hi all, I miss ovirt-setup-lib package for Fedora 26. Could we please have it built for this OS? Thanks Jakub

4 5

Lago OST plugin v0.42 Release Announcement
by Gal Ben Haim 01 Aug '17

01 Aug '17

Hi All, On behalf of the Lago OST plugin team, I'm pleased to announce Lago OST plugin v0.42 is available! For a detailed release announcement please refer to our Github page at: https://github.com/lago-project/lago-ost-plugin/releases/tag/0.42 Resources ========== Docs: http://lago-ost-plugin.readthedocs.io/en/latest/ GitHub: https://github.com/lago-project/lago-ost-plugin YUM Repository: http://resources.ovirt.org/repos/lago/stable/0.0/rpm/ OST Docs: http://ovirt-system-tests.readthedocs.io/en/latest/ Changelog: http://lago-ost-plugin.readthedocs.io/en/latest/_static/ChangeLog.txt -- *GAL bEN HAIM* RHV DEVOPS

1 0

Lago v0.41 Release Announcement
by Gal Ben Haim 01 Aug '17

01 Aug '17

Hi All, On behalf of the Lago team, I'm pleased to announce Lago v0.41 is available! For a detailed release announcement please refer to our Github page at: https://github.com/lago-project/lago/releases/tag/0.41 Resources ========== Lago Docs: http://lago.readthedocs.io/en/latest/ GitHub: https://github.com/lago-project/lago/ YUM Repository: http://resources.ovirt.org/repos/lago/stable/0.0/rpm/ Pypi: https://pypi.python.org/pypi/lago OST Docs: http://ovirt-system-tests.readthedocs.io/en/latest/ Changelog: http://lago.readthedocs.io/en/0.41/_static/ChangeLog.txt <http://lago.readthedocs.io/en/0.40/_static/ChangeLog.txt> As always, if you find any problems, or willing to contribute, visit our GitHub page. Enjoy! -- *GAL bEN HAIM* RHV DEVOPS

1 0