- Devel - oVirt List Archives

[VDSM] All tests passed, but CI failed to archive the artifacts (No space left on device)
by Nir Soffer 03 Jul '18

03 Jul '18

Can we improve the CI so the build will succeed once check-patch completed successfully, regardless of errors after that point? All tests suceeded *13:41:18* tests: commands succeeded*13:41:18* storage-py27: commands succeeded*13:41:18* storage-py36: commands succeeded*13:41:18* lib-py27: commands succeeded*13:41:18* lib-py36: commands succeeded*13:41:18* network-py27: commands succeeded*13:41:18* network-py36: commands succeeded*13:41:18* virt-py27: commands succeeded*13:41:18* virt-py36: commands succeeded*13:41:18* congratulations :) But the build failed: https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/229/ Because of: *13:42:33* POST BUILD TASK : SUCCESS*13:42:33* END OF POST BUILD TASK : 2*13:42:33* Archiving artifacts*13:42:35* ERROR: Step ‘Archive the artifacts’ aborted due to exception: *13:42:35* java.io.IOException: No space left on device*13:42:35* at sun.nio.ch.FileDispatcherImpl.write0(Native Method)*13:42:35* at sun.nio.ch.FileDispatcherImpl.write(FileDispatcherImpl.java:60)*13:42:35* at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)*13:42:35* at sun.nio.ch.IOUtil.write(IOUtil.java:65)*13:42:35* at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:211)*13:42:35* at java.nio.channels.Channels.writeFullyImpl(Channels.java:78)*13:42:35* at java.nio.channels.Channels.writeFully(Channels.java:101)*13:42:35* at java.nio.channels.Channels.access$000(Channels.java:61)*13:42:35* at java.nio.channels.Channels$1.write(Channels.java:174)*13:42:35* at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1793)*13:42:35* at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769)*13:42:35* at org.apache.commons.io.IOUtils.copy(IOUtils.java:1744)*13:42:35* at hudson.util.IOUtils.copy(IOUtils.java:43)*13:42:35* at hudson.FilePath.readFromTar(FilePath.java:2465)*13:42:35* Also: Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to vm0064.workers-phx.ovirt.org*13:42:35* at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)*13:42:35* at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)*13:42:35* at hudson.remoting.Channel$2.adapt(Channel.java:990)*13:42:35* at hudson.remoting.Channel$2.adapt(Channel.java:986)*13:42:35* at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)*13:42:35* at hudson.FilePath.copyRecursiveTo(FilePath.java:2368)*13:42:35* at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61)*13:42:35* at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:235)*13:42:35* at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)*13:42:35* at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)*13:42:35* at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)*13:42:35* at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)*13:42:35* at hudson.model.Build$BuildExecution.post2(Build.java:186)*13:42:35* at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)*13:42:35* at hudson.model.Run.execute(Run.java:1819)*13:42:35* at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) See https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/229/conso… Nir

2 1

Recent he-basic-ansible-suite-4.2 failures
by Yedidyah Bar David 02 Jul '18

02 Jul '18

Hi all, I noticed that our hosted-engine suites [1] often fail recently, and decided to have a look at [2], which are on 4.2, which should hopefully be "rock solid" and basically never fail. I looked at these, [3][4][5][6][7], which are all the ones that still appear in [2] and marked as failed. Among them: - All but one failed while "Waiting for agent to be ready" and timing out after 10 minutes, as part of 008_restart_he_vm.py, which was added a month ago [8] and then patched [9]. - The other one [7] failed while "Waiting for engine to migrate", also eventually timing out after 10 minutes, as part of 010_local_mainentance.py, which was also added in [9]. I also had a look at the last ones that succeeded, builds 329 to 337 of [2]. There: - "Waiting for agent to be ready" took between 26 and 48 seconds - "Waiting for engine to migrate" took between 69 and 82 seconds Assuming these numbers are reasonable (which might be debatable), 10 minutes indeed sounds like a reasonable timeout, and I think we should handle each failure specifically. Did anyone check them? Was it an infra issue/load/etc.? A bug? Something else? I didn't check the logs yet, might do this later. Also didn't check the failures in other jobs in [1]. Best regards, [1] https://jenkins.ovirt.org/search/?q=he-basic [2] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/ [3] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2… [4] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2… [5] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2… [6] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2… [7] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2… [8] https://gerrit.ovirt.org/91952 [9] https://gerrit.ovirt.org/92341 -- Didi

