- Devel - oVirt List Archives

[VDSM] STOMP tests failures
by Nir Soffer 08 Mar '16

08 Mar '16

Hi all, We are seeing the following error randomly - there must be a timing issue in the test, or maybe in the code? Pitor, can you check this? (From http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/3568/conso…) 13:33:28 ====================================================================== 13:33:28 ERROR: test_echo(1024, False) (stompTests.StompTests) 13:33:28 ---------------------------------------------------------------------- 13:33:28 Traceback (most recent call last): 13:33:28 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/testlib.py", line 73, in wrapper 13:33:28 return f(self, *args) 13:33:28 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/stompTests.py", line 83, in test_echo 13:33:28 str(uuid4())), 13:33:28 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/__init__.py", line 339, in callMethod 13:33:28 raise JsonRpcNoResponseError(methodName) 13:33:28 JsonRpcNoResponseError: [-32605] No response for JSON-RPC echo request. 13:33:28 -------------------- >> begin captured logging << -------------------- 13:33:28 vds.MultiProtocolAcceptor: INFO: Listening at ::1:38659 13:33:28 Scheduler: DEBUG: Starting scheduler test.Scheduler 13:33:28 Scheduler: DEBUG: started 13:33:28 Executor: DEBUG: Starting executor 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/0 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/1 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/2 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/3 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/4 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/5 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/6 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/7 13:33:28 Executor: DEBUG: Worker started 13:33:28 vds.MultiProtocolAcceptor: DEBUG: Adding detector <vdsm.rpc.bindingxmlrpc.XmlDetector instance at 0x7f9e4b3e9a70> 13:33:28 vds.MultiProtocolAcceptor: DEBUG: Adding detector <yajsonrpc.stompreactor.StompDetector instance at 0x7f9e4b3e9ab8> 13:33:28 FakeClientIf: INFO: XMLRPC server running 13:33:28 ProtocolDetector.AcceptorImpl: INFO: Accepting connection from ::1:39788 13:33:28 ProtocolDetector.Detector: DEBUG: Using required_size=11 13:33:28 ProtocolDetector.Detector: INFO: Detected protocol stomp from ::1:39788 13:33:28 Broker.StompAdapter: INFO: Processing CONNECT request 13:33:28 jsonrpc.AsyncoreClient: DEBUG: Sending response 13:33:28 yajsonrpc.protocols.stomp.AsyncClient: DEBUG: Stomp connection established 13:33:28 Broker.StompAdapter: INFO: Subscribe command received 13:33:28 jsonrpc.JsonRpcServer: DEBUG: Calling 'echo' in bridge with [u'Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut en'] 13:33:29 jsonrpc.JsonRpcServer: DEBUG: Return 'echo' in bridge with Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut en 13:33:29 protocoldetector.StompDetector: DEBUG: Stomp detected from ('::1', 39788) 13:33:29 vds.MultiProtocolAcceptor: DEBUG: Stopping Acceptor 13:33:29 jsonrpc.JsonRpcServer: INFO: Stopping JsonRPC Server 13:33:29 Executor: DEBUG: Stopping executor 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/7 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/2 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/3 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/0 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/1 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/6 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/5 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/4 13:33:29 FakeClientIf: INFO: Stopping XMLRPC server 13:33:29 FakeClientIf: INFO: XMLRPC server stopped 13:33:29 Scheduler: DEBUG: Stopping scheduler test.Scheduler 13:33:29 Scheduler: DEBUG: stopped 13:33:29 --------------------- >> end captured logging << ---------------------

2 1

[URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed
by Sandro Bonazzola 08 Mar '16

08 Mar '16

Hi, I think I already raised the issue several times, but let me raise this again. VDSM building / automated versioning is badly broken. Currently, 3.6 snapshot is building: vdsm-4.17.19-32.git171584b.el7.centos.src.rpm <http://jenkins.ovirt.org/job/vdsm_3.6_build-artifacts-el7-x86_64/178/artifa…> because the last tag on the 3.6 branch was 4.17.19 and new tags have been created in different branches. This make impossible to upgrade from stable (4.17.23) to latest snapshot. This also break dependencies on other projects requiring the latest released version like hosted engine. Please fix the automated versioning system vdsm is currently using or get rid of it. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 23

[oVirt jenkins] Weekly report on open tasks for ovirt-engine
by jenkins＠ovirt.org 08 Mar '16

08 Mar '16

------=_Part_84_1710939013.1457436534280 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Files scanned: '**/*.java, **/*.py'. Strings searched: FIXME | TODO | @deprecated Report: http://jenkins.ovirt.org/job/ovirt-engine_master_scan-open-tasks_merged//45… ------=_Part_84_1710939013.1457436534280--

1 0

How can users use oVirtCli to complete "run once"?
by zhukaijie 08 Mar '16

08 Mar '16

As you know. In web, users can use "RUN ONCE" button to run a VM with some params (such as certain custom properties). But can oVirtCli be used to complete "RUN ONCE"? Thank you.

3 2

oVirt Integration Development Team weekly status - 2016-03-07
by Sandro Bonazzola 07 Mar '16

07 Mar '16

- oVirt integration open bugs: https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%… - 3.6.3 - Built and released oVirt 3.6.3 GA distribution - Built and released oVirt Live 3.6.3 GA media - Release notes: http://www.ovirt.org/release/3.6.3/ - Announce: http://lists.ovirt.org/pipermail/announce/2016-March/000237.html - Fixing latest blockers for 3.6.3 - Adding Fedora 23 support to ovirt-log-collector - Published documentation about HE upgrade from el6 3.5 to el7 3.6 - 4.0.0 - Re-factored ovirt-release package for easy Jenkins and NGN consumption - started 4.0 pre integration and migration from 3.6 testing - SpagoBi: progress packaging spagobi and spagobi-dependencies - Infra: - Fixed several jobs issues - CentOS Virt SIG: - Rafael joined CentOS Virt SIG - CentOS Virt SIG - oVirt How To: http://wiki.centos.org/HowTos/oVirt - Meeting minutes will be available on https://www.centos.org/minutes/2016/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

master ovirt-engine requires ovirt-engine-sdk-python >= 4.0.0.0
by Yedidyah Bar David 07 Mar '16

07 Mar '16

Hi all, I am trying, on a rhel7 vm: yum install -y http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm yum install ovirt-engine Fails with: --> Finished Dependency Resolution Error: Package: ovirt-iso-uploader-4.0.0-0.0.master.20160208072812.gita433ce3.el7.centos.noarch (ovirt-master-snapshot) Requires: ovirt-engine-sdk-python >= 4.0.0.0 Available: ovirt-engine-sdk-python-3.6.0.3-1.el7.centos.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.0.3-1.el7.centos Available: ovirt-engine-sdk-python-3.6.2.1-1.el7.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.2.1-1.el7 Installing: ovirt-engine-sdk-python-3.6.3.0-1.el7.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.3.0-1.el7 Error: Package: ovirt-image-uploader-4.0.0-0.0.master.20160211135948.git43cc942.el7.centos.noarch (ovirt-master-snapshot) Requires: ovirt-engine-sdk-python >= 4.0.0.0 Available: ovirt-engine-sdk-python-3.6.0.3-1.el7.centos.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.0.3-1.el7.centos Available: ovirt-engine-sdk-python-3.6.2.1-1.el7.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.2.1-1.el7 Installing: ovirt-engine-sdk-python-3.6.3.0-1.el7.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.3.0-1.el7 Tried also: yum install http://jenkins.ovirt.org/job/ovirt-engine-sdk_master_build-artifacts-el7-x8… which works, but does not satisfy the above dep. Should it? Any other place to find 4.0 python sdk? Thanks, -- Didi

4 6

nested hosts \ vdsm hooks on rhel 7.2
by emarcian 07 Mar '16

07 Mar '16

Hi, Has anyone ever used vdsm hooks in RHEL 7.2 on to of 3.6 ? I faced some issues with that, related to emulated machines [root@localhost ~]# tail -f /var/log/vdsm/vdsm.log |grep ':ERROR:' Thread-18::ERROR::2016-03-06 07:43:57,019::caps::195::root::(_get_emulated_machines_from_domain) Error while looking for kvm domain (x86_64) libvirt capabilities -Eldad

2 2

logging VDSM-generated libvirt XML properly
by Martin Polednik 07 Mar '16

07 Mar '16

Hello developers! I've been chasing a bug that lead me to an idea of improving our XML logging. Now, to see a VMs generated libvirt XML, we have to rely on vdsm.log. The issue is that the log is rotating and therefore, it is easy to miss the correct XML when dealing with busy hypervisor. Since we're built on libvirt, I was thinking of doing similar thinks that libvirt does with qemu commandline. Each running domain(VM) has it's command line logged in /var/log/libvirt/qemu/${vmname}. This is great for debugging as you can mostly just take the cmdline and restart the VM. There is an issue with using the cmdline directly - networking. Libvirt uses additional script to create and up a bridge. Therefore, it is easier to use the XML and shape it to one's needs. I propose that we properly log the generated XML in a similar fashion as libvirt generates the cmdline. This means we would have path like /var/log/vdsm/libvirt/${vmname}, where generated XML would be stored. To minimize the logging requirements, only last definition of VM with that name may be stored. Additionally, exception level errors related to that VM could also be stored there. What do you think, can we afford the space and additional writes per VM to help the debugging process? Regards, mpolednik

2 2

In AIO environment, why engine and vdsm communicate timeout
by 李坚 07 Mar '16

07 Mar '16

4 3

Engine High Availability
by Sunny Shin 06 Mar '16

06 Mar '16

Hi All, In the new architecture page ( http://www.ovirt.org/documentation/architecture/architecture/) overall architecture picture shows that engine supports active-active high availability. However, as per engine HA page ( http://www.ovirt.org/develop/release-management/features/engine/engine-high…) active-active HA is not supported yet and there are several implementation issues. So, could anyone give me a brief explanation about discrepancy between these two pages, and about the plan to implement this feature if not implemented yet? Sunny

2 9