April 2017 - Devel - oVirt List Archives

[OST] [HC] HE VM fails to start
by Sahina Bose 06 Apr '17

06 Apr '17

The error in vdsm.log Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 2016, in _setup_devices dev_object.setup() File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/graphics.py", line 63, in setup net_api.create_libvirt_network(display_network, self.conf['vmId']) File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 90, in create_libvirt_network libvirt.create_network(netname, user_reference) File "/usr/lib/python2.7/site-packages/vdsm/network/libvirt.py", line 94, in create_network if not is_libvirt_network(netname): File "/usr/lib/python2.7/site-packages/vdsm/network/libvirt.py", line 159, in is_libvirt_network netname = LIBVIRT_NET_PREFIX + netname TypeError: cannot concatenate 'str' and 'NoneType' objects 2017-03-29 22:58:39,559-0400 ERROR (vm/d71bdf4e) [virt.vm] (vmId='d71bdf4e-1eb3-4762-bd0e-05bb9f5e43ef') The vm start process failed (vm:659) The tests last passed on Mar 28. Did a recent patch break this? The full build logs at http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/52/artifact/expor… thanks sahina

4 12

Firewalld migration.
by Leon Goldberg 06 Apr '17

06 Apr '17

Hey, We're looking to migrate from iptables to firewalld. We came up with a couple of possible approaches we'd like opinions on. I'll list the options first, and will 1) Replicate existing flow: As of date, iptable rules are inserted in the database via SQL config files. During host deployment, VdsDeployIptablesUnit adds the required rules (based on cluster/firewall configuration) to the deployment configuration, en route to being deployed on the host via otopi and its iptables plugin. Pros: - Reuse of existing infrastructure. Cons: - Current infrastructure is overly complex... - Many of the required services are provided by firewalld. Rewriting them is wasteful; specifying them (instead of providing actual service .xml content) will require adaptations on both (engine/host) sides. More on that later. 2) Host side based configuration: Essentially, all the required logic (aforementioned cluster/firewall configuration) to determine if/how firewalld should be deployed could be passed on to the host via ohd. Vdsm could take on the responsibility of examining the relevant configuration, and then creating and/or adding the required services (using vdsm.conf and vdsm-tool). Pros: - Engine side involvement is greatly diminished. - Simple(r). Cons: - Custom services/rules capabilities will have to be rethought and re-implemented (current infrastructure supports custom iptables rules by being specified in the SQL config file). 3) Some other hybrid approach: If we're able to guarantee all the required firewalld services are statically provided one way or the other, the current procedure could be replicated and be made more simpler. Instead of providing xml content in the form of strings, service names could be supplied. The responsibility of actual service deployment becomes easier, and could be left to otopi (with the appropriate modifications) or switched over to vdsm. -- Regardless, usage of statically provided vs. dynamically created services remains an open question. I think we'd like to avoid implementing logic that ask whether some service is provided (and then write it if it isn't...), and so choosing between the dynamic and static approaches is also needed. Using the static approach, guaranteeing *all* services are provided will be required. I do believe guaranteeing the presence of all required services is worth it, however custom services aren't going to be naively compatible, and we'll still have to use similar mechanism as described in #1 (service string -> .xml -> addition of service name to active zone). Your thoughts are welcome. Thanks, Leon

10 37

[ OST Failure Report ] [ oVirt master ] [ 5/4/2017 ] [ add_non_vm_network ]
by Barak Korren 05 Apr '17

05 Apr '17

Test failed: [ add_non_vm_network ] Link to suspected patches: - https://gerrit.ovirt.org/75020 - https://gerrit.ovirt.org/75010 - https://gerrit.ovirt.org/75065 - https://gerrit.ovirt.org/75021 - https://gerrit.ovirt.org/75067 - https://gerrit.ovirt.org/74916 Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6208/ Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6208/artif… Error snippet from log: <error> status: 400 reason: Bad Request detail: Internal Engine Error </error> -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

2 1

[ ACTION REQUIRED ] ABORTED jobs in Jenkins
by Barak Korren 05 Apr '17

05 Apr '17

Hi, We are having a Jenkins malfunction ATM that makes it necessary to abort some CI jobs. If the jobs it your patch get aborted, please re-trigger them, they should pass fine now. -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

1 0

[ANN] oVirt 4.1.1 Async release candidate
by Sandro Bonazzola 05 Apr '17

05 Apr '17