3 3

ovirt extensions -- weekly report
by Greg Sheremeta 01 Jul '18

01 Jul '18

ovirt extensions -- weekly report A team is working on set of features to make ansible roles/playbooks runnable via the administration portal. project book: ovirt extensions project book [1] The project has 3 sub-parts, currently: migrate-vm cluster-upgrade central considerations (long-running operations, APIs, notifications) migrate-vm (note: uses REST API, not ansible backend) design document: [2] design discussion moved to github: [3] patches: [4] Status: should be merged Monday / Tuesday * Greg, Vojtech: merge and remove old migrate button cluster-upgrade design document: [5] design discussion moved to github: PR [6] Status: in design review. Please comment freely on the PR! Action items: * all - design review * Greg: code UI (haven't begun) central considerations design document: [7] design discussions on github: [8] patches: [9] Status: in coding (notifications + API) Action items: * Greg: coding notifications drawer (expect merge Monday) * Ondra: coding ansible remote API (code review discussion ongoing) [1] ovirt extensions project book - Google Docs https://docs.google.com/document/d/1n4VlosdPnIZL81wx0sEIrkAfBehuV5DfOU7eH9i… [2] Migrate VMs Modal - Google Docs https://docs.google.com/document/d/1NF46ZJSOcGFrLWx18Ujsckoob19ANfBlpisB6_f… [3] ovirt-design - Migrate Virtual Machines https://ovirt.github.io/ovirt-design/admin-ui/compute/migrate-vms [4] project:ovirt-engine-ui-extensions | gerrit.ovirt Code Review https://gerrit.ovirt.org/#/q/project:ovirt-engine-ui-extensions [5] Cluster Upgrade - Google Docs https://docs.google.com/document/d/1kRDAeu0-wIKbSNieXenQY5qevwNlyCnpyZdeUX-… [6] Adding design proposal around Upgrading a Cluster by lizsurette · Pull Request #5 · oVirt/ovirt-design https://github.com/oVirt/ovirt-design/pull/5 [7] ovirt-engine-ui-extensions - overall design considerations and notes - Google Docs https://docs.google.com/document/d/1GMurjSMtzLaZFktH_Ysge4lRIpLd0nosuV1m8IR… [8] ovirt-design/notifications.md at master · oVirt/ovirt-design https://github.com/oVirt/ovirt-design/blob/master/admin-ui/framework/notifi… [9] Change I73f35974: webadmin: notifications drawer | gerrit.ovirt Code Review https://gerrit.ovirt.org/#/c/92443/ Change Ib7198f91: services: Add /ansible service for remote execution | gerrit.ovirt Code Review https://gerrit.ovirt.org/#/c/92404/ Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

1 0

vm portal UI redesign -- weekly report
by Greg Sheremeta 01 Jul '18

01 Jul '18

vm portal UI redesign -- weekly report screens: https://github.com/oVirt/ovirt-design/pulls github issues: https://github.com/oVirt/ovirt-web-ui/issues?q=label%3Aredesign google doc for bootstrapping: [1] Status: * Scott had AI of prototype. Liz and Jenny had AIs for continuing design * last week we: - brought Moran (PM) into the project to help set direction (Weds) - had our weekly sync meeting (Thurs) where we * Demos - Bohdan showed the VM list page - Scott showed the VM view / edit page * iterated on Jenny's design updates * iterated on Liz's design updates Action items: Liz/Jenny - more designs showing different VM states Liz - refine disks, snapshots, networks Liz - start a console designs document (or use slides) and let’s iterate in there, goal of consensus before next meeting Liz - continue work on New VM Scott - continue Edit page Bohdan - Green buttons --> gray Marek + Bohdan + Scott - continue coding [1] https://docs.google.com/presentation/d/1UavAccggYAqLeXZYnVpyiE6h5tnCJJQMq_f… Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

1 0

Gerrit trying to set 3rd party cookies
by Nir Soffer 01 Jul '18

01 Jul '18

After watching Sarah Bird's great talk about the terrifying web[1], I found that for some reason 3rd party cookies were enabled in my browser. After disabling them, I found that gerrit is using 3rd party cookies from gravatar.com. (see attached screenshot). Why do we allow 3rd parties like gravatar to set cookies? Can we use gravatar without setting cookies? [image: Screenshot from 2018-07-01 15-31-37.png] [1] https://il.pycon.org/2018/schedule/presentation/18/ Nir

2 2

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 28-06-2018 ] [ 098_ovirt_provider_ovn.use_ovn_provider.]
by Dafna Ron 01 Jul '18

