- Devel - oVirt List Archives

Failed to add CentOS 7 host
by Fedor Gavrilov 13 Aug '19

13 Aug '19

Hi, Couple of days ago I had to refresh my dev environment to validate the issue and since support for Fedora 28 is no longer there I used CentOS 7 for both engine and host. Vdsm and cockpit socket on host is from the package, engine is compiled from git master. As I try to add new host, installment proceeds for quite a while but fails in the end, setting host to non operational. I see the following in the engine logs: 2019-08-12 17:32:40,341+02 INFO [org.ovirt.engine.core.bll.host.HostConnectivityChecker] (EE-ManagedThreadFactory-engine-Thread-20) [9f80a7] Engine managed to communicate with VDSM agent on host 'banana' with address 'banana' ('bcabbd09-81ef-422d-811c-3a18ac97919f') 2019-08-12 17:32:42,163+02 WARN [org.ovirt.engine.core.bll.network.NetworkConfigurator] (EE-ManagedThreadFactory-engine-Thread-20) [9f80a7] Failed to find a valid interface for the management network of host banana. If the interface null is a bridge, it should be torn-down manually. 2019-08-12 17:32:42,166+02 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-20) [9f80a7] Exception: org.ovirt.engine.core.bll.network.NetworkConfigurator$NetworkConfiguratorException: Interface null is invalid for management network at org.ovirt.engine.core.bll.network.NetworkConfigurator.findNicToSetupManagementNetwork(NetworkConfigurator.java:159) [bll.jar:] at org.ovirt.engine.core.bll.network.NetworkConfigurator.createManagementNetworkIfRequired(NetworkConfigurator.java:82) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand.configureManagementNetwork(InstallVdsInternalCommand.java:291) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand.installHost(InstallVdsInternalCommand.java:203) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand.executeCommand(InstallVdsInternalCommand.java:112) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1168) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1326) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2005) [bll.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:164) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:103) [utils.jar:] at org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1386) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:420) [bll.jar:] at org.ovirt.engine.core.bll.executor.DefaultBackendActionExecutor.execute(DefaultBackendActionExecutor.java:13) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runAction(Backend.java:451) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:433) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:639) [bll.jar:] at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source) [:1.8.0_222] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_222] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_222] at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:79) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:89) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:102) at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:216) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:418) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:148) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) [weld-ejb-3.1.1.Final.jar:3.1.1.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:618) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81) at org.ovirt.engine.core.bll.interfaces.BackendInternal$$$view3.runInternalAction(Unknown Source) [bll.jar:] at sun.reflect.GeneratedMethodAccessor111.invoke(Unknown Source) [:1.8.0_222] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_222] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_222] at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:410) [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] at org.jboss.weld.module.ejb.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:134) [weld-ejb-3.1.1.Final.jar:3.1.1.Final] at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] at org.jboss.weld.module.ejb.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:68) [weld-ejb-3.1.1.Final.jar:3.1.1.Final] at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106) [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] at org.ovirt.engine.core.bll.BackendCommandObjectsHandler$BackendInternal$BackendLocal$2049259618$Proxy$_$$_Weld$EnterpriseProxy$.runInternalAction(Unknown Source) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInternalAction(CommandBase.java:2395) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand.lambda$executeCommand$3(AddVdsCommand.java:226) [bll.jar:] at org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil$InternalWrapperRunnable.run(ThreadPoolUtil.java:96) [utils.jar:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_222] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_222] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_222] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_222] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_222] at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) [javax.enterprise.concurrent-1.0.jar:] 2019-08-12 17:32:42,188+02 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-20) [9f80a7] Host installation failed for host 'bcabbd09-81ef-422d-811c-3a18ac97919f', 'banana': Failed to configure management network on the host ... 2019-08-12 17:35:01,502+02 ERROR [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-85) [3c4801f1] Host 'banana' is set to Non-Operational, it is missing the following networks: 'ovirtmgmt' On host, sudo systemctl status vdsmd shows vdsm as active (running) with two concerning messages: авг 12 17:30:01 banana vdsm[2309]: WARN MOM not available. авг 12 17:30:01 banana vdsm[2309]: WARN MOM not available, KSM stats will be missing. I found a similar bug, https://bugzilla.redhat.com/show_bug.cgi?id=1676695 but it was fixed for 4.30 while on host I use 4.40.0-696 Have you seen such issue? Do you think networking error is related to MOM warnings? Setup I use is very much what worked perfectly fine for fedora and networking-vise the only questionable thing I am doing is having this kind of records in machine's /etc/hosts files to use names instead IPs (as imageio can't stand certificates with IPs): 192.168.111.2 apple 192.168.111.3 banana But this can't be the reason, right? Fedor

