- Devel - oVirt List Archives

how to generate engine's pki to talk to vdsm
by pengyixiang 18 Sep '17

18 Sep '17

------=_Part_41210_154884496.1505698817143 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: base64 aGVsbG8sIGV2ZXJ5IQogICAgIHdoYXQgc2hvdWxkIGkgZG8gdG8gZ2VuZXJhdGUgZmlsZXMgaW4g L2hvbWUvcGVuY2MvdGVzdC9vdmlydC1lbmdpbmUtaW5zdGFsbGVkL2V0Yy9vdmlydC1lbmdpbmUv ZW5naW5lLmNvbmYuZC8xMC1zZXR1cC1wa2kuY29uZiBmb3IgdGFsa2luZyB0byB2ZHNtLgpsaWtl IGdlbmVyYXRlIEVOR0lORV9QS0lfVFJVU1RfU1RPUkUgYW5kIEVOR0lORV9QS0lfRU5HSU5FX1NU T1JFLiBzaG91bGQgaSBjb3BlZCB0aGF0IHRvIHZkc20/IGhhdmUgc29tZSBkb2N1bWVudD8KClRo YW5rcyBpbiBBZHZhbmNlIQo= ------=_Part_41210_154884496.1505698817143 Content-Type: text/html; charset=GBK Content-Transfer-Encoding: base64 PGRpdiBzdHlsZT0ibGluZS1oZWlnaHQ6MS43O2NvbG9yOiMwMDAwMDA7Zm9udC1zaXplOjE0cHg7 Zm9udC1mYW1pbHk6QXJpYWwiPjxkaXY+aGVsbG8sIGV2ZXJ5ITwvZGl2PjxkaXY+Jm5ic3A7Jm5i c3A7Jm5ic3A7Jm5ic3A7IHdoYXQgc2hvdWxkIGkgZG8gdG8gZ2VuZXJhdGUgZmlsZXMgaW4gL2hv bWUvcGVuY2MvdGVzdC9vdmlydC1lbmdpbmUtaW5zdGFsbGVkL2V0Yy9vdmlydC1lbmdpbmUvZW5n aW5lLmNvbmYuZC8xMC1zZXR1cC1wa2kuY29uZiBmb3IgdGFsa2luZyB0byB2ZHNtLjwvZGl2Pjxk aXY+bGlrZSBnZW5lcmF0ZSBFTkdJTkVfUEtJX1RSVVNUX1NUT1JFIGFuZCBFTkdJTkVfUEtJX0VO R0lORV9TVE9SRS4gc2hvdWxkIGkgY29wZWQgdGhhdCB0byB2ZHNtPyBoYXZlIHNvbWUgZG9jdW1l bnQ/IDxicj48L2Rpdj48ZGl2PlRoYW5rcyBpbiBBZHZhbmNlITxicj48L2Rpdj48L2Rpdj48YnI+ PGJyPjxzcGFuIHRpdGxlPSJuZXRlYXNlZm9vdGVyIj48cD4mbmJzcDs8L3A+PC9zcGFuPg== ------=_Part_41210_154884496.1505698817143--

2 1

[Vdsm] Move to Fedora 26?
by Milan Zamazal 15 Sep '17

15 Sep '17

Hi, now when new CentOS is available we can use new libvirt. However in order to use the updated libvirt and not to make our CI automation fail we need current Fedora too. Could we update our requirements and automation to Fedora 26 virt-preview? Thanks, Milan

2 2

[Vdsm] CI problems with new CentOS
by Milan Zamazal 14 Sep '17

14 Sep '17

Hi, Jenkins fails now on no-longer available repo http://mirror.centos.org/centos/7/virt/x86_64/ovirt-4.0/ defined in Vdsm automation. It has already been fixed in OST (https://gerrit.ovirt.org/81729) could a similar or another fix be applied to Vdsm as well? Thanks, Milan

3 2

[review][vdsm] please review https://gerrit.ovirt.org/#/q/topic:drivemonitor_event+status:open
by Francesco Romani 14 Sep '17

14 Sep '17

