Created attachment 935687[details]
vdsm+engine logs
Description of problem:
The operation of oVirt-engine service restart does not handle well the existence of active tasks if the number of those tasks exceeds $CERTAIN_NUMBER.
And when I say "does not handle well" I mean,internal engine server NullPointer failure(see image).
After a while the engine comes back,but it reports so slowly I had to wipe the setup in order to regain the usual speed (tried to restart engine again,restart vdsm,reboot)
Version-Release number of selected component (if applicable):
rhev 3.5 vt2.2
How reproducible:
100%
Steps to Reproduce && Actual results:
In order to reproduce this bug,we need some how to cause the engine to accumulate tasks(mine had 35 before restarting the engine)
step 1: accumulating tasks
1.initiating an unsuccessful template creation (like BZ #1139678)
2.or you can delete a lot of disks with wipe after delete flag on
step 2: restart engine
1.after accumulating more than 25 tasks restart engine's service
2.Error 500 will appear,wait for engine to come back(it will take a while)
3. login again,engine reports incredibly slow
Expected results:
restarting oVirt-engine should know how to "kill" it's tasks safely,not causing such failures
Additional info:
I am unable to reproduce this. From the logs it looks like the 500 error is related to database connection issue. All the other exceptions are related to BZ 1105211.
Please retest
Created attachment 937340[details]
vdsm+engine logs + image
(In reply to Ravi Nori from comment #1)
> I am unable to reproduce this. From the logs it looks like the 500 error is
> related to database connection issue. All the other exceptions are related
> to BZ 1105211.
>
> Please retest
1) I have divided this bug into two bugs,BZ #1141540 deals with database connections problems due to multi-diskRemove operations while this bug will deal with restarting oVirt-engine after a several fails to create template because of broken volume chain.
2) When retesting this bug on rhev vt3.1 (accumulate template failures and restart engine) no NPE was thrown on engine logs,though,NullPointer message did appeared on browser(see image).