Created attachment 1184200 [details] database dump Description of problem: If there are outdated entries that remain in command_entities, it might cause the engine to fail to start. Specifically, in the reported case I see an instance of RunVmCommand in command_entities that refers to VM that has already been removed ('f8b68db9-3503-4295-afd9-92b0596f746d'). Version-Release number of selected component (if applicable): How reproducible: Not sure how to reproduce it exactly, but once we get to this state the engine will never start. Steps to Reproduce: 1. 2. 3. Actual results: NPE prevents the engine from starting. Expected results: The engine should start. Additional info: I set the severity to urgent because it prevents the engine from starting. However, I think that the priority can be lower because we have a workaround that worked - to delete the entries from command_entities.
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
The actual problem of engine strtup is tracked in bug 1360378
Verified with rhevm-4.0.2.3-0.1.el7ev.noarch. Steps to re produce: 1. Invokes an action to fill command_entities table - added a new vm with preallocated disk. 2. Dumped the data from the command_entities table to some file in csv format. 3. Removed vm. 4. Stopped engine. 5. Copied the data from the file back to command_entities table. 6. Started engine. Result: Engine started with no problem. The redundant entries in command_entities table were removed after a certain timeout.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days