01 Jul '18

Hi, We had a failure in test 098_ovirt_provider_ovn.use_ovn_provider. Although CQ is pointing to this change: https://gerrit.ovirt.org/#/c/92567/ - packaging: Add python-netaddr requirement I actually think from the error its because of changes made to multiqueues https://gerrit.ovirt.org/#/c/92009/ - engine: Update libvirtVmXml to consider vmBase.multiQueuesEnabled attribute https://gerrit.ovirt.org/#/c/92008/ - engine: Introduce algorithm for calculating how many queues asign per vnic https://gerrit.ovirt.org/#/c/92007/ - engine: Add multiQueuesEnabled to VmBase https://gerrit.ovirt.org/#/c/92318/ - restapi: Add 'Multi Queues Enabled' to the relevant mappers https://gerrit.ovirt.org/#/c/92149/ - webadmin: Add 'Multi Queues Enabled' to vm dialog Alona, can you please take a look? *Link to Job:* *http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/>Link to all logs:https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/ar… <https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/artifac…>(Relevant) error snippet from the log: <error>* *eng**ine: * 2018-06-27 13:59:25,976-04 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-80) [] Command 'GetAllVmStatsVDSCommand(HostName = lago-basic-suite-master-host-1, VdsIdVDSCommandParametersBase:{hostId='d9094c95-3275-4616-b4c2-815e753bcfed'})' execution failed: VDSGenericException: VDSNetworkException: Broken pipe 2018-06-27 13:59:25,977-04 DEBUG [org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil] (EE-ManagedThreadFactory-engine-Thread-442) [] Executing task: EE-ManagedThreadFactory-engine-Thread-442 2018-06-27 13:59:25,977-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-engine-Thread-442) [] method: getVdsManager, params: [d9094c95-3275-4616-b4c2-815e753bcfed], timeElapsed: 0ms 2018-06-27 13:59:25,977-04 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedThreadFactory-engine-Thread-442) [] Host 'lago-basic-suite-master-host-1' is not responding. 2018-06-27 13:59:25,979-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM lago-basic-suite-master-host-1 command GetStatsAsyncVDS failed: Broken pipe 2018-06-27 13:59:25,976-04 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-80) [] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetworkException: Broken pipe at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.proceedProxyReturnValue(BrokerCommandBase.java:189) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand.executeVdsBrokerCommand(GetAllVmStatsVDSCommand.java:23) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65) [vdsbroker.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31) [dal.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.DefaultVdsCommandExecutor.execute(DefaultVdsCommandExecutor.java:14) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:399) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown Source) [vdsbroker.jar:] at sun.reflect.GeneratedMethodAccessor270.invoke(Unknown Source) [:1.8.0_171] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_171] at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) [common.jar:] at sun.reflect.GeneratedMethodAccessor68.invoke(Unknown Source) [:1.8.0_171] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_171] at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand(Unknown Source) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher.poll(VmsStatisticsFetcher.java:29) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.monitoring.VmsListFetcher.fetch(VmsListFetcher.java:49) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher.poll(PollVmStatsRefresher.java:44) [vdsbroker.jar:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_171] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [rt.jar:1.8.0_171] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383) [javax.enterprise.concurrent-1.0.jar:] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534) [javax.enterprise.concurrent-1.0.jar:] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171] at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) [javax.enterprise.concurrent-1.0.jar:] at org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$ElytronManagedThread.run(ElytronManagedThreadFactory.java:78) 2018-06-27 13:59:25,984-04 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-80) [] FINISH, GetAllVmStatsVDSCommand, return: , log id: 56d99e77 2018-06-27 13:59:25,984-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-engineScheduled-Thread-80) [] method: runVdsCommand, params: [GetAllVmStats, VdsIdVDSCommandParametersBase:{hostId='d9094c95-3275-4616-b4c2-815e753bcfed'}], timeElapsed: 1497ms 2018-06-27 13:59:25,984-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher] (EE-ManagedThreadFactory-engineScheduled-Thread-80) [] Failed to fetch vms info for host 'lago-basic-suite-master-host-1' - skipping VMs monitoring. *vdsm: 2018-06-27 14:10:17,314-0400 INFO (jsonrpc/7) [virt.vm] (vmId='b8a11304-07e3-4e64-af35-7421be780d5b') Hotunplug NIC xml: <?xml version='1.0' encoding='utf-8'?><interface type="bridge"> <address bus="0x00" domain="0x0000" function="0x0" slot="0x0b" type="pci" /> <mac address="00:1a:4a:16:01:0e" /> <model type="virtio" /> <source bridge="network_1" /> <link state="up" /> <driver name="vhost" queues="" /> <alias name="ua-3c77476f-f194-476a-8412-d76a9e58d1f9" /></interface> (vm:3321)2018-06-27 14:10:17,328-0400 ERROR (jsonrpc/7) [virt.vm] (vmId='b8a11304-07e3-4e64-af35-7421be780d5b') Hotunplug failed (vm:3353)Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 3343, in hotunplugNic self._dom.detachDevice(nicXml) File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 99, in f ret = attr(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 93, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1177, in detachDevice if ret == -1: raise libvirtError ('virDomainDetachDevice() failed', dom=self)libvirtError: 'queues' attribute must be positive number: 2018-06-27 14:10:17,345-0400 DEBUG (jsonrpc/7) [api] FINISH hotunplugNic response={'status': {'message': "'queues' attribute must be positive number: ", 'code': 50}} (api:136)2018-06-27 14:10:17,346-0400 INFO (jsonrpc/7) [api.virt] FINISH hotunplugNic return={'status': {'message': "'queues' attribute must be positive number: ", 'code': 50}} from=::ffff:192.168.201.4,32976, flow_id=ecb6652, vmId=b8a11304-07e3-4e64-af35-7421be780d5b (api:53)2018-06-27 14:10:17,346-0400 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call VM.hotunplugNic failed (error 50) in 0.07 seconds (__init__:311)2018-06-27 14:10:19,244-0400 DEBUG (qgapoller/2) [vds] Not sending QEMU-GA command 'guest-get-users' to vm_id='b8a11304-07e3-4e64-af35-7421be780d5b', command is not supported (qemuguestagent:192)2018-06-27 14:10:20,038-0400 DEBUG (jsonrpc/1) [jsonrpc.JsonRpcServer] Calling 'Host.getAllVmStats' in bridge with {} (__init__:328)2018-06-27 14:10:20,038-0400 INFO (jsonrpc/1) [api.host] START getAllVmStats() from=::1,48032 (api:47)2018-06-27 14:10:20,041-0400 INFO (jsonrpc/1) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::1,48032 (api:53)2018-06-27 14:10:20,043-0400 DEBUG (jsonrpc/1) [jsonrpc.JsonRpcServer] Return 'Host.getAllVmStats' in bridge with (suppressed) (__init__:355)2018-06-27 14:10:20,043-0400 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:311)2018-06-27 14:10:20,057-0400 DEBUG (jsonrpc/6) [jsonrpc.JsonRpcServer] Calling 'Host.getAllVmIoTunePolicies' in bridge with {} (__init__:328)2018-06-27 14:10:20,058-0400 INFO (jsonrpc/6) [api.host] START getAllVmIoTunePolicies() from=::1,48032 (api:47)2018-06-27 14:10:20,058-0400 INFO (jsonrpc/6) [api.host] FINISH getAllVmIoTunePolicies return={'status': {'message': 'Done', 'code': 0}, 'io_tune_policies_dict': {'b8a11304-07e3-4e64-af35-7421be780d5b': {'policy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/blockSD/cf23ceeb-81a3-4714-85a0-c6ddd1e024da/images/650fe4ae-47a1-4f2d-9cba-1617a8c868c3/03e75c3c-24e7-4e68-a6f1-21728aaaa73e', 'name': 'vda'}]}}} from=::1,48032 (api:53)2018-06-27 14:10:20,059-0400 DEBUG (jsonrpc/6) [jsonrpc.JsonRpcServer] Return 'Host.getAllVmIoTunePolicies' in bridge with {'b8a11304-07e3-4e64-af35-7421be780d5b': {'policy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/blockSD/cf23ceeb-81a3-4714-85a0-c6ddd1e024da/images/650fe4ae-47a1-4f2d-9cba-1617a8c868c3/03e75c3c-24e7-4e68-a6f1-21728aaaa73e', 'name': 'vda'}]}} (__init__:355)</error>*

