April 2017 - Devel - oVirt List Archives

[ OST Failure Report ] [ oVirt 4.1 ] [ 23-03-2017 ] [ 002_bootstrap.add_secondary_storage_domains ]
by Shlomo Ben David 20 Apr '17

20 Apr '17

Hi, Test failed: [ 002_bootstrap.add_secondary_storage_domains ] Link to suspected patches: N/A Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1054 Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1054/artifact… Error snippet from the log: <error> 2017-03-23 07:23:38,867-0400 ERROR (jsonrpc/2) [storage.TaskManager.Task] (Task='8347d74c-92fe-4371-bc84-1314a43a2971') Unexpected error (task:870) Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 877, in _run return fn(*args, **kargs) File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 52, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 1159, in attachStorageDomain pool.attachSD(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/share/vdsm/storage/sp.py", line 924, in attachSD dom = sdCache.produce(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 112, in produce domain.getRealDomain() File "/usr/share/vdsm/storage/sdc.py", line 53, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 136, in _realProduce domain = self._findDomain(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 153, in _findDomain return findMethod(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 178, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: (u'127fbe66-204c-4c6d-b521-d0f431af2b6c',) </error> Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCVA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

2 1

[ OST Failure Report ] [ oVirt master ] [ 20.4.17 ] [ add_secondary_storage_domains ]
by Gil Shinar 20 Apr '17

20 Apr '17

Test failed: add_secondary_storage_domains Link to suspected patches: Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6403 Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6403/artif… Error seems to be: *2017-04-19 18:58:58,774-0400 ERROR (jsonrpc/2) [storage.TaskManager.Task] (Task='8f9699ed-cc2f-434b-aa1e-b3c8ff30324a') Unexpected error (task:871)Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 878, in _run return fn(*args, **kargs) File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 52, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 2709, in getStorageDomainInfo dom = self.validateSdUUID(sdUUID) File "/usr/share/vdsm/storage/hsm.py", line 298, in validateSdUUID sdDom = sdCache.produce(sdUUID=sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 112, in produce domain.getRealDomain() File "/usr/share/vdsm/storage/sdc.py", line 53, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 136, in _realProduce domain = self._findDomain(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 153, in _findDomain return findMethod(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 178, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID)StorageDomainDoesNotExist: Storage domain does not exist: (u'ac3bbc93-26ba-4ea8-8e76-c5b761f01931',)2017-04-19 18:58:58,777-0400 INFO (jsonrpc/2) [storage.TaskManager.Task] (Task='8f9699ed-cc2f-434b-aa1e-b3c8ff30324a') aborting: Task is aborted: 'Storage domain does not exist' - code 358 (task:1176)2017-04-19 18:58:58,777-0400 ERROR (jsonrpc/2) [storage.Dispatcher] {'status': {'message': "Storage domain does not exist: (u'ac3bbc93-26ba-4ea8-8e76-c5b761f01931',)", 'code': 358}} (dispatcher:78)*

4 9

Announcing VM Portal 0.1.4
by Marek Libra 20 Apr '17

20 Apr '17

Hello All, Let me announce availability of the VM Portal v0.1.4 for preliminary testing. We are looking forward to your feedback which we will try to incorporate into oncoming stable 1.0.0 version. The VM Portal aims to be a drop-in replacement of the existing Basic User Portal. Revised list of Extended User Portal features will be implemented to ideally replace it as well. The VM Portal is installed by default since oVirt 4.1. *The simplest way to try latest version is via Docker by [1].* Once oVirt credentials are entered and initialization is finished, you can access it on [2]. If you prefer to stay as closest to the production setup as possible, the latest rpms are available on project's yum repo [3]. Then you can access the portal from [4]. Prerequisites: The VM Portal requires ovirt-engine 4.0+, so far mostly tested on 4.1. Please note, the docker image is so far meant to just simplify user testing and is not ready for production setup. Unless decided otherwise in the future, stable releases are still planed to be deployed via rpms. For issue reporting or enhancement ideas, please use project's github issue tracker [5]. Thank you for your feedback, Marek [1] docker run --rm -it -e ENGINE_URL=https://[OVIRT.ENGINE.FQDN]/ovirt-engine/ -p 3000:3000 mareklibra/ovirt-web-ui:latest [2] http://localhost:3000 [3] https://people.redhat.com/mlibra/repos/ovirt-web-ui [4] https://[OVIRT.ENGINE.FQDN]/ovirt-engine/web-ui [5] https://github.com/oVirt/ovirt-web-ui/issues -- Marek Libra senior software engineer Red Hat Czech <https://www.redhat.com>

3 2

Fwd: F27 Self Contained Change: Java 9
by Sandro Bonazzola 19 Apr '17

19 Apr '17

FYI ---------- Forwarded message ---------- From: Jan Kurik <jkurik(a)redhat.com> Date: Wed, Apr 19, 2017 at 2:13 PM Subject: F27 Self Contained Change: Java 9 To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org>, devel-announce(a)lists.fedoraproject.org = Proposed Self Contained Change: Java 9 = https://fedoraproject.org/wiki/Changes/Java9TechPreview Change owner(s): * Jiri Vanek <jvanek at redhat dot com> Add a tech preview preview of the the upcoming version of Java (OpenJDK9) to Fedora 27 == Detailed Description == The current Java implementation in Fedora comes from OpenJDK. Java 9 (and OpenJDK9) are tentatively scheduled for release in 2017-07-27. Fedora 27 will most likely be out just a few months after that, and is therefore positioned to receive a tech preview version of the latest OpenJDK9 candidates. This preview should be released version of Java 9, will contain new Java 9 APIs, but may not be supported by many applications directly, therefore it have to warm up as techpreview. == Scope == The current version of OpenJDK 9 will be packaged and added to Fedora. It will be a stand alone package and will not impact existing OpenJDK 8 packages. Since this will be a tech preview, the primary JDK in Fedora 27 will continue to be OpenJDK8. OpenJDK9 is not expected to be the primary Java until Fedora 28 at least. Two problems would generally be expected with a major JDK update based on past experience: FTFBS failures due to packages having a hard-coded JDK version dependency. This was dealt with when both OpenJDK8 and OpenJDK7 were introduced over Fedora 16/17 and Fedora 19/21. Now all Java dependent packages should require java >= 1.6.0, and therefore this issue will not be a problem any more. There may be packages that rely on API that is deprecated in Java 9 Such packages cannot be identified until we actually start to build with Java 9. Since Java 8 will continue to remain the primary version of Java in Fedora 26, any API deprecation issues will be a secondary problem as the main JVM will continue to be able to run everything correctly. We expect to have everything resolved well before Java 9 is to become the primary Java version in Fedora (F28 or later). * Proposal owners: providing java-9-openjdk package to main repositories * Other developers: N/A (not a System Wide Change) * Release engineering: only the inclusion of new package is needed * List of deliverables: N/A (not a System Wide Change) * Policies and guidelines: N/A (not a System Wide Change) * Trademark approval: N/A (not needed for this Change) -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org -- 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

[VDSM] [ENGINE] [RFC] A configuration verb for contexual vdsm operation mode
by Roy Golan 19 Apr '17

19 Apr '17

I'm working on a POC lately on a change to stats collection and retrieval by VDSM. The moto is to cut all we can from host/vm stats (possibly caps) and report only core-business stuff to the engine. Engine will retrieve the rest through a 3rd party provider (nevermind what is it atm) Being backward compatible by design, I have to support 2 API versions for Host.getStats , '4.1' and '4.2'. Except from supplying less parameters, I want VDSM to do less stuff. It doesn't need to sample what it doesn't report. In other words I want '4.1-sampling' and '4.2-sampling' # Introducing 'configuration' Verb: As engine knows always(Hosted Engine as well) what cluster version this host belongs to, it can configure VDSM to operate in cluster version mode. Host.configure(config={version: 4.2} Consider this verb, pre-activating using 'Host.getCaps' to set the context. It will set the righjt sampling method, and other stuff if needed then API endpoints will have the right permutation of the api to answer it. 4.2 host can operate in 4.1 mode: Host.configure(config={version: 4.1} Issue: moving a 4.2 host from 4.2 cluster to 4.1 is a problem since engine needs to know this is a new vdsm that has the verb available. One way to overcome that is to fire the verb for every host regardless of the version and disregard an error that implies the verb doesn't exist. # Engine: Engine will have a handling of the verb per version. Host/Vms monitoring should be changed - I suggest to move out of the monitoring code the whole stats collection as it is a different task which is orthogonal to 'monitoring' and in 4.2 more than before. I know configuration for VDSM has been discussed before and there are probably tons of ways to do it. When you share your thoughts please remember that configuration is a by-product of the effort. Nevertheless it can be potentially beneficial to more functions in vdsm. Thanks, Roy

6 14

Feedback from oVirt community survey
by Sandro Bonazzola 14 Apr '17

14 Apr '17

Hi, from oVirt survey, here are the suggestion from community: - I want oVirt built reporting for hosts and VMs performance analyze - Please add some more fancy icons to the Engine. Also, if possible add icons to the menus when you click with right button. Helps A LOT with User Experience. - Improve where there options are to make easy to find them. Two examples: a Storage Migration option (not only a Live Migration) in the main VM menu and an easier way to manage Snapshots as for example revert back to previous snapshot when something goes wrong within the Guest. - I think the project need some more enterprise features like: - performance monitoring - alerting - more robust import/export tools from other enterprise virtualization solutions - direct Ceph support. - The killer feature can be SDN like VMware NSX - I use a lot of scripts based on ovirtsdk3 and ovirtshell and It's a matter that there is no adaptation of the CLI to sdk4 - Need a stable backup implementation - Node cannot have shared storage and local storage on one host. - Please improve ceph support -- 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

How do you oVirt? Here the answers!
by Sandro Bonazzola 14 Apr '17

14 Apr '17

Hi, a few weeks ago I opened a survey asking oVirt users about how they use oVirt. Here are the analytics of the survey: https://docs.google.com/forms/d/1s3k4pq_U4vHTuUUKr6dOosGj_EGFxqEisansHlqnyy… Most notable facts: - 197 responses, two times the responses we got with the 3.6 survey! - CentOS confims as the most used distribution for running oVirt engine (89.8%) and Hypervisors (74.3% which become 94.2% including oVirt Node which is a CentOS spin) - Fedora is the second distribution (4.6%) mostly used only for runnig oVirt engine - oVirt Node jumped from 7.1% on 3.6 survey to 19.9% in 4.1! - Surprisingly we have someone running both engine and hypervisor on Ubuntu based system, within VMs. I'd like to hear more about this use case. - Within other OS we had Red Hat Enterprise Linux 6 and 7 and Scientific Linux (I guess 7, wasn't specified) - Within the storage, there isn't a "winner" between NFS, Gluster and iSCSI. Within Other Storage, Fiber Channel is the most used. We had also: Ceph, DAS, EMC ScaleIO, GPFS - Hosted Engine is the most used deployment choice with 58.4% (was 50.0% in 3.6) - 65.8% of Hosted Engine users use it in Hyperconverged setup. Thank you for your feedback and appreciation, we'll look into suggestions you sent in the survey. -- 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

ovirt-engine version problem
by shubham dubey 13 Apr '17

13 Apr '17

Hello, Recently I have installed ovirt-engine development environment. The snapshot repository I have used is ovirt-release-master. Now I have installed vdsm in ovirt host with ovirt-release41, so when I am trying to add the host it is showing that ovirt node support cluster version 3.9,4.0 and 4.1 but 4.2 is available. So I have decided to installed ovirt engine with ovirt-engine41 repository. The steps I follow are :- 1) yum remove ovirt-release-master.noarch 2) yum install ovirt-release41.noarch 3) delete $HOME/ovirt-engine and $HOME/git/ovirt-engine 4) git clone ovirt-engine again 5) make install-dev PREFIX=$HOME/ovirt-engine The compiling ends successfully but the $HOME/ovirt-engine directory is coming out empty. So $HOME/ovirt-engine/bin/engine-setup is giving error that NO file or directory found. So can anyone tell me what I am doing wrong? Note:One more thing I have noticed is that even after changing repo to ovirt 4.1 the make is still compiling ovirt 4.2 snapshot. Thanks, Shubham

