Created attachment 1365590 [details] in the attached engine.log see the line 22682 for example.there are more places Description of problem: Rename of VM causes "command 'org.ovirt.engine.core.bll.ProcessDownVmCommand' failed: java.lang.NullPointerException" (engine log attached) Version-Release number of selected component (if applicable): How reproducible:100% Steps to Reproduce: 1.open Edit window for the running VM , change the name, ok in the popUp window saying about restart . 2.stop VM Actual results: Command 'org.ovirt.engine.core.bll.ProcessDownVmCommand' failed: java.lang.NullPointerException 2017-12-10 14:49:14,070+02 ERROR [org.ovirt.engine.core.bll.ProcessDownVmCommand] (EE-ManagedThreadFactory-engine-Thread-2917) [1246794a] Exception: javax.ejb.EJBException: java.lang.NullPointerException at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInNoTx(CMTTxInterceptor.java:214) [wildfly-ejb3-7.1.0.GA-redhat-11.jar:7.1.0.GA-redhat-11] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:266) [wildfly-ejb3-7.1.0.GA-redhat-11.jar:7.1.0.GA-redhat-11] at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:379) [wildfly-ejb3-7.1.0.GA-redhat-11.jar:7.1.0.GA-redhat-11] Expected results: VM name changed with no NullPointerException Additional info:
verified in ovirt-engine-4.1.9-0.2.el7.noarch
environment for verification compute-ge-he-2.qa.lab.tlv.redhat.com
This bugzilla is included in oVirt 4.1.9 release, published on Jan 24th 2018. Since the problem described in this bug report should be resolved in oVirt 4.1.9 release, published on Jan 24th 2018, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.