Hi everyone, https://gerrit.ovirt.org/#/q/topic:drivemonitor_event+status:open is ready for review. It is the first part of the series needed to consume the BLOCK_THRESHOLD event available with libvirt >= 3.2.0 and QEMU >= 2.3.0. Once completed, this patchset will allow Vdsm to avoid polling, thus greatly improving the system performance and eventually close https://bugzilla.redhat.com/show_bug.cgi?id=1181665 Please note that: 1. CI fails because the workers are not yet updated to CentOS 7.4 (not yet released AFAIK!) which will provide libvirt >= 3.2.0. 2. Few more simple patches will be needed to enable/disable monitoring in specific flows where we cannot use events (e.g. LSM) 3. I did initial verification successfully, installing fedora 25 on thin provisioned disk without issue. -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

3 3

[ OST Failure Report ] [ oVirt master ] [ 2017-09-11 ]
by Dusan Fodor 14 Sep '17

14 Sep '17

Link to suspected patch: https://gerrit.ovirt.org/#/c/80993/19 Link to job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2498/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2498/artifact… Error snippet from log: <error> DEBUG util.py:533: Executing command: ['/usr/bin/yum', '--installroot', '/var/lib/mock/epel-7-x86_64-01b5c106167c9b71f022fe64bb4fa43a-167519/root/', '--releasever', '7', 'install', '@buildsys-build', 'grubby', 'lago', 'lago-ovirt', 'ovirt-engine-sdk-python', 'python-netaddr', 'python-ovirt-engine-sdk4', '--setopt=tsflags=nocontexts'] with env {'LANG': 'en_US.UTF-8', 'LD_PRELOAD': '/var/tmp/tmp.mock.RxN7kZ/$LIB/nosync.so', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'LC_MESSAGES': 'C.UTF-8', 'STD_CI_STAGE': 'basic_suite_master', 'http_proxy': 'http://proxy01.phx.ovirt.org:3128', 'STD_CI_YUMREPOS': '', 'STD_CI_DISTRO': 'el7', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'HOME': '/builddir', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False DEBUG util.py:450: Failed to set locale, defaulting to C DEBUG util.py:450: Error: Package: python-lago-0.41.0-1.el7.centos.noarch (lago) DEBUG util.py:450: Requires: qemu-kvm-rhev >= 2.1.2 DEBUG util.py:450: Error: Package: python-lago-0.41.0-1.el7.centos.noarch (lago) DEBUG util.py:450: Requires: qemu-img-rhev >= 2.1.2 </error>

5 7

Engine fails to start due to server error
by Maor Lipchuk 14 Sep '17

14 Sep '17

Hi all, I've fetched rebased my env and updated my DB and now I've encountered an issue that I can't start my engine, I get the following error, see [1]. It seems that as part of the Backend startup we call DBConfigUtils. and once the config value of DBI18NPrefix is being added, it is dependent on DBEngine, and when trying to get the value of DBEngine it looks like that this value was not initialized yet in the _vdcOptionCache at DBConfigUtils and throws the error. Is there something I'm missing? Regards, Maor [1] 2017-09-14 16:30:49,024+03 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 53) MSC000001: Failed to start service jboss.deployment.subunit."engine.ear"."bll.jar".component.B ackend.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_121] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_121] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121] at org.jboss.threads.JBossThread.run(JBossThread.java:320) Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:124) at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:138) at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] ... 6 more Caused by: javax.ejb.EJBException: java.lang.IllegalArgumentException: DBEngine has no value for version: general at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInNoTx(CMTTxInterceptor.java:213) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:265) at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:374) at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:70) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.ejb3.component.singleton.StartupCountDownInterceptor.processInvocation(StartupCountDownInterceptor.java:25)

2 3

OST failures
by Dusan Fodor 14 Sep '17

14 Sep '17

Hello all, the current higher amount of OST failures is expected, as they're mostly caused by CentOS 7.4 release. We are working on fixes.

1 0

ovirt-jboss-modules-maven-plugin?
by Sandro Bonazzola 14 Sep '17

14 Sep '17