4 8

[OST Failure Report][oVirt master][2017-04-11] add_secondary_storage_domains
by Sandro Bonazzola 12 Apr '17

12 Apr '17

Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6303 *OST is failing in the last 50 builds* *00:18:22.090* [basic_suit_el7] # add_secondary_storage_domains: *00:18:22.090* [basic_suit_el7] Error while running thread*00:18:22.090* [basic_suit_el7] Traceback (most recent call last):*00:18:22.090* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue*00:18:22.090* [basic_suit_el7] queue.put({'return': func()})*00:18:22.090* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 427, in add_nfs_storage_domain*00:18:22.090* [basic_suit_el7] add_generic_nfs_storage_domain(prefix, SD_NFS_NAME, SD_NFS_HOST_NAME, SD_NFS_PATH, nfs_version='v4_2')*00:18:22.091* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 441, in add_generic_nfs_storage_domain*00:18:22.091* [basic_suit_el7] add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mount_path, sd_format, sd_type, nfs_version)*00:18:22.091* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 490, in add_generic_nfs_storage_domain_4*00:18:22.091* [basic_suit_el7] host=_random_host_from_dc_4(api, DC_NAME),*00:18:22.091* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 106, in _random_host_from_dc_4*00:18:22.091* [basic_suit_el7] return random.choice(_hosts_in_dc_4(api, dc_name))*00:18:22.091* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 100, in _hosts_in_dc_4*00:18:22.091* [basic_suit_el7] raise RuntimeError('Could not find hosts that are up in DC %s' % dc_name)*00:18:22.092* [basic_suit_el7] RuntimeError: Could not find hosts that are up in DC test-dc*00:18:22.092* [basic_suit_el7] Error while running thread*00:18:22.092* [basic_suit_el7] Traceback (most recent call last):*00:18:22.092* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue*00:18:22.092* [basic_suit_el7] queue.put({'return': func()})*00:18:22.092* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 583, in add_iso_storage_domain*00:18:22.092* [basic_suit_el7] add_generic_nfs_storage_domain(prefix, SD_ISO_NAME, SD_ISO_HOST_NAME, SD_ISO_PATH, sd_format='v1', sd_type='iso', nfs_version='v3')*00:18:22.092* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 441, in add_generic_nfs_storage_domain*00:18:22.092* [basic_suit_el7] add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mount_path, sd_format, sd_type, nfs_version)*00:18:22.093* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 490, in add_generic_nfs_storage_domain_4*00:18:22.093* [basic_suit_el7] host=_random_host_from_dc_4(api, DC_NAME),*00:18:22.093* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 106, in _random_host_from_dc_4*00:18:22.093* [basic_suit_el7] return random.choice(_hosts_in_dc_4(api, dc_name))*00:18:22.093* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 100, in _hosts_in_dc_4*00:18:22.093* [basic_suit_el7] raise RuntimeError('Could not find hosts that are up in DC %s' % dc_name)*00:18:22.093* [basic_suit_el7] RuntimeError: Could not find hosts that are up in DC test-dc*00:18:22.094* [basic_suit_el7] Error while running thread*00:18:22.094* [basic_suit_el7] Traceback (most recent call last):*00:18:22.094* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue*00:18:22.094* [basic_suit_el7] queue.put({'return': func()})*00:18:22.094* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 587, in add_templates_storage_domain*00:18:22.094* [basic_suit_el7] add_generic_nfs_storage_domain(prefix, SD_TEMPLATES_NAME, SD_TEMPLATES_HOST_NAME, SD_TEMPLATES_PATH, sd_format='v1', sd_type='export', nfs_version='v4_1')*00:18:22.094* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 441, in add_generic_nfs_storage_domain*00:18:22.094* [basic_suit_el7] add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mount_path, sd_format, sd_type, nfs_version)*00:18:22.094* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 490, in add_generic_nfs_storage_domain_4*00:18:22.095* [basic_suit_el7] host=_random_host_from_dc_4(api, DC_NAME),*00:18:22.095* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 106, in _random_host_from_dc_4*00:18:22.095* [basic_suit_el7] return random.choice(_hosts_in_dc_4(api, dc_name))*00:18:22.095* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 100, in _hosts_in_dc_4*00:18:22.095* [basic_suit_el7] raise RuntimeError('Could not find hosts that are up in DC %s' % dc_name)*00:18:22.095* [basic_suit_el7] RuntimeError: Could not find hosts that are up in DC test-dc*00:18:22.095* [basic_suit_el7] Error while running thread*00:18:22.095* [basic_suit_el7] Traceback (most recent call last):*00:18:22.096* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue*00:18:22.096* [basic_suit_el7] queue.put({'return': func()})*00:18:22.096* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 436, in add_second_nfs_storage_domain*00:18:22.096* [basic_suit_el7] SD_NFS_HOST_NAME, SD_SECOND_NFS_PATH)*00:18:22.096* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 441, in add_generic_nfs_storage_domain*00:18:22.096* [basic_suit_el7] add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mount_path, sd_format, sd_type, nfs_version)*00:18:22.096* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 490, in add_generic_nfs_storage_domain_4*00:18:22.096* [basic_suit_el7] host=_random_host_from_dc_4(api, DC_NAME),*00:18:22.096* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 106, in _random_host_from_dc_4*00:18:22.097* [basic_suit_el7] return random.choice(_hosts_in_dc_4(api, dc_name))*00:18:22.097* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 100, in _hosts_in_dc_4*00:18:22.097* [basic_suit_el7] raise RuntimeError('Could not find hosts that are up in DC %s' % dc_name)*00:18:22.097* [basic_suit_el7] RuntimeError: Could not find hosts that are up in DC test-dc*00:18:22.097* [basic_suit_el7] Error while running thread*00:18:22.097* [basic_suit_el7] Traceback (most recent call last):*00:18:22.097* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue*00:18:22.098* [basic_suit_el7] queue.put({'return': func()})*00:18:22.098* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 803, in import_template_from_glance*00:18:22.098* [basic_suit_el7] generic_import_from_glance(api, image_name=CIRROS_IMAGE_NAME, image_ext='_glance_template', as_template=True)*00:18:22.098* [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 637, in generic_import_from_glance*00:18:22.098* [basic_suit_el7] target_image.import_image(import_action)*00:18:22.098* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 26017, in import_image*00:18:22.098* [basic_suit_el7] headers={"Correlation-Id":correlation_id}*00:18:22.098* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request*00:18:22.098* [basic_suit_el7] persistent_auth=self.__persistent_auth*00:18:22.099* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request*00:18:22.099* [basic_suit_el7] persistent_auth)*00:18:22.099* [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request*00:18:22.099* [basic_suit_el7] raise errors.RequestError(response_code, response_reason, response_body)*00:18:22.099* [basic_suit_el7] RequestError: *00:18:22.099* [basic_suit_el7] status: 400*00:18:22.099* [basic_suit_el7] reason: Bad Request*00:18:22.099* [basic_suit_el7] detail: Cannot import Virtual Disk: Storage Domain cannot be accessed.*00:18:22.099* [basic_suit_el7] -Please check that at least one Host is operational and Data Center state is up. -- 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>