3 7

oVirt HCI point-to-point interconnection
by Stefano Zappa 30 Jun '18

30 Jun '18

Good morning, I would like to kindly ask you a question about the feasibility of defining a point-to-point interconnection between three ovirt nodes. Initially with the idea of optimizing the direct communications between the nodes and especially the gluster communications, and so it would seem quite easy, then evaluating a more complex configuration, assuming to create an overlay L2 network on the three L3 point-to-point, using techniques like geneve, of which at the moment I have no mastery. If the direct routing of three nodes to interconnect the public network with the private overlay network was not easily doable, we could leave the private overlay network isolated from the outside world and connect the VM hosted engine directly to the two networks with two adapters. This layout with direct interconnection of the nodes without switches and a shared L2 overlay network between the nodes may in future be contemplated in future releases of your HCI solution? Thank you for your attention, have a nice day! Stefano Zappa. [cid:609f1f14-f74e-489f-b86d-08647efc6d1c] Stefano Zappa IT Specialist CAE - TT-3 Industrie Saleri Italo S.p.A. Phone: +39 0308250480 Fax: +39 0308250466 This message contains confidential information and is intended only for users(a)ovirt.org, infra(a)ovirt.org, devel(a)ovirt.org. If you are not users(a)ovirt.org, infra(a)ovirt.org, devel(a)ovirt.org you should not disseminate, distribute or copy this e-mail. Please notify Stefano.Zappa(a)saleri.it immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Stefano Zappa therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. PRIVACY INFORMATION ART. 13 EU REG. 2016/679 We inform you that the personal data contained in the present and subsequent electronic communications will be processed in compliance with the EU Regulation 2016/679, for the purpose of and only for the time necessary to allow the sender to carry out the activities connected to the existing commercial relationships. The provision of personal data is not mandatory. However, failure to provide them determines the impossibility of achieving the aforementioned purpose. With regard to these data, is allowed the exercise of the rights set out in art. 13 and from the articles from 15 to 22 of EU Regulation 2016/679 and in particular the right to request the access to, updating, rectification and erasure of your personal data, as well as the right to object to processing and to lodge a complaint with the Supervisory Authority, by sending an e-mail to privacy(a)saleri.it. Data Controller of your personal data is Industrie Saleri Italo S.p.a., with registered office in via Ruca, 406 - 25065 Lumezzane (BS).