Hi, I see we ship ovirt-jboss-modules-maven-plugin.noarch-2.0.2-0.1.20160715.gitec01507.el7.centos on master and I was wandering why. Jenkins has only the following: http://jenkins.ovirt.org/job/ovirt-jboss-modules-maven-plugin_master_check-… which is not published anywhere. Is ovirt-jboss-modules-maven-plugin still used? can we just delete the job and the rpm from the master repo? -- 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

ovirt-system-tests started failing locally
by Marc Young 14 Sep '17

14 Sep '17

While rerunning some local tests, I encountered a new error: + lago ovirt deploy @ Deploy oVirt environment: # Deploy environment: * [Thread-2] Deploy VM lago-vagrant-engine: * [Thread-3] Deploy VM lago-vagrant-host-0: * [Thread-3] Deploy VM lago-vagrant-host-0: Success (in 0:00:45) STDERR + MAIN_NFS_DEV=disk/by-id/scsi-0QEMU_QEMU_HARDDISK_2 + ISCSI_DEV=disk/by-id/scsi-0QEMU_QEMU_HARDDISK_3 + NUM_LUNS=5 + EL7='release 7\.[0-9]' + main + install_deps + systemctl disable --now kdump.service + yum install -y --downloaddir=/dev/shm nfs-utils rpcbind lvm2 targetcli sg3_utils iscsi-initiator-utils lsscsi policycoreutils-python Error: Package: gssproxy-0.7.0-4.el7.x86_64 (alocalsync) Requires: krb5-libs >= 1.15 Installed: krb5-libs-1.14.1-27.el7_3.x86_64 (installed) krb5-libs = 1.14.1-27.el7_3 Available: krb5-libs-1.14.1-26.el7.i686 (base) krb5-libs = 1.14.1-26.el7 - STDERR + MAIN_NFS_DEV=disk/by-id/scsi-0QEMU_QEMU_HARDDISK_2 + ISCSI_DEV=disk/by-id/scsi-0QEMU_QEMU_HARDDISK_3 + NUM_LUNS=5 + EL7='release 7\.[0-9]' + main + install_deps + systemctl disable --now kdump.service + yum install -y --downloaddir=/dev/shm nfs-utils rpcbind lvm2 targetcli sg3_utils iscsi-initiator-utils lsscsi policycoreutils-python Error: Package: gssproxy-0.7.0-4.el7.x86_64 (alocalsync) Requires: krb5-libs >= 1.15 Installed: krb5-libs-1.14.1-27.el7_3.x86_64 (installed) krb5-libs = 1.14.1-27.el7_3 Available: krb5-libs-1.14.1-26.el7.i686 (base) krb5-libs = 1.14.1-26.el7 * [Thread-2] Deploy VM lago-vagrant-engine: ERROR (in 0:01:05) Error while running thread 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 "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1610, in _deploy_host (script, ret, host.name(), ), RuntimeError: /home/myoung/repos/github/ovirt-system-tests/deployment-vagrant/default/scripts/_home_myoung_repos_github_ovirt-system-tests_vagrant_.._common_deploy-scripts_setup_storage_unified_el7.sh failed with status 1 on lago-vagrant-engine Error while running thread 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 "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1610, in _deploy_host (script, ret, host.name(), ), RuntimeError: /home/myoung/repos/github/ovirt-system-tests/deployment-vagrant/default/scripts/_home_myoung_repos_github_ovirt-system-tests_vagrant_.._common_deploy-scripts_setup_storage_unified_el7.sh failed with status 1 on lago-vagrant-engine # Deploy environment: ERROR (in 0:01:05) @ Deploy oVirt environment: ERROR (in 0:01:05) Its the same error as here: http://jenkins.ovirt.org/view/oVirt%20system% 20tests/job/ovirt-system-tests_master_check-patch-el7-x86_64/1683/console

5 9

All ConfigValues MUST be in database
by Miroslava Voglova 13 Sep '17

13 Sep '17

Hi, to master was merged patch that removed default values for engine options [1]. Now all values are present in 0000_config. For adding new engine option, besides adding it in ConfigValues, add it also into 0000_config (using procedure *fn_db_add_config_value* or *fn_db_add_config_value_for_versions_up_to*). Thanks, Mirka [1] https://gerrit.ovirt.org/#/c/81464/ <https://gerrit.ovirt.org/#/c/81464/>

1 0