April 2016 - Devel - oVirt List Archives

Integration tests future (and very nice alternative for the DAO fixture file)
by Roman Mohr 04 Jul '16

04 Jul '16

Hi all, In [1] you can find some patches which are meant to improve the test writing experience in ovirt-engine. They provide the following things: A) Domain Object builders which can be used for creating and/or persisting domain objects [2] B) DAO testing without writing fixtures because of the builders C) Integration testing for commands in conjunction with a real database Arquillian, injectable commands and the builders [3] # How to run what? A) In normal unit tests just create a new instance of a builder and use it. This should help us to get rid of all the small createDefaultVm(), createHostWithX() helper methods in our tests. B) In dao tests just inject them and go ahead. The advantage of not using the fixture file is that we can now set up clean scenarios for every test in a setup method. See example 2 below on how easy it is to set up a new cluster. C) Arquillian integration tests need to be marked with "@Category(IntegrationTest.class)" and can inherit from TransactionalTestBase. The @Category annotation makes sure that the integration tests are only run when mvn clean verify -DskipITs=false is invoked. Note that these tests are then executed in the integration test phase of maven. For them we use the maven-failsafe-plugin[5] which will also make sure that the testing database is up to date. See [4] for more details. # Examples 1) Add a running VM to a host, persist everything to the database and load all VMs which are running on the host: VDS host = vdsBuilder.cluster(persistedCluster).persist(); vmBuilder.host(host).up().persist(); List<VM> vms = vmDao.getAllRunningForVds(host.getId()); 2) Add 10 hosts with 1 GB of RAM to a cluster, persist the hosts to the database in a DAO test: public class MyHostDaoTest extends BaseDaoTestCase { @Inject private VdsBuilder vdsBuilder; @Test public void createHosts() { VdsBuilder builder = vdsBuilder.cluster(persistedCluster).physicalMemory(1000); for (int x =0; x < 10; x++){ builder.id(Guid.newGuid()).persist(); } } } 3) Full integration test with arquillian and the database @Category(IntegrationTest.class) public class VmDaoIntegrationTest extends TransactionalTestBase { @Inject VmDao vmDao; private final Guid VM1_GUID = Guid.createGuidFromString("0fe4bc81-5999-4ab6-80f8-7a4a2d4bfacd"); @Deployment public static JavaArchive deploy(){ return createDeployment(); } @Test public void shouldFailOnExistingEntity() { vmBuilder.id(VM1_GUID).cluster(clusterBuilder.reset().persist()).persist(); // This uses assertThat from assertj: assertThat(vmDao.get(VM1_GUID)).isNotNull(); } } 4) Using the builders in a normal unit test without a database: VM vm = new VmBuilder().id(Guid.newGuid()).up().build(); # How to add your own Domain objects? There are just a few simple rules: 1) Your builder should extend org.ovirt.engine.core.builder.AbstractBuilder 2) Make sure that you only access DAOs injected into the builder during #prePersist() and #persist(). This allows to use the #build() method also without injections 3) #prePersist() should set all fields which are necessary to suffice database constraints. The fields should only be set if they are not already set before by the builder. When following this rule we can always persist new objects to the database by simply calling myBuilder.reset().persist(). 4) Mark your builder with @Repository to make them useable for our Spring DAO tests and our Arquillian integration tests. So have a look at the patches at [1] and let me know what you think about them. Best Regards and happy testing, Roman [1] https://gerrit.ovirt.org/#/q/topic:integration [2] https://gerrit.ovirt.org/#/c/47008/17 [3] https://gerrit.ovirt.org/#/c/47007/10 [4] https://gerrit.ovirt.org/#/c/47008/17 [5] https://maven.apache.org/surefire/maven-failsafe-plugin/

5 7

Progress report on Vdsm Debian packaging
by Milan Zamazal 21 May '16

21 May '16

I made progress with Debian packaging of Vdsm. We have all the supporting packages (cpopen, ioprocess, mom, pthreading, safelease, sanlock) in Debian now. I took over maintenance of sanlock Debian package, updated it and made a lot of fixes, including preparing the previously unavailable python-sanlock package. As for Vdsm itself, the package can be installed now and Vdsm can be started. It doesn't work with Engine, which is no big surprise. We can't simply reinstall a Debian host from Engine, so we need to find some way how to initialize the host properly. And it's likely there are distribution specific pieces inside Vdsm and elsewhere. All the package sources, including not yet uploaded Vdsm package, are available on http://git.debian.org . How you can help: - Obviously, we need to make Vdsm hosts working, so any help in this area is welcome. - Reviewing and testing Vdsm Debian package (without actually using it) is also very helpful, I'm sure there are things to fix or improve. - There are some Lintian warnings in the packages, fixing them would be nice. - We should also review Debian patches in the packages, decide what should be changed upstream and report it. - You can help with anything else you consider useful.

4 6

[VDSM] flaky networking test
by Nir Soffer 01 May '16

01 May '16