5 8

oVirt on Fedora 28 for developers
by Nir Soffer 29 Jun '18

29 Jun '18

I want to share the current state of oVirt on Fedora 28, hopefully it will save time for other developers. 1. Why should I run oVirt on Fedora 28? - Fedora is the the base for future CentOS. The bugs we find *today* on Fedora 28 are the bugs that we will not have next year when we try oVirt on CentOS. - I want to contribute to projects that require python 3. For example, virt-v2v require python 3.6 in upstream. If you want to contribute you need to test it on Fedora 28. - I need to develop with latest libvirt and qemu. One example is incremental backup, you will need Fefora 28 to work on this. - CentOS is old and boring, I want to play with the newest bugs :-) 2. How to install oVirt with Fedora 28 hosts Warning: ugly hacks bellow! - Install ovirt-release-master.rpm on all hosts dnf install http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm - Install or build engine on CentOS 7.5 (1804)[1] - When provisioning a host, make sure you have lvm2-2.02.177-5.fc28 without it, no block storage you[2] - When adding a host, disable "Configure host firewall" - it does not work now I hope that Sandro team will fix this issue soon. - Adding a host will fail, because without firewall setup, port 54321 is not reacable. to fix this, configure the firewall manually, or disable it iptables -F This is pretty lame because you have to apply it again after restart, but it was good enough for now. - Because the host was not reachable, we don't configure the host network so the host will be non-operational. To fix this, open host > network > setup networks and assign ovirtmgmt to the host management nic. The host will become UP after that. I hope that Dan team will fix it soon. - Adding storage will fail because sanlock selinux issue[3] To fix, set selinux to permissive mode: setenforce 0 At this point you should have a working setup. 3. Building and instaling vdsm from source on Fedora 28 - Install build dependencies using dnf install `cat automation/check-patch.packages.fc28` - Clean the source (needed if you rerun ./autogen.sh with different options) git clean -dxf - Configure vdsm with hooks - for some reason 2 hooks are required on Fedora but not on EL. ./autogen.sh --system --enable-hooks - Build make make rpm - Install the packages at /home/user/rpmbuild/RPMS/{noarch,x86_64} - if vdsm was never installed, you need to configure and enable it vdsm-tool configure --force systemctl enable vdsmd systemctl start vdsmd At this point you can test the new bugs you added to vdsm :-) [1] I did not try to install engine on Fedora 28. I guess engine folks can share if there are issues with this. [2] https://bugzilla.redhat.com/1575762 LVM team fixed the issue couple of hours after I asked about it in #lvm We had a build for testing couple of days later. [3] https://bugzilla.redhat.com/1593853 We are still waiting for selinux folks response. Happy hacking! Nir

