Red Hat Bugzilla – Bug 1252408
[oVirt Live] NullPointerException after "Restarting httpd."
Last modified: 2016-02-10 07:50:53 EST
Description of problem:
I'm trying to run oVirt Live with CentOS 7, because standard image with CentOS 6 is not working anymore for HW problem or something.
But during oVirt setup process I'm getting NullPointerException, which happens right after "Restarting httpd". Here are logs of setup:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Make USB-flash of oVirt Live based on CentOS 7 with Fedora LiveUSB Creator.
2. Boot from USB.
3. Run automatic oVirt setup.
Failed setup with NullPointerException after "Restarting httpd."
Succeeded setup with working oVirt.
2015-08-11 12:26:00,963 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-5)  Exception: javax.ejb.EJBException: java.lang.NullPointerException
Moving to ovirt-engine-api, infra vertical.
The relevant part of the log is the following:
Caused by: java.lang.NullPointerException
And the code at Backend.java:485 is like this:
returnValue = ExecutionHandler.evaluateCorrelationId(commandBase.getParameters());
The only way that a NPE can be generated there is if "commandBase" is null. That "commandBase" parameter is generated in the "runActionImpl" method as follows:
CommandBase<?> command = CommandsFactory.createCommand(actionType, parameters, context);
result = runAction(command, runAsInternal);
So I think that the problem is that this code is running at a point where the backend isn't yet completely initialized, maybe before some dependencies are injected.
The RESTAPI takes the Backend object from the JNDI java:global name space, and it assumes that is is completely initialized. The backend needs to make sure that everything is completely initialized before the EJB is registered in the JNDI java:global environment. This usually means making sure that all the initialization has been completed before finishing the @PostConstruct method.
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Sandro - does it still happen?
Can't reproduce with http://plain.resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-live/el7-rc1/ovirt-live-el7-rc1.iso
Nika, can you please verify on your system?
Ravi, I suggest to re-target to 3.6.0-rc since it looks like it has been fixed there
(In reply to Sandro Bonazzola from comment #6)
> Can't reproduce with
> Nika, can you please verify on your system?
Sorry for long response. Yes, it now works with this build.
Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Based on comment 8 put to verified