Hi all, I think we have a pending patch for this, perhaps we should merge it? 19:32:54 ====================================================================== 19:32:54 ERROR: test_local_auto_with_dynamic_address_from_ra (network.netinfo_test.TestIPv6Addresses) 19:32:54 ---------------------------------------------------------------------- 19:32:54 Traceback (most recent call last): 19:32:54 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/testValidation.py", line 97, in wrapper 19:32:54 return f(*args, **kwargs) 19:32:54 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/network/netinfo_test.py", line 446, in test_local_auto_with_dynamic_address_from_ra 19:32:54 self.assertEqual('link', ip_addrs[1]['scope']) 19:32:54 File "/usr/lib64/python2.7/contextlib.py", line 24, in __exit__ 19:32:54 self.gen.next() 19:32:54 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/network/nettestlib.py", line 405, in dnsmasq_run 19:32:54 server.stop() 19:32:54 File "/usr/lib64/python2.7/contextlib.py", line 24, in __exit__ 19:32:54 self.gen.next() 19:32:54 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/network/firewall.py", line 45, in allow_dhcp 19:32:54 _forbid_dhcp(iface) 19:32:54 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/network/firewall.py", line 89, in _forbid_dhcp 19:32:54 '67', '-j', 'ACCEPT']) # DHCPv4 19:32:54 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/network/firewall.py", line 110, in _execCmdChecker 19:32:54 command, out, err)) 19:32:54 FirewallError: Command ['/sbin/iptables', '-D', 'INPUT', '-i', 'veth_qjA94YJwY8', '-p', 'udp', '--sport', '68', '--dport', '67', '-j', 'ACCEPT'] failed with []; ['Another app is currently holding the xtables lock. Perhaps you want to use the -w option?'] 19:32:54 -------------------- >> begin captured logging << -------------------- 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link add name veth_qjA94YJwY8 type veth peer name veth_NLC6ccMcUU (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /usr/sbin/dnsmasq --dhcp-authoritative -p 0 --dhcp-option=3 --dhcp-option=6 -i veth_qjA94YJwY8 -I lo -d --bind-dynamic --enable-ra --dhcp-range=2001:1:1:1::,slaac,2m (cwd None) 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/service iptables status (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = 'Redirecting to /bin/systemctl status iptables.service\nRunning in chroot, ignoring request.\n'; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/iptables --wait -I INPUT -i veth_qjA94YJwY8 -p udp --sport 68 --dport 67 -j ACCEPT (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/iptables --wait -I INPUT -i veth_qjA94YJwY8 -p udp --sport 546 --dport 547 -j ACCEPT (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link set dev veth_NLC6ccMcUU up (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link set dev veth_qjA94YJwY8 up (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip -6 addr add dev veth_qjA94YJwY8 2001:1:1:1::1/64 (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:54 root: DEBUG: dnsmasq: started, version 2.75 DNS disabled 19:32:54 dnsmasq: compile time options: IPv6 GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC loop-detect inotify 19:32:54 dnsmasq: warning: interface veth_qjA94YJwY8 does not currently exist 19:32:54 dnsmasq-dhcp: router advertisement on 2001:1:1:1:: 19:32:54 dnsmasq-dhcp: IPv6 router advertisement enabled 19:32:54 dnsmasq-dhcp: RTR-SOLICIT(veth_qjA94YJwY8) ce:82:16:6e:a5:7d 19:32:54 dnsmasq-dhcp: RTR-ADVERT(veth_qjA94YJwY8) 2001:1:1:1:: 19:32:54 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/service iptables status (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = 'Redirecting to /bin/systemctl status iptables.service\nRunning in chroot, ignoring request.\n'; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/iptables -D INPUT -i veth_qjA94YJwY8 -p udp --sport 68 --dport 67 -j ACCEPT (cwd None) 19:32:55 root: DEBUG: FAILED: <err> = 'Another app is currently holding the xtables lock. Perhaps you want to use the -w option?\n'; <rc> = 4 19:32:55 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link del dev veth_qjA94YJwY8 (cwd None) 19:32:55 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:55 --------------------- >> end captured logging << ---------------------

2 3

cannot create local ISO domain in RHEVM
by knarra 01 May '16

01 May '16

Hi, I am trying to set up Hosted Engine. I wanted to deploy windows virtual machines in this environment and as part of that i am creating ISO Domain to upload my windows image. But for some reason, while i create ISO domain it always fails with error "Failed to add Storage Domain <storagedomain_name"> and always remains in unattached state. Can some one please help me to reslove this issue? Attaching the vdsm logs. Thanks kasturi.

2 2

[REVIEW-REQUEST] Gluster Self-Heal Monitoring feature page
by Ramesh Nachimuthu 29 Apr '16

29 Apr '16

Hi, We are planning to implement "Gluster Self-Heal Monitoring" feature in oVirt 4.0. This is very important for host maintenance and host fencing flows in Ovirt-Gluster Hyperconvergence use cases. I have added a feature to discuss the feature in detail. Please review the same and provide your feedback. Feature Page: http://www.ovirt.org/develop/release-management/features/gluster-self-heal-… Regards, Ramesh

1 0

Vdsm api package
by Nir Soffer 29 Apr '16

29 Apr '16

Hi all, In the Vdsm call, we discussed a way to expose vdsm errors to its clients (e.g, engine, hosted engine agent/setup). The idea is to have a vdsmapi package, holding: - errors.py - all public errors - events.py - all events sent by vdsm - client.py - library for communicating with vdsm - schema.py - the client will use this to autogenerate online help and validate messages - schema.yaml - we probably need several files (gluster, events, etc.) This will allow other projects talking with vdsm to do: from vdsmapi import client, errors ... try: client.list(vmId="xxxyyy") except errors.NoSuchVM: ... (this is a fake example, the real api may be different) Engine can build-require vdsmapi, and generate java module with the public errors from vdsmapi/errors.py module, instead of keeping this hardcoded in engine, and updating it every time vdsm adds new public error. Vdsm will use this package when building response to clients. Edi was concerned about sharing the errors module, so maybe we need a package: vdsmapi/ errors/ network.py virt.py storage.py gluster.py We can still expose all the errors via errors/__init__.py, so clients do not have to care about the area of the application the error come from. Thoughts? Nir

5 7

[VDSM] Flaky stompTests tests
by Nir Soffer 29 Apr '16

29 Apr '16

Hi all, We see random failures in the stomp tests for long time. I suggest we mark these tests as broken for now. See examples at the end of the message. Nir ---- http://jenkins.phx.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/93/con… 17:53:09 ====================================================================== 17:53:09 ERROR: test_event(False) (stompTests.StompTests) 17:53:09 ---------------------------------------------------------------------- 17:53:09 Traceback (most recent call last): 17:53:09 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/testlib.py", line 74, in wrapper 17:53:09 return f(self, *args) 17:53:09 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/stompTests.py", line 110, in test_event 17:53:09 client.callMethod("event", [], str(uuid4())) 17:53:09 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/__init__.py", line 340, in callMethod 17:53:09 raise JsonRpcNoResponseError(methodName) 17:53:09 JsonRpcNoResponseError: [-32605] No response for JSON-RPC event request. 17:53:09 -------------------- >> begin captured logging << -------------------- 17:53:09 vds.MultiProtocolAcceptor: INFO: Listening at ::1:36333 17:53:09 Scheduler: DEBUG: Starting scheduler test.Scheduler 17:53:09 Scheduler: DEBUG: started 17:53:09 Executor: DEBUG: Starting executor 17:53:09 Executor: DEBUG: Starting worker jsonrpc.Executor/0 17:53:09 Executor: DEBUG: Worker started 17:53:09 Executor: DEBUG: Starting worker jsonrpc.Executor/1 17:53:09 Executor: DEBUG: Starting worker jsonrpc.Executor/2 17:53:09 Executor: DEBUG: Worker started 17:53:09 Executor: DEBUG: Starting worker jsonrpc.Executor/3 17:53:09 Executor: DEBUG: Worker started 17:53:09 Executor: DEBUG: Worker started 17:53:09 Executor: DEBUG: Starting worker jsonrpc.Executor/4 17:53:09 Executor: DEBUG: Worker started 17:53:09 Executor: DEBUG: Starting worker jsonrpc.Executor/5 17:53:09 Executor: DEBUG: Worker started 17:53:09 Executor: DEBUG: Starting worker jsonrpc.Executor/6 17:53:09 Executor: DEBUG: Worker started 17:53:09 Executor: DEBUG: Starting worker jsonrpc.Executor/7 17:53:09 Executor: DEBUG: Worker started 17:53:09 FakeClientIf: INFO: XMLRPC server running 17:53:09 vds.MultiProtocolAcceptor: DEBUG: Adding detector <vdsm.rpc.bindingxmlrpc.XmlDetector instance at 0x7f0191899488> 17:53:09 vds.MultiProtocolAcceptor: DEBUG: Adding detector <yajsonrpc.stompreactor.StompDetector instance at 0x7f01918994d0> 17:53:09 ProtocolDetector.AcceptorImpl: INFO: Accepting connection from ::1:39823 17:53:09 ProtocolDetector.Detector: DEBUG: Using required_size=11 17:53:09 ProtocolDetector.Detector: INFO: Detected protocol stomp from ::1:39823 17:53:09 jsonrpc.AsyncoreClient: DEBUG: Sending response 17:53:09 Broker.StompAdapter: INFO: Processing CONNECT request 17:53:09 yajsonrpc.protocols.stomp.AsyncClient: DEBUG: Stomp connection established 17:53:09 jsonrpc.JsonRpcServer: DEBUG: Calling 'event' in bridge with [] 17:53:09 jsonrpc.Notification: DEBUG: Sending event {"params": {"content": true, "notify_time": 6398709080}, "jsonrpc": "2.0", "method": "vdsm.event"} 17:53:09 jsonrpc.JsonRpcServer: DEBUG: Return 'event' in bridge with True 17:53:09 Broker.StompAdapter: INFO: Subscribe command received 17:53:09 protocoldetector.StompDetector: DEBUG: Stomp detected from ('::1', 39823) 17:53:09 vds.MultiProtocolAcceptor: DEBUG: Stopping Acceptor 17:53:09 jsonrpc.JsonRpcServer: INFO: Stopping JsonRPC Server 17:53:09 Executor: DEBUG: Stopping executor 17:53:09 Executor: DEBUG: Worker stopped 17:53:09 Executor: DEBUG: Worker stopped 17:53:09 Executor: DEBUG: Worker stopped 17:53:09 Executor: DEBUG: Worker stopped 17:53:09 Executor: DEBUG: Worker stopped 17:53:09 Executor: DEBUG: Worker stopped 17:53:09 Executor: DEBUG: Worker stopped 17:53:09 Executor: DEBUG: Worker stopped 17:53:09 Executor: DEBUG: Waiting for worker jsonrpc.Executor/0 17:53:09 Executor: DEBUG: Waiting for worker jsonrpc.Executor/7 17:53:09 Executor: DEBUG: Waiting for worker jsonrpc.Executor/2 17:53:09 Executor: DEBUG: Waiting for worker jsonrpc.Executor/1 17:53:09 Executor: DEBUG: Waiting for worker jsonrpc.Executor/5 17:53:09 Executor: DEBUG: Waiting for worker jsonrpc.Executor/3 17:53:09 Executor: DEBUG: Waiting for worker jsonrpc.Executor/6 17:53:09 Executor: DEBUG: Waiting for worker jsonrpc.Executor/4 17:53:09 FakeClientIf: INFO: Stopping XMLRPC server 17:53:09 FakeClientIf: INFO: XMLRPC server stopped 17:53:09 Scheduler: DEBUG: Stopping scheduler test.Scheduler 17:53:09 Scheduler: DEBUG: stopped 17:53:09 --------------------- >> end captured logging << --------------------- http://jenkins.phx.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/87/con… 17:14:24 ====================================================================== 17:14:24 ERROR: test_event(False) (stompTests.StompTests) 17:14:24 ---------------------------------------------------------------------- 17:14:24 Traceback (most recent call last): 17:14:24 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/testlib.py", line 74, in wrapper 17:14:24 return f(self, *args) 17:14:24 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/stompTests.py", line 110, in test_event 17:14:24 client.callMethod("event", [], str(uuid4())) 17:14:24 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/__init__.py", line 340, in callMethod 17:14:24 raise JsonRpcNoResponseError(methodName) 17:14:24 JsonRpcNoResponseError: [-32605] No response for JSON-RPC event request. 17:14:24 -------------------- >> begin captured logging << -------------------- 17:14:24 vds.MultiProtocolAcceptor: INFO: Listening at ::1:39663 17:14:24 Scheduler: DEBUG: Starting scheduler test.Scheduler 17:14:24 Scheduler: DEBUG: started 17:14:24 Executor: DEBUG: Starting executor 17:14:24 Executor: DEBUG: Starting worker jsonrpc.Executor/0 17:14:24 Executor: DEBUG: Worker started 17:14:24 Executor: DEBUG: Starting worker jsonrpc.Executor/1 17:14:24 Executor: DEBUG: Worker started 17:14:24 Executor: DEBUG: Starting worker jsonrpc.Executor/2 17:14:24 Executor: DEBUG: Starting worker jsonrpc.Executor/3 17:14:24 Executor: DEBUG: Worker started 17:14:24 Executor: DEBUG: Worker started 17:14:24 Executor: DEBUG: Starting worker jsonrpc.Executor/4 17:14:24 Executor: DEBUG: Worker started 17:14:24 Executor: DEBUG: Starting worker jsonrpc.Executor/5 17:14:24 Executor: DEBUG: Worker started 17:14:24 Executor: DEBUG: Starting worker jsonrpc.Executor/6 17:14:24 Executor: DEBUG: Worker started 17:14:24 Executor: DEBUG: Starting worker jsonrpc.Executor/7 17:14:24 Executor: DEBUG: Worker started 17:14:24 FakeClientIf: INFO: XMLRPC server running 17:14:24 vds.MultiProtocolAcceptor: DEBUG: Adding detector <vdsm.rpc.bindingxmlrpc.XmlDetector instance at 0x7fa3a183c6c8> 17:14:24 vds.MultiProtocolAcceptor: DEBUG: Adding detector <yajsonrpc.stompreactor.StompDetector instance at 0x7fa3a183c710> 17:14:24 ProtocolDetector.AcceptorImpl: INFO: Accepting connection from ::1:34641 17:14:24 ProtocolDetector.Detector: DEBUG: Using required_size=11 17:14:24 ProtocolDetector.Detector: INFO: Detected protocol stomp from ::1:34641 17:14:24 jsonrpc.AsyncoreClient: DEBUG: Sending response 17:14:24 Broker.StompAdapter: INFO: Processing CONNECT request 17:14:24 yajsonrpc.protocols.stomp.AsyncClient: DEBUG: Stomp connection established 17:14:24 jsonrpc.JsonRpcServer: DEBUG: Calling 'event' in bridge with [] 17:14:24 jsonrpc.Notification: DEBUG: Sending event {"params": {"content": true, "notify_time": 11313399420}, "jsonrpc": "2.0", "method": "vdsm.event"} 17:14:24 jsonrpc.JsonRpcServer: DEBUG: Return 'event' in bridge with True 17:14:24 Broker.StompAdapter: INFO: Subscribe command received 17:14:24 protocoldetector.StompDetector: DEBUG: Stomp detected from ('::1', 34641) 17:14:24 vds.MultiProtocolAcceptor: DEBUG: Stopping Acceptor 17:14:24 jsonrpc.JsonRpcServer: INFO: Stopping JsonRPC Server 17:14:24 Executor: DEBUG: Stopping executor 17:14:24 Executor: DEBUG: Worker stopped 17:14:24 Executor: DEBUG: Worker stopped 17:14:24 Executor: DEBUG: Worker stopped 17:14:24 Executor: DEBUG: Worker stopped 17:14:24 Executor: DEBUG: Worker stopped 17:14:24 Executor: DEBUG: Worker stopped 17:14:24 Executor: DEBUG: Worker stopped 17:14:24 Executor: DEBUG: Worker stopped 17:14:24 Executor: DEBUG: Waiting for worker jsonrpc.Executor/5 17:14:24 Executor: DEBUG: Waiting for worker jsonrpc.Executor/3 17:14:24 Executor: DEBUG: Waiting for worker jsonrpc.Executor/0 17:14:24 Executor: DEBUG: Waiting for worker jsonrpc.Executor/2 17:14:24 Executor: DEBUG: Waiting for worker jsonrpc.Executor/1 17:14:24 Executor: DEBUG: Waiting for worker jsonrpc.Executor/4 17:14:24 Executor: DEBUG: Waiting for worker jsonrpc.Executor/7 17:14:24 Executor: DEBUG: Waiting for worker jsonrpc.Executor/6 17:14:24 FakeClientIf: INFO: Stopping XMLRPC server 17:14:24 FakeClientIf: INFO: XMLRPC server stopped 17:14:24 Scheduler: DEBUG: Stopping scheduler test.Scheduler 17:14:24 Scheduler: DEBUG: stopped 17:14:24 --------------------- >> end captured logging << --------------------- http://jenkins.phx.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/82/con… 17:05:43 ====================================================================== 17:05:43 ERROR: test_event(False) (stompTests.StompTests) 17:05:43 ---------------------------------------------------------------------- 17:05:43 Traceback (most recent call last): 17:05:43 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/testlib.py", line 74, in wrapper 17:05:43 return f(self, *args) 17:05:43 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/stompTests.py", line 110, in test_event 17:05:43 client.callMethod("event", [], str(uuid4())) 17:05:43 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/__init__.py", line 340, in callMethod 17:05:43 raise JsonRpcNoResponseError(methodName) 17:05:43 JsonRpcNoResponseError: [-32605] No response for JSON-RPC event request. 17:05:43 -------------------- >> begin captured logging << -------------------- 17:05:43 Scheduler: DEBUG: stopped 17:05:43 vds.MultiProtocolAcceptor: INFO: Listening at ::1:37245 17:05:43 Scheduler: DEBUG: Starting scheduler test.Scheduler 17:05:43 Scheduler: DEBUG: started 17:05:43 Executor: DEBUG: Starting executor 17:05:43 Executor: DEBUG: Starting worker jsonrpc.Executor/0 17:05:43 Executor: DEBUG: Worker started 17:05:43 Executor: DEBUG: Starting worker jsonrpc.Executor/1 17:05:43 Executor: DEBUG: Worker started 17:05:43 Executor: DEBUG: Starting worker jsonrpc.Executor/2 17:05:43 Executor: DEBUG: Worker started 17:05:43 Executor: DEBUG: Starting worker jsonrpc.Executor/3 17:05:43 Executor: DEBUG: Worker started 17:05:43 Executor: DEBUG: Starting worker jsonrpc.Executor/4 17:05:43 Executor: DEBUG: Worker started 17:05:43 Executor: DEBUG: Starting worker jsonrpc.Executor/5 17:05:43 Executor: DEBUG: Worker started 17:05:43 Executor: DEBUG: Starting worker jsonrpc.Executor/6 17:05:43 Executor: DEBUG: Starting worker jsonrpc.Executor/7 17:05:43 Executor: DEBUG: Worker started 17:05:43 Executor: DEBUG: Worker started 17:05:43 FakeClientIf: INFO: XMLRPC server running 17:05:43 vds.MultiProtocolAcceptor: DEBUG: Adding detector <vdsm.rpc.bindingxmlrpc.XmlDetector instance at 0x7f27fb0d70e0> 17:05:43 vds.MultiProtocolAcceptor: DEBUG: Adding detector <yajsonrpc.stompreactor.StompDetector instance at 0x7f27fb0e2488> 17:05:43 ProtocolDetector.AcceptorImpl: INFO: Accepting connection from ::1:52346 17:05:43 ProtocolDetector.Detector: DEBUG: Using required_size=11 17:05:43 jsonrpc.AsyncoreClient: DEBUG: Sending response 17:05:43 ProtocolDetector.Detector: INFO: Detected protocol stomp from ::1:52346 17:05:43 Broker.StompAdapter: INFO: Processing CONNECT request 17:05:43 yajsonrpc.protocols.stomp.AsyncClient: DEBUG: Stomp connection established 17:05:43 jsonrpc.JsonRpcServer: DEBUG: Calling 'event' in bridge with [] 17:05:43 jsonrpc.Notification: DEBUG: Sending event {"params": {"content": true, "notify_time": 6397426400}, "jsonrpc": "2.0", "method": "vdsm.event"} 17:05:43 jsonrpc.JsonRpcServer: DEBUG: Return 'event' in bridge with True 17:05:43 Broker.StompAdapter: INFO: Subscribe command received 17:05:43 protocoldetector.StompDetector: DEBUG: Stomp detected from ('::1', 52346) 17:05:43 vds.MultiProtocolAcceptor: DEBUG: Stopping Acceptor 17:05:43 jsonrpc.JsonRpcServer: INFO: Stopping JsonRPC Server 17:05:43 Executor: DEBUG: Stopping executor 17:05:43 Executor: DEBUG: Worker stopped 17:05:43 Executor: DEBUG: Worker stopped 17:05:43 Executor: DEBUG: Worker stopped 17:05:43 Executor: DEBUG: Worker stopped 17:05:43 Executor: DEBUG: Worker stopped 17:05:43 Executor: DEBUG: Worker stopped 17:05:43 Executor: DEBUG: Worker stopped 17:05:43 Executor: DEBUG: Waiting for worker jsonrpc.Executor/6 17:05:43 Executor: DEBUG: Worker stopped 17:05:43 Executor: DEBUG: Waiting for worker jsonrpc.Executor/3 17:05:43 Executor: DEBUG: Waiting for worker jsonrpc.Executor/1 17:05:43 Executor: DEBUG: Waiting for worker jsonrpc.Executor/4 17:05:43 Executor: DEBUG: Waiting for worker jsonrpc.Executor/0 17:05:43 Executor: DEBUG: Waiting for worker jsonrpc.Executor/5 17:05:43 Executor: DEBUG: Waiting for worker jsonrpc.Executor/2 17:05:43 Executor: DEBUG: Waiting for worker jsonrpc.Executor/7 17:05:43 FakeClientIf: INFO: Stopping XMLRPC server 17:05:43 FakeClientIf: INFO: XMLRPC server stopped 17:05:43 Scheduler: DEBUG: Stopping scheduler test.Scheduler 17:05:43 Scheduler: DEBUG: stopped 17:05:43 --------------------- >> end captured logging << --------------------- http://jenkins.phx.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/72/con… 16:32:00 ====================================================================== 16:32:00 ERROR: test_echo(4096, False) (stompTests.StompTests) 16:32:00 ---------------------------------------------------------------------- 16:32:00 Traceback (most recent call last): 16:32:00 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/testlib.py", line 74, in wrapper 16:32:00 return f(self, *args) 16:32:00 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/stompTests.py", line 90, in test_echo 16:32:00 str(uuid4())), 16:32:00 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/__init__.py", line 340, in callMethod 16:32:00 raise JsonRpcNoResponseError(methodName) 16:32:00 JsonRpcNoResponseError: [-32605] No response for JSON-RPC echo request. 16:32:00 -------------------- >> begin captured logging << -------------------- 16:32:00 vds.MultiProtocolAcceptor: INFO: Listening at ::1:59025 16:32:00 Scheduler: DEBUG: Starting scheduler test.Scheduler 16:32:00 Scheduler: DEBUG: started 16:32:00 Executor: DEBUG: Starting executor 16:32:00 Executor: DEBUG: Starting worker jsonrpc.Executor/0 16:32:00 Executor: DEBUG: Worker started 16:32:00 Executor: DEBUG: Starting worker jsonrpc.Executor/1 16:32:00 Executor: DEBUG: Worker started 16:32:00 Executor: DEBUG: Starting worker jsonrpc.Executor/2 16:32:00 Executor: DEBUG: Worker started 16:32:00 Executor: DEBUG: Starting worker jsonrpc.Executor/3 16:32:00 Executor: DEBUG: Starting worker jsonrpc.Executor/4 16:32:00 Executor: DEBUG: Worker started 16:32:00 Executor: DEBUG: Worker started 16:32:00 Executor: DEBUG: Starting worker jsonrpc.Executor/5 16:32:00 Executor: DEBUG: Worker started 16:32:00 Executor: DEBUG: Starting worker jsonrpc.Executor/6 16:32:00 Executor: DEBUG: Starting worker jsonrpc.Executor/7 16:32:00 Executor: DEBUG: Worker started 16:32:00 Executor: DEBUG: Worker started 16:32:00 FakeClientIf: INFO: XMLRPC server running 16:32:00 vds.MultiProtocolAcceptor: DEBUG: Adding detector <vdsm.rpc.bindingxmlrpc.XmlDetector instance at 0x7f411903ecf8> 16:32:00 vds.MultiProtocolAcceptor: DEBUG: Adding detector <yajsonrpc.stompreactor.StompDetector instance at 0x7f411903ed40> 16:32:00 ProtocolDetector.AcceptorImpl: INFO: Accepting connection from ::1:49920 16:32:00 ProtocolDetector.Detector: DEBUG: Using required_size=11 16:32:00 ProtocolDetector.Detector: INFO: Detected protocol stomp from ::1:49920 16:32:00 Broker.StompAdapter: INFO: Processing CONNECT request 16:32:00 jsonrpc.AsyncoreClient: DEBUG: Sending response 16:32:00 Broker.StompAdapter: INFO: Subscribe command received 16:32:00 vds.dispatcher: ERROR: uncaptured python exception, closing channel <yajsonrpc.betterAsyncore.Dispatcher ('::1', 49920, 0, 0) at 0x7f411903ef38> (<type 'exceptions.AttributeError'>:'NoneType' object has no attribute 'command' [/usr/lib64/python2.7/asyncore.py|readwrite|108] [/usr/lib64/python2.7/asyncore.py|handle_read_event|449] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/betterAsyncore.py|handle_read|63] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/betterAsyncore.py|_delegate_call|137] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/protocoldetector.py|handle_read|125] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/stompreactor.py|handle_socket|481] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/rpc/bindingjsonrpc.py|add_socket|48] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/stompreactor.py|createListener|449] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/stompreactor.py|StompListener|415] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/betterAsyncore.py|__init__|39] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/betterAsyncore.py|switch_implementation|72] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/stompreactor.py|init|433] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/rpc/bindingjsonrpc.py|_onAccept|51] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/stompreactor.py|set_message_handler|297] [/usr/lib64/python2.7/asyncore.py|handle_read_event|449] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/betterAsyncore.py|handle_read|63] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/betterAsyncore.py|_delegate_call|137] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/stomp.py|handle_read|367] [/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/stompreactor.py|handle_frame|260]) 16:32:00 vds.dispatcher: WARNING: unhandled close event 16:32:00 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 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 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 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 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 '] 16:32:01 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 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 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 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 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 16:32:01 yajsonrpc.protocols.stomp.AsyncClient: DEBUG: Stomp connection established 16:32:01 vds.MultiProtocolAcceptor: DEBUG: Stopping Acceptor 16:32:01 jsonrpc.JsonRpcServer: INFO: Stopping JsonRPC Server 16:32:01 Executor: DEBUG: Stopping executor 16:32:01 Executor: DEBUG: Worker stopped 16:32:01 Executor: DEBUG: Worker stopped 16:32:01 Executor: DEBUG: Worker stopped 16:32:01 Executor: DEBUG: Worker stopped 16:32:01 Executor: DEBUG: Worker stopped 16:32:01 Executor: DEBUG: Worker stopped 16:32:01 Executor: DEBUG: Worker stopped 16:32:01 Executor: DEBUG: Worker stopped 16:32:01 Executor: DEBUG: Waiting for worker jsonrpc.Executor/5 16:32:01 Executor: DEBUG: Waiting for worker jsonrpc.Executor/6 16:32:01 Executor: DEBUG: Waiting for worker jsonrpc.Executor/4 16:32:01 Executor: DEBUG: Waiting for worker jsonrpc.Executor/0 16:32:01 Executor: DEBUG: Waiting for worker jsonrpc.Executor/2 16:32:01 Executor: DEBUG: Waiting for worker jsonrpc.Executor/1 16:32:01 Executor: DEBUG: Waiting for worker jsonrpc.Executor/7 16:32:01 Executor: DEBUG: Waiting for worker jsonrpc.Executor/3 16:32:01 FakeClientIf: INFO: Stopping XMLRPC server 16:32:01 FakeClientIf: INFO: XMLRPC server stopped 16:32:01 Scheduler: DEBUG: Stopping scheduler test.Scheduler 16:32:01 Scheduler: DEBUG: stopped 16:32:01 --------------------- >> end captured logging << ---------------------

4 4

Pull request for gluster self-heal monitoring feature page https://github.com/oVirt/ovirt-site/pull/214
by Ramesh Nachimuthu 29 Apr '16

29 Apr '16

Hi, I have a pull request for "Gluster Slef Heal Monitoring" feature page. Can someone help me with the review?. Regards, Rames

2 1

A question about vdsm
by zhukaijie 28 Apr '16

28 Apr '16

[vm_id].recovery file is generated which /var/run/vdsm/, which contains some VM config info that I want to prevent from other users. So are there any configurations or ways I can use to disable generation of the file? thank you.

3 2

[ACTION REQUIRED][ATTENTION NEEDED] move gluster repo to CentOS Storage SIG
by Sandro Bonazzola 28 Apr '16

28 Apr '16

Hi, this week we faced an outage on download.gluster.org server which broke our CI and caused users to be unable to install oVirt on centOS during the outage due to missing gluster packages. We've been advised by gluster community to use CentOS Storage SIG gluster rpms instead of community ones. I've started moving our release rpm to point to it starting from master ( https://gerrit.ovirt.org/56751 ) and I'll slowly go over our projects. In the meanwhile, if you've standard-ci based automation and you require gluster repositories, please move to CentOS Storage SIG as well. Repository is at http://mirror.centos.org/centos/$releasever/storage/$basearch/gluster-3.7/ <http://mirror.centos.org/centos/$releasever/storage/$basearch/gluster-3.7/> Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Attention needed] GlusterFS repository down - affects CI / Installations
by Nadav Goldin 27 Apr '16

27 Apr '16

Hi, The GlusterFS repository became unavailable this morning, as a result all Jenkins jobs that use the repository will fail, the common error would be: > > http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-7/n…: > [Errno 14] HTTP Error 403 - Forbidden > Also, installations of oVirt will fail. We are working on a solution and will update asap. Nadav.

5 5

[ATN] Activation of old Gerrit patches on ALL oVirt projects
by Eyal Edri 27 Apr '16

27 Apr '16

FYI, Following the successful runs on the old patch jenkins job on a few projects (mostly engine + vdsm) we are enabling the script to run on ALL projects hosted on gerrit.ovirt.org. As a starting point, as we did for ovirt-engine & vdsm, the limits were raised back to : [1] WARN: 90 Days ABANDON: 360 Days. If you have old patches that were untouched for the above dates, you should expect an email asking you to abandon or update the patch. Since there might be a lot of projects alerting, we've also added the project name to the email subject to make it easier to differ between projects. The script will be activated next week on Sunday. I would like to thank Vishnu to wrote this script and added the new functionally in a very short time! [1] And will continue to be lowered periodically towards a reasonable limit of a 30-60 days. Eyal E. oVirt infra.

1 0

[ANN] oVirt Node Next Beta
by Fabian Deutsch 27 Apr '16

27 Apr '16

Hey, the just released oVirt 3.6.6rc1 release marks the first official oVirt release which is accompanied by oVirt Node Next (Beta). Since it's pre-alpha release a few weeks ago, Node has seen a lot of testing and fixes, which brought it to the beta level. If you have not yet started to test oVirt Node Next, this is the time to do so. Take a look at the quick-start guide to see the next steps [0]. What is oVirt Node? oVirt Node is a ready-to-use OS image, containing all the OS and oVirt packages needed to act as host for oVirt Engine. The image can be installed in minutes, can be administered using Cockpit [1], and provides a safe upgrade and rollback mechanism. Where can I learn more about oVirt Node? A quick-start guide, and links to additional documentation can be found on the oVirt Node Project page <http://www.ovirt.org/node/>. On behalf of the Node team - fabian -- [0] http://www.ovirt.org/node/ [1] http://cockpit-project.org/

1 0

[ANN] oVirt 3.6.6 First Release Candidate is now available for testing
by Sandro Bonazzola 27 Apr '16

27 Apr '16

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 3.6.6 for testing, as of April 27th, 2016 This release is available now for: * Fedora 22 * Red Hat Enterprise Linux 6.7 * CentOS Linux 6.7 (or similar) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 22 This release candidate includes the following updated packages: * ovirt-engine * ovirt-engine-extension-aaa-jdbc * ovirt-engine-extension-aaa-ldap * ovirt-engine-dwh-3.6.6 (git hash 33f6636) * ovirt-hosted-engine-setup-1.3.6.0 * ovirt-vmconsole v1.0.2 * vdsm v4.17.27 See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO is already available [2]. * A new oVirt Node Next Install ISO is already available[3] * Mirrors[4] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 3.6.6 release highlights: http://www.ovirt.org/release/3.6.6/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/3.6.6/ [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-live/ [3] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-node-ng-installer/ [4] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[ANN] oVirt 3.6.5 Final Release is now available
by Sandro Bonazzola 26 Apr '16

26 Apr '16

The oVirt Project is pleased to announce today the general availability of oVirt 3.6.5. This latest community release includes new features and bug fixes for - oVirt Engine - VDSM - oVirt Hosted Engine HA - oVirt Hosted Engine Setup - oVirt Reports - oVirt Engine SDK - oVirt Engine Extension AAA LDAP oVirt is an open-source, openly-governed enterprise virtualization management application, developed by a global community. You can use the oVirt management interface (oVirt Engine) to manage hardware nodes, storage and network resources, and to deploy and monitor virtual machines running in your data center. If you are familiar with VMware products, oVirt is conceptually similar to vSphere. oVirt serves as the bedrock for Red Hat's Enterprise Virtualization product, and it is the "upstream" project where new features are developed prior to their inclusion in Red Hat's supported product offering. Additional Resources: * Read more about the oVirt 3.6.5 release highlights: http://www.ovirt.org/release/3.6.5/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ Note: ovirt.org website is suffering update issues so it may take a while before it receives 3.6.5 updates. ( https://github.com/oVirt/ovirt-site/issues/193 ) -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

Fwd: vdsm-jsonrpc-java_{master, 3.6}_build-artifacts-fc23 Failure
by Piotr Kliczewski 26 Apr '16

26 Apr '16

---------- Forwarded message ---------- From: Yaniv Kaul <ykaul(a)redhat.com> Date: Mon, Apr 25, 2016 at 8:56 PM Subject: Re: vdsm-jsonrpc-java_{master,3.6}_build-artifacts-fc23 Failure To: Piotr Kliczewski <pkliczew(a)redhat.com> Cc: Eyal Edri <eedri(a)redhat.com>, infra <infra(a)ovirt.org> Since this Java update solves several CVEs, I don't see how we can roll back. Y. On Mon, Apr 25, 2016 at 9:43 PM, Piotr Kliczewski <pkliczew(a)redhat.com> wrote: > > I pushed [1] patch to keep specific version of java but I see jenkins complaining about it: > > Package matching 1:java-1.8.0-openjdk-devel-1.8.0.60-14.b27.fc23.x86_64 already installed. Checking for update. > > and later: > > 18:39:15 error: Failed build dependencies: > 18:39:15 java-1.8.0-openjdk-devel = 1:1.8.0.60 is needed by vdsm-jsonrpc-java-1.2.2-master.fc23.noarch > > > > [1] https://gerrit.ovirt.org/#/c/56583 > > On Mon, Apr 25, 2016 at 8:15 PM, Piotr Kliczewski <pkliczew(a)redhat.com> wrote: >> >> I downgraded to java-1.8.0-openjdk-1.8.0.60-14.b27 and it works again. >> >> We need to make sure that we update you spec files. >> >> On Mon, Apr 25, 2016 at 7:46 PM, Piotr Kliczewski <pkliczew(a)redhat.com> wrote: >>> >>> I looks like it was already reported [1]. >>> >>> >>> [1] https://bugzilla.redhat.com/1329342 >>> >>> On Mon, Apr 25, 2016 at 7:42 PM, Piotr Kliczewski <pkliczew(a)redhat.com> wrote: >>>> >>>> It is interesting to see that ssl communication stopped working on CI only for f23. >>>> >>>> I have tested it for some time and was not able to reproduce the issue. >>>> >>>> After a while I noticed that there are some updates including java. >>>> >>>> In between my tests I updated my system (f23) and first attempt reproduced the issue. >>>> >>>> One of the packages being updated: >>>> >>>> java-1.8.0-openjdk.x86_64 1:1.8.0.91-1.b14.fc23 >>>> >>>> Investigating what changes were introduced in this version. >>>> >>>> As workaround we can downgrade java before I will find a fix. >>>> >>>> Thanks, >>>> Piotr >>>> >>>> On Mon, Apr 25, 2016 at 3:03 PM, Nadav Goldin <ngoldin(a)redhat.com> wrote: >>>>> >>>>> Hey Piotr and Oved, >>>>> Can you have a look at: >>>>> http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_master_build-artifacts-fc23-… >>>>> http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_3.6_build-artifacts-fc23-x86… >>>>> >>>>>> >> 07:02:35 Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 560.634 sec <<< FAILURE! - in org.ovirt.vdsm.jsonrpc.client.reactors.stomp.SSLStompClientTestCase >>>>>> >> 07:02:35 testLongMessage(org.ovirt.vdsm.jsonrpc.client.reactors.stomp.SSLStompClientTestCase) Time elapsed: 180.56 sec <<< ERROR! >>>>>> >> 07:02:35 org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection timeout >>>>> >>>>> >>>>> to ensure this isn't related to the Jenkins migration I re-triggered it on the old instance with the same results(http://jenkins-old.ovirt.org/job/vdsm-jsonrpc-java_master_build-art… >>>>> >>>>> Thanks, >>>>> >>>>> Nadav. >>>>> >>>> >>> >> > _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

1 0

Get Active status of Storagedomain from API
by Bryan Hughes 25 Apr '16

25 Apr '16

--_000_6C187156641F437BA138C4528DAD774Cexetergovcom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SXMgdGhlcmUgYSB3YXkgdG8gZ2V0IHRoZSBzdGF0dXMgb24gd2hldGhlciBhIHN0b3JhZ2UgZG9t YWluIGlzIGFjdGl2ZSBvciBub3QgZnJvbSB0aGUgT3ZpcnQgQVBJPyAgSSBzZWUgdGhlIGV4dGVy bmFsX3N0YXR1cy5zdGF0ZSB2YXJpYWJsZSBidXQgdGhhdCBkb2VzIG5vdCBzZWVtIHRvIHRpZSB0 byB0aGUgYWN0aXZlIHN0YXR1cyBvZiB0aGUgZG9tYWluPw0KDQpUaGFua3MsDQpCcnlhbg0K --_000_6C187156641F437BA138C4528DAD774Cexetergovcom_ Content-Type: text/html; charset="utf-8" Content-ID: <3CD6E0D9A64EAD49AD6495FA374E8DF8(a)namprd06.prod.outlook.com> Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj4NCjxkaXY+DQo8 ZGl2PklzIHRoZXJlIGEgd2F5IHRvIGdldCB0aGUgc3RhdHVzIG9uIHdoZXRoZXIgYSBzdG9yYWdl IGRvbWFpbiBpcyBhY3RpdmUgb3Igbm90IGZyb20gdGhlIE92aXJ0IEFQST8gJm5ic3A7SSBzZWUg dGhlIGV4dGVybmFsX3N0YXR1cy5zdGF0ZSB2YXJpYWJsZSBidXQgdGhhdCBkb2VzIG5vdCBzZWVt IHRvIHRpZSB0byB0aGUgYWN0aXZlIHN0YXR1cyBvZiB0aGUgZG9tYWluPzwvZGl2Pg0KPGRpdj48 YnI+DQo8L2Rpdj4NCjxkaXY+VGhhbmtzLDwvZGl2Pg0KPGRpdj5CcnlhbjwvZGl2Pg0KPGRpdj4N CjxkaXYgaWQ9Ik1BQ19PVVRMT09LX1NJR05BVFVSRSI+PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K PC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo= --_000_6C187156641F437BA138C4528DAD774Cexetergovcom_--

1 0

oVirt 3.6.6 RC1 merge / tag / bugzilla reminder
by Rafael Martins 25 Apr '16

25 Apr '16

All stable branch maintainers, please make sure to merge all relevant open bugs until Tuesday morning 11:00 AM TLV time. https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.… Every package build (i.e oVirt product) - please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag: ovirt-engine-3.6.6, tr: 3.6.6) Thanks, Rafael Martins

1 0

oVirt 3.6.6 RC1 build planned
by Rafael Martins 25 Apr '16

25 Apr '16

Fyi oVirt developers, An oVirt build is planned for this Tuesday 11:00 AM TLV time (10:00 AM CET). Taking into consideration the time it takes for Jenkins to run a full CI everything need to be backported by monday 11PM. Please make sure to mark as verified and CR +2 so it will be ready for merging tuesday morning. https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.… Thanks Rafael Martins

1 0

show only direct permissions of VM?
by Tomas Jelinek 25 Apr '16

25 Apr '16

Hi all, if you go in webadmin into the permissions subtab, it will show you only the permissions directly added to the VM, not the inherited once. This is not the case for any other entity like template where also the inherited permissions are shown. At first it looks like a bug, but the code is very explicit about it and looks like this in PermissionListModel: boolean directOnly = objType == VdcObjectType.VM ? true : false; And this code is there since the introduction of the engine. Any chance there is someone out there who remembers why? Can this be dropped and just show the inherited permissions also for VMs? Or is there a deep meaning behind it? Thanx, Tomas

1 0

User authentication on http://jenkins.ovirt.org
by Nadav Goldin 25 Apr '16

25 Apr '16

Hi all, I note again that personal user accounts were not migrated to the new Jenkins instance, so if you need other than read-only access please enrol again(press sign up in the welcome page). If you require permissions to trigger jobs manually: email infra-support(a)ovirt.org 'please put my Jenkins $username, in dev role group' for other permissions(create job, etc) - if it is a 'testing' job feel free to use http://jenkins-old.ovirt.org, as we are trying to minimize the number of none-yamlized jobs in the new instance. If that is not suitable please email what you need. Thanks, Nadav.

1 0

Jenkins.ovirt.org Upgrade | 24/04/2016(Sunday) - 18:00 TLV
by Nadav Goldin 24 Apr '16

24 Apr '16

Hey all, On Sunday, 24.04.2015 - 18:00 TLV (17:00 CET) we plan to migrate Jenkins( http://jenkins.ovirt.org) to a new VM in the PHX datacenter, this will increase the instance storage and allow better connectivity with the slaves. 1. The expected downtime is 2 hours, during that time no patches will be checked and you could not login to Jenkins. Patches sent to gerrit during the downtime, might get checked after the downtime. 2.What will be migrated: All yamlized jobs, global configuration and most of the existing slaves. 3. The old Jenkins instance will still be available under jenkins-old.ovirt.org, with a minimum number of slaves. It will be kept at least in the following months for backup and for the none-yamlized jobs(but with no gerrit triggers) 4. User authentication: all users will have to enrol again, this can be done already this week via http://jenkins.phx.ovirt.org Another reminder will be sent ~ 2 hours before the migration. Thanks, Nadav.

1 1

Weekly bug status for ovirt-system-tests (using Lago) [ 24/04/16 ]
by Eyal Edri 24 Apr '16

24 Apr '16

FYI, Some updates from recent activity on ovirt-system-tests running on Lago. *Open bugs:* https://goo.gl/eUaPUY *Open issues:* Still suffering from host add failures (stuck in installing, David has been debugging it constantly with Piotr last week) *Open patches:* (reviews are welcome) https://gerrit.ovirt.org/#/q/project:ovirt-system-tests+status:open *Jenkins jobs: (failing on known issues)* http://jenkins.ovirt.org/view/oVirt%20system%20tests/ *Recently merged patches:* (Thanks again to Yaniv K!) Author: Yaniv Kaul <ykaul(a)redhat.com> Date: Wed Apr 20 23:51:55 2016 +0300 More accurate 3.6 repo 1. With this repo, both engine and hosts can be installed, without any external access, I hope. 2. Now we can test latest 3.6, not the released one. Change-Id: I9066af4f5d92e275586c29c65fe7ef7500fe5c20 Signed-off-by: Yaniv Kaul <ykaul(a)redhat.com> -------------------------------------------------------------------------------------------------------------------- Author: Yaniv Kaul <ykaul(a)redhat.com> Date: Tue Apr 12 23:00:16 2016 +0300 Fixes for FC23 local repo setup: 1. The interface may not be eth0. The new code hopefully work with any if name. Depends that the interface is the first, but let's hope it is. 2. Add 'cost=1' to ensure the local repo is preferred over other repos. Change-Id: If846d7bacdf517d1342464c210359e5a0e8cad6e Signed-off-by: Yaniv Kaul <ykaul(a)redhat.com> -------------------------------------------------------------------------------------------------------------------- Author: Yaniv Kaul <ykaul(a)redhat.com> Date: Wed Mar 30 22:46:39 2016 +0300 Basic quota tests Add quota and set it to audit mode, not more than that. Change-Id: Ia35e9b2b65c01cdcca8da7f87ed7a38f8dc2bb17 Signed-off-by: Yaniv Kaul <ykaul(a)redhat.com> -------------------------------------------------------------------------------------------------------------------- Author: Yaniv Kaul <ykaul(a)redhat.com> Date: Thu Apr 14 01:04:28 2016 +0300 Fix mount / path issues with storage_nfs_el7 provisioning script Clearly was not tested well (because of the host installation, but that's an execuse). This patch fixes it, tested on 3.6 with adding all domains, finally. It also again simplifies it - but removes the option of not mounting the export mount. Note that the ISO mount is not completely done as well, I think. Will attend to in a follow up patch. Based on David's request, the whole setup is split into functions. Tested (properly) with 3.6, including the TEMPLATES domain attachment. (The test for it should still be excluded, IMHO). Change-Id: I261f3d3f3b3647cbbc506913478ffc6c36594519 Signed-off-by: Yaniv Kaul <ykaul(a)redhat.com> -------------------------------------------------------------------------------------------------------------------- Author: Yaniv Kaul <ykaul(a)redhat.com> Date: Sun Apr 10 17:10:16 2016 +0300 Simplification and enhancements to iSCSI and NFS servers deployment Removed a lot of not needed code from the setup. Mainly, just straightforward using the disks (in case of NFS), no need for LVM stuff. Disabled firewall, enabled 'noop' scheduler. Tested with both master and 3.6. Never got to test fully master, blocked by a host installation bug. 3.6 passed well. Change-Id: I7ec630ba5fa62529421b8e8f9aec993e7cdc84b6 Signed-off-by: Yaniv Kaul <ykaul(a)redhat.com> Please comment / update on any additional info you have on this thread, Eyal.

1 0

[ATTENTION NEEDED] Jenkins upgrade | Today(24/04/2016) - 18:00 TLV
by Nadav Goldin 24 Apr '16

24 Apr '16

Hey all, Reminder: http://jenkins.ovirt.org will be down today between 18:00-20:00 TLV(17:00-19:00 CET), details below. Thanks, Nadav. ---------- Forwarded message ---------- From: Nadav Goldin <ngoldin(a)redhat.com> Date: Thu, Apr 21, 2016 at 10:59 AM Subject: [ovirt-devel] Jenkins.ovirt.org Upgrade | 24/04/2016(Sunday) - 18:00 TLV To: devel <devel(a)ovirt.org>, infra <infra(a)ovirt.org> Hey all, On Sunday, 24.04.2015 - 18:00 TLV (17:00 CET) we plan to migrate Jenkins( http://jenkins.ovirt.org) to a new VM in the PHX datacenter, this will increase the instance storage and allow better connectivity with the slaves. 1. The expected downtime is 2 hours, during that time no patches will be checked and you could not login to Jenkins. Patches sent to gerrit during the downtime, might get checked after the downtime. 2.What will be migrated: All yamlized jobs, global configuration and most of the existing slaves. 3. The old Jenkins instance will still be available under jenkins-old.ovirt.org, with a minimum number of slaves. It will be kept at least in the following months for backup and for the none-yamlized jobs(but with no gerrit triggers) 4. User authentication: all users will have to enrol again, this can be done already this week via http://jenkins.phx.ovirt.org Another reminder will be sent ~ 2 hours before the migration. Thanks, Nadav.

1 0

UI plugins - access to engine styles and libraries
by Martin Sivak 21 Apr '16

21 Apr '16

Hi everybody, there is one piece I always missed when developing my optimizer plugin and that is the access to the engine css styles. I feel it might be pretty easy and good for both bandwidth and branding to expose them using some "well known" url from the engine. All plugins would be then able to (re-)use the same styling information and basic javascript libraries (jQuery, angular, whatever you decide the core engine will use). So far, each UI plugin has to link to its own version of libraries and define (and maintain) custom color theme. Do you think this would be doable for 4.0? Best regards -- Martin Sivak SLA / oVirt

3 10