Hi, following oVirt 4.1.1 GA the oVirt team identified some bugs worth to be addressed out of the usual release cycle. For this reason an async release including these fixes is under preparation. An update to the following packages have been pushed to the pre-release repository for testing. - cockpit-ovirt-0.10.7-0.0.16 - imgbased-0.9.20 - ovirt-engine-4.1.1.8 - ovirt-engine-metrics-1.0.2 - ovirt-release41-4.1.1.1 - ovirt-web-ui-0.1.2-4 - vdsm-jsonrpc-java-1.3.10 - vdsm v4.19.10.1 In order to test it, you'll need pre-release repository enabled: yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release41-pre.rpm An update to release notes including bugs related to above packages and updates applied in bugzilla documentation texts has been pushed tohttps://github.com/oVirt/ovirt-site/pull/888 for review. On behalf of the oVirt team, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Engine error: No enum constant ProviderType.http://localhost:9696
by Jakub Niedermertl 04 Apr '17

04 Apr '17

Hi, anyone else is experiencing following error message in engine log? 2017-04-04 17:38:48,988+02 ERROR [org.ovirt.engine.core.bll.provider.GetAllProvidersQuery] (default task-101) [b421c4c1-1602-4c41-88f6-b5ff20888713] Query 'GetAllProvidersQuery' failed: No enum constant org.ovirt.engine.core.common.businessentities.ProviderType.http://localhost:9696 2017-04-04 17:38:48,989+02 ERROR [org.ovirt.engine.core.bll.provider.GetAllProvidersQuery] (default task-101) [b421c4c1-1602-4c41-88f6-b5ff20888713] Exception: java.lang.IllegalArgumentException: No enum constant org.ovirt.engine.core.common.businessentities.ProviderType.http://localhost:9696 at java.lang.Enum.valueOf(Enum.java:238) [rt.jar:1.8.0_121] at org.ovirt.engine.core.common.businessentities.ProviderType.valueOf(ProviderType.java:11) [common.jar:] at org.ovirt.engine.core.dao.provider.ProviderDaoImpl$ProviderRowMapper.mapRow(ProviderDaoImpl.java:134) [dal.jar:] at org.ovirt.engine.core.dao.provider.ProviderDaoImpl$ProviderRowMapper.mapRow(ProviderDaoImpl.java:119) [dal.jar:] ... I filed an issue for that https://bugzilla.redhat.com/show_bug.cgi?id=1438883. Jakub

2 1

Live demo session on how to debug oVirt GWT applications
by Vojtech Szocs 04 Apr '17

04 Apr '17

Hello UI devs, with oVirt master UI using the latest GWT SDK [1], I'd like to host a live demo session with two goals in mind: a, explain how the (Java IDE based) Classic Dev Mode works and mention its limitations b, explain how the (browser based) Super Dev Mode works and encourage people to start using it to boost their productivity [1] http://www.mail-archive.com/devel@ovirt.org/msg08558.html The Classic vs. Super Dev Mode are two possible ways to debug GWT applications. This session will give you the knowledge to decide which one to use in a specific situation. Proposed time: Mon, Apr 3 @ 5pm CET / 6pm TLV / 11am US EST. (This can be changed as needed.) Let me know if this kind of session interests you or if the above time doesn't fit you but you'd still like to join. Thanks, Vojtech

2 5

planned Gerrit maintenance
by Evgheni Dereveanchin 04 Apr '17

04 Apr '17

Hi everyone, I will be performing updates on gerrit.ovirt.org during the next hour. Within this period the UI and repositories may be unavailable. I will follow up as soon as maintenance activities are over. -- Regards, Evgheni Dereveanchin

1 1

Gluster/virt ports clarifications.
by Leon Goldberg 03 Apr '17

03 Apr '17

Hey, We're gathering information regarding the ports we open as part of the firewalld migration research. We have most of the current ports covered by either firewalld itself or by 3rd party packages, however some questions remain unanswered: IPTablesConfigForVirt: - serial consoles (tcp/2223): Is this required? can't find a single reference to a listening entity. Either way, I couldn't find a relevant service that provides it. IPTablesConfigForGluster: - Gluster swift (tcp/8080): Doesn't appear in Gluster's firewalld service. Should be added to Gluster's firewalld service? - tcp/39543 and tcp/55863, appear under "status". Couldn't find a relevant service that provides them. Should be added? (and if so, where?) - nlockmgr (tcp/38468, udp/963, tcp/965): tcp/38468 appears in gluster's service. Couldn't find a relevant service that provides the other two. Should be added? (and if so, where?) - ctdbd (tcp/4379): Couldn't find a relevant service that provides this. Should be added? (and if so, where?) Thanks, Leon

4 3

[ OST Failure Report ] [ oVirt master ] [ 3/4/2017 ] [test_intialize_engine]
by Barak Korren 03 Apr '17

03 Apr '17

Link to suspected patches: https://gerrit.ovirt.org/#/c/73688/ Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6164/ Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6164/artif… Error snippet from log: <error> [ INFO ] Starting engine service [ ERROR ] Failed to execute stage 'Closing up': Failed to start service 'ovirt-engine' [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20170403084130-sfzp94.log </error> -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/Test failed: [ TEST NAME ]

2 1