4 5

CVE-2018-3639 qemu-kvm-ev-2.10.0-21.el7_5.4.1 is now available for testing
by Sandro Bonazzola 28 Jun '18

28 Jun '18

Hi, qemu-kvm-ev-2.10.0-21.el7_5.4.1 has been tagged for testing. If nothing shows up, I'll tag it for release on Monday July 2nd. Here's the changelog: * Thu Jun 28 2018 Sandro Bonazzola <sbonazzo(a)redhat.com> - ev-2.10.0-21.el7_5.4.1 - Removing RH branding from package name * Sat Jun 09 2018 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.10.0-21.el7_5.4 - kvm-scsi-disk-allow-customizing-the-SCSI-version.patch [bz#1571370] - kvm-hw-scsi-support-SCSI-2-passthrough-without-PI.patch [bz#1571370] - kvm-i386-Define-the-Virt-SSBD-MSR-and-handling-of-it-CVE.patch [bz#1584370] - kvm-i386-define-the-AMD-virt-ssbd-CPUID-feature-bit-CVE-.patch [bz#1584370] - kvm-cpus-Fix-event-order-on-resume-of-stopped-guest.patch [bz#1582122] - kvm-spec-Enable-Native-Ceph-support-on-all-architectures.patch [bz#1588001] - Resolves: bz#1571370 (Pegas1.1 Alpha: SCSI pass-thru of aacraid RAID1 is inaccessible (qemu-kvm-rhev) [rhel-7.5.z]) - Resolves: bz#1582122 (IOERROR pause code lost after resuming a VM while I/O error is still present [rhel-7.5.z]) - Resolves: bz#1584370 (CVE-2018-3639 qemu-kvm-rhev: hw: cpu: AMD: speculative store bypass [rhel-7.5.z]) - Resolves: bz#1588001 (Enable Native Ceph support on non x86_64 CPUs [rhel-7.5.z]) For testing: $ sudo yum install centos-release-qemu-ev $ sudo yum-config-manager --enable centos-qemu-ev-test $ sudo yum update "qemu-kvm-ev*" and use it as usual. Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

[VDSM] Why hooks are required for installing vdsm?
by Nir Soffer 28 Jun '18

28 Jun '18

Trying to update vdsm master, my update script fail with: installing... error: Failed dependencies: vdsm = 4.30.0-429.git05bfb8731.fc28 is needed by (installed) vdsm-hook-fcoe-4.30.0-429.git05bfb8731.fc28.noarch vdsm = 4.30.0-429.git05bfb8731.fc28 is needed by (installed) vdsm-hook-ethtool-options-4.30.0-429.git05bfb8731.fc28.noarch I tried to remove these hooks, since I'm not interested in any of them, but removing them try to remove 136 packages including libvirt. Why do we have these dependencies? hook should be optional. Who owns these hooks? Nir

2 4