7 21

vdsm-ppc64le builds is not deployed to ovirt-master-snapshot
by Sandro Bonazzola 12 Apr '17

12 Apr '17

The x86_64 job[1] has a downstream project[2] taking care of deploying the build to the repos while the ppc64le[3] hasn't. Result is that ovirt-master-snapshot is not receiving updates for ppc64le and is currently failing repository closure: *00:02:47.636* Error: Package: vdsm-gluster-4.20.0-612.git378d837.el7.centos.noarch (ovirt-master-snapshot)*00:02:47.637* Requires: vdsm = 4.20.0-612.git378d837.el7.centos*00:02:47.637* Installing: vdsm-4.18.999-925.git195c44e.el7.centos.ppc64le (ovirt-master-snapshot)*00:02:47.637* vdsm = 4.18.999-925.git195c44e.el7.centos*00:02:47.637* Error: Package: vdsm-hook-ethtool-options-4.20.0-612.git378d837.el7.centos.noarch (ovirt-master-snapshot)*00:02:47.637* Requires: vdsm = 4.20.0-612.git378d837.el7.centos*00:02:47.637* Installing: vdsm-4.18.999-925.git195c44e.el7.centos.ppc64le (ovirt-master-snapshot)*00:02:47.637* vdsm = 4.18.999-925.git195c44e.el7.centos Please fix vdsm job for triggering deploy-to-ovirt_experimental_master [1] http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/ [2] http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/ [3] http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/ -- 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>