2 2

vdsm has been tagged (v4.30.27)
by Milan Zamazal 13 Aug '19

13 Aug '19

1 0

No response for post using curl for The Backup and Restore API oVirt API
by smidhunraj＠gmail.com 13 Aug '19

13 Aug '19

I have 2 virtual machines in my ovirt open virtualisation manager.The name of first virtual machine is backupvm and the name of second virtual machine is secondvm .I have created many snapshot shot of secondvm I want to convert a particular snapshot ofsecondvm using the ovirt api to secondvm backup and attach it to backupvm The link of the api is https://ovirt.org/documentation/admin-guide/chap-Backups_and_Migration.html… .I want to run the fourth step which says. Attach the snapshot to the backup virtual machine and activate the disk: POST /api/vms/22222222-2222-2222-2222-222222222222/disks/ HTTP/1.1 Accept: application/xml Content-type: application/xml <disk id="11111111-1111-1111-1111-111111111111"> <snapshot id="11111111-1111-1111-1111-111111111111"/> <active>true</active> </disk> .I want to attach this snapshots after converting them to backups of vms and then attach to vm named backupvm.The api for this is mentioned as The id of secondvm is a88a79ab-1f0c-4f32-bdaa-abc8109b3c0d and the id of backupvm is a88a79ab-1f0c-4f32-bdaa-abc8109b3c0d.The id of snapshot is 804cb937-5961-4a55-a453-74932c508dd6 and id of disk is e6c623e3-31d8-4554-ad5a-2b581914494b I have written a curl command for this as curl -u 'username:password' -H "Accept: application/xml" -H "Content-type: application/xml" -X POST -d '<disk id="e6c623e3-31d8-4554-ad5a-2b581914494b"> <snapshot id="804cb937-5961-4a55-a453-74932c508dd6"/> <active>true</active> </disk>' https:<url>/ovirt-engine/api/vms/a88a79ab-1f0c-4f32-bdaa-abc8109b3c0d/disks/ ; I expect the vm snapshot to be attached to backupvm.But i am not getting any response .Hence i am under the assumption that it is not working.. What modification should i make in the curl command to get it working In the figure below secondvm is labelled as bobcarenewvm https://i.stack.imgur.com/LC3An.png https://i.stack.imgur.com/Lgozu.png https://i.stack.imgur.com/efQrf.png https://i.stack.imgur.com/3wAyA.png Please help me, Thanks and Regards, Midhun.

3 3

[OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import]
by Dusan Fodor 12 Aug '19

12 Aug '19

Hi, we have failures in test verify glance import appearing in both 4.3 and master. Api call to get the disk status times out. Example of failed job can be seen here: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… Can you please take a look?

3 3

Setting Start Running On Specific host radio button via the SDK
by donagh.moran＠oracle.com 12 Aug '19

12 Aug '19

Hi I'm looking to target the radio button for Specific host, Does anyone have info on what SDK object controls this feature? Even better if anyone can point me towards some documentation that maps oVirt UI functionality to the SDK endpoints? Best Regards Donagh

2 2

ovirt-host-deploy modifies the vdsm.conf
by Ales Musil 12 Aug '19

12 Aug '19