2 1

planned Jenkins restart
by Evgheni Dereveanchin 11 Apr '17

11 Apr '17

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new builds will be scheduled during this maintenance period. I will inform you once it is over. Regards, Evgheni Dereveanchin

1 1

Failed to execute stage 'Misc configuration': Command '/usr/bin/ovirt-aaa-jdbc-tool' failed to execute
by Sandro Bonazzola 11 Apr '17

11 Apr '17

engine-setup: 2017-04-11 09:43:29,659-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/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/config/aaajdbc.py", line 384, in _misc self._setupAdminUser() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/config/aaajdbc.py", line 284, in _setupAdminUser name=adminUser, File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/config/aaajdbc.py", line 64, in _userExists envAppend=toolEnv, File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 931, in execute command=args[0], RuntimeError: Command '/usr/bin/ovirt-aaa-jdbc-tool' failed to execute /usr/bin/ovirt-aaa-jdbc-tool: 2017-04-11 09:43:29,659-0400 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.config.aaajdbc plugin.execute:926 execute-output: ('/usr/bin/ovirt-aaa-jdbc-tool', '--db-config=/etc/ovirt-engine/aaa/internal.pro perties', 'query', '--what=user', '--pattern=name=admin') stderr: Exception in thread "main" org.jboss.modules.ModuleLoadError: Error loading module from /usr/share/ovirt-engine/modules/tools/org/slf4j/main/module.xml at org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.java:74) at org.jboss.modules.Module.getPathsUnchecked(Module.java:1435) at org.jboss.modules.Module.loadModuleClass(Module.java:601) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) at org.ovirt.engine.extension.aaa.jdbc.binding.cli.Cli.<clinit>(Cli.java:87) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at org.jboss.modules.Module.run(Module.java:320) at org.jboss.modules.Main.main(Main.java:505) Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add resource root 'slf4j-jdk14.jar' at path 'slf4j-jdk14.jar' (position: END_TAG seen ...path="slf4j-api.jar"/>\n <resource-root path="slf4j- jdk14.jar"/>... @11:44) caused by: java.io.FileNotFoundException: /usr/share/ovirt-engine/modules/tools/org/slf4j/main/slf4j-jdk14.jar (File o directory non esistente) at org.jboss.modules.xml.ModuleXmlParser.parseResourceRoot(ModuleXmlParser.java:891) at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleXmlParser.java:735) at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:535) at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXmlParser.java:340) at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:226) at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:204) at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:170) at org.jboss.modules.LocalModuleFinder.lambda$findModule$0(LocalModuleFinder.java:149) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:144) at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:439) at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:342) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:289) at org.jboss.modules.Module.addPaths(Module.java:1079) at org.jboss.modules.Module.link(Module.java:1449) at org.jboss.modules.Module.getPaths(Module.java:1410) at org.jboss.modules.Module.getPathsUnchecked(Module.java:1433) ... 10 more # rpm -qf /usr/bin/ovirt-aaa-jdbc-tool ovirt-engine-extension-aaa-jdbc-1.1.5-0.0.master.git2a03d42.el7.centos.noarch # rpm -qv ovirt-engine ovirt-engine-4.2.0-0.0.master.20170408115943.gitea6bd62.el7.centos.noarch -- 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>