Hi, I have tried: /etc/ovirt-host-deploy.conf.d/50-development.conf [environment:enforce] VDSM/configOverride=bool:False But the vdsm config is still being modified by the host deploy any idea what is wrong with this configuration? Thank you. Regards, Ales -- Ales Musil Associate Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

1 1

Setting Migration Mode via SDK
by donagh.moran＠oracle.com 12 Aug '19

12 Aug '19

Hi In the VM Host settings, I need to set Migration mode ( Migration Options ) to "Do not allow migration" from the SDK but I do not see any functionality that would allow me to preform this task. Is there any method available that would let me achieve this from my Java code? Any help would be much appreciated. Best Regards Don

2 2

No response for post using curl for The Backup and Restore API oVirt API
by smidhunraj＠gmail.com 12 Aug '19

12 Aug '19

I have 2 virtual machines in my ovirt open virtualisation manager.The name of first virtual machine is backupvm and the name of second virtual machine is secondvm .I have created many snapshot shot of secondvm I want to convert a particular snapshot ofsecondvm using the ovirt api to secondvm backup and attach it to backupvm The link of the api is https://ovirt.org/documentation/admin-guide/chap-Backups_and_Migration.html… .I want to run the fourth step which says. Attach the snapshot to the backup virtual machine and activate the disk: POST /api/vms/22222222-2222-2222-2222-222222222222/disks/ HTTP/1.1 Accept: application/xml Content-type: application/xml <disk id="11111111-1111-1111-1111-111111111111"> <snapshot id="11111111-1111-1111-1111-111111111111"/> <active>true</active> </disk> .I want to attach this snapshots after converting them to backups of vms and then attach to vm named backupvm.The api for this is mentioned as The id of secondvm is a88a79ab-1f0c-4f32-bdaa-abc8109b3c0d and the id of backupvm is a88a79ab-1f0c-4f32-bdaa-abc8109b3c0d.The id of snapshot is 804cb937-5961-4a55-a453-74932c508dd6 and id of disk is e6c623e3-31d8-4554-ad5a-2b581914494b I have written a curl command for this as curl -u 'username:password' -H "Accept: application/xml" -H "Content-type: application/xml" -X POST -d '<disk id="e6c623e3-31d8-4554-ad5a-2b581914494b"> <snapshot id="804cb937-5961-4a55-a453-74932c508dd6"/> <active>true</active> </disk>' https:<url>/ovirt-engine/api/vms/a88a79ab-1f0c-4f32-bdaa-abc8109b3c0d/disks/ ; I expect the vm snapshot to be attached to backupvm.But i am not getting any response .Hence i am under the assumption that it is not working.. What modification should i make in the curl command to get it working In the figure below secondvm is labelled as bobcarenewvm https://i.stack.imgur.com/LC3An.png https://i.stack.imgur.com/Lgozu.png https://i.stack.imgur.com/efQrf.png https://i.stack.imgur.com/3wAyA.png Please help me, Thanks and Regards, Midhun.

1 0

[Ovirt] [CQ weekly status] [10-08-2019]
by Dusan Fodor 11 Aug '19

11 Aug '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#3) No failure during this week. *CQ-4.3*: RED (#1) Last failure was on 10-08 for ovirt-ansible-image-template in verify_glance_import. This issue is ongoing, investigation will continue under thread [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import] *CQ-Master:* RED (#1) Last failure was on 10-08 for ovirt-ansible-image-template in verify_glance_import. This issue is ongoing, investigation will continue under thread [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import] Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.2_change-queue-tester/ [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.3_change-queue-tester/ [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -master_change-queue-tester/ Have a nice week! Dusan ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3) _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt .org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt .org/message/YCNCKRK3G4EJXA3OCYAUS4VMKRDA67F4/

2 1

CI: vdsm-standard-check-patch fails
by Amit Bawer 09 Aug '19

09 Aug '19

Hi, CI seems to fail constantly for unavailable remote gerrit repository. Example can be seen here: https://jenkins.ovirt.org/job/vdsm_standard-check-patch/9415/console

6 20