2 3

[ OST Failure Report ] [ oVirt master ] [ 9/4/2017 ] [ add_secondary_storage_domains ]
by Barak Korren 10 Apr '17

10 Apr '17

Test failed: [ add_secondary_storage_domains ] Link to suspected patches: - https://gerrit.ovirt.org/#/c/74779/ Link to Job: - http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6257/ Link to all logs: - http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6257/artif… Error snippet from log: <error> detail: Cannot import Virtual Disk: Storage Domain cannot be accessed. -Please check that at least one Host is operational and Data Center state is up. ... AssertionError: False != True after 600 seconds </error> -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

6 9

oVirt repositories 101; or everything you wanted to know about oVirt repositories and didn't ask
by Eyal Edri 09 Apr '17

09 Apr '17

Hi oVirt developers and users, Some of you might be familiar with the oVirt repositories and all their flavors, while some of you are just familiar with the official releases. The fact is, we have plenty of them and each has its own role and a right usage. Moreover, we did a significant overhaul on all the repositories in the past months, So hopefully now it will be easier to explain which repo to use when. I'll start with reviewing each oVirt repository and give a bit of background and the logic behind it, how to consume it and the relevant usage for it. For simplicity, I'll review the repositories on the 4.1 release, but it valid for all other oVirt releases ( except 'master' which doesn't have an official or pre-release repositories ). I will also upload this information to the oVirt.org site, but since this is important, I didn't want to wait with the sending this email. *oVirt repositories* *Official repositories* *Desc:* here you can find the official signed oVirt RPMs, immediately after an official release has been done. *Path:* http://resources.ovirt.org/pub/ovirt-4.1/rpm/$distro *Update frequency:* on every oVirt release, usually happens on a monthly cadence. *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm *Who should use it? * oVirt users, developers or anyone who wants a final and official release *Pre-release repositories* *Desc:* here you can find the pre-release bits of oVirt RC builds, just before they are released. *Path:* http://resources.ovirt.org/pub/ovirt-4.1-pre/rpm/$distro *Update frequency:* usually on a weekly or bi-weekly basis *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt- release41-pre.rpm *Who should use it? * oVirt users, developers or anyone who wants to try out oVirt new version before its out, Keeping in mind this isn't a fully verified release and might still have critical bugs which are not fixed yet. Packages in this repo are verified by automation and checked by humans for basic sanity before publishing. *Nightly snapshot (verified) repositories* *Desc:* here you can find the nightly snapshot of RPMs, which passed basic sanity by our 'oVirt System Tests' framework in the oVirt CI system. *Path:* http://resources.ovirt.org/pub/ovirt-4.1-snapshot/rpm/$distro *Update frequency:* Every night *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt- release41-snapshot.rpm *Who should use it? * oVirt users, developers or anyone who wants to try out oVirt latest bits right of the build oven! We trust our system tests, which already run more than 40 various tests such as 'add host', 'create VM', 'live migration' and more! *** Important note: the snapshot repositories are verified only in master currently, we might do the same for 4.1 soon, as we see no issues with master so far ** * *The above repos should suffice to most usres and developers, but if you feel its not enough and you still need a faster verified repo, look below! * *Advanced oVirt repositories* *Builds artifacts repo* *Desc:* This is a new feature from oVirt 'standard CI' project, where each 'build-artifacts' job is actually a yum repo as well. *Path:* http://jenkins.ovirt.org/job/ovirt-engine_4.1_ build-artifacts-on-demand-el7-x86_64/lastSuccessfulBuild/ artifact/exported-artifacts ( example ) *Update frequency:* after each commit or 'ci please build' comment *Release rpm: *N/A *Who should use it? * oVirt developers who need latest RPMs from another oVirt project and cannot or need not wait for that project`s packages to pass OST". oVirt developers running manual OST job and need to test an open Gerrit patch, using the 'ci please build' command. *Tested repositories* *Desc:* The tested repositories hold all the oVIrt packages which passed CI ( similar to snapshot repos ) and retain also version history for X versions back. *Path:* http://resources.ovirt.org/repos/ovirt/tested/4.1/rpm/$distro *Update frequency:* after each 'build artifacts' job is triggered by any oVirt project and if the packages passed sanity checks *Release rpm: *N/A *Who should use it? * If you want to have latest and greatest oVirt packages and can't wait for the nightly repo. If you are testing upgrades or need more than one version of a pacakge in your repo. *Experimental repositories * *Desc:* Internal CI repos which are a part of the 'experimental' flow which runs OST on each built package. *Path:* http://resources.ovirt.org/repos/ovirt/experimental/ 4.1/latest.tested/rpm/el7/$distro *Update frequency:* after each 'build artifacts' job is triggered by any oVirt project and if the packages passed sanity checks *Release rpm: *N/A *Who should use it? * *No one other than internal CI jobs.* These repos are constantly refreshed and RPMs are being removed from them, so they are very prone to errors, please don't use them. I hope this makes a bit of order in all the repos and how to use them. If you still have questions, please don't hesitate to contact the infra team at infra(a)ovirt.org or just reply to this thread. -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

ovirt-engine dependencies and packaging plans for 4.2
by Sandro Bonazzola 08 Apr '17

08 Apr '17

In https://bugzilla.redhat.com/show_bug.cgi?id=1439518 I'm suggesting a packaging change for ovirt-engine allowing to reduce the space needed to install a minimal ovirt-engine. Martin says: We should get rid of PostgreSQL RPM dependency when we move to SCL version of PG9.5/9.6, which is planned fo 4.2 Do we have a bz to track it? How engine-setup can upgrade from a non-scl to a scl postgres setup? Who's going to handle it? Following up from https://bugzilla.redhat.com/show_bug.cgi?id=1439518#c1 Do we have plans to split userportal/backend to their own containers at some point? -- 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>

3 2

[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