Description of problem: I was working with RHEVM without problem, but after I left it for a while and reopened, error occured. I kept getting error pop-up window saying "Error while executing action: A Request to the Server failed with the following Status Code: 500". When I closed it, i got another one: "Error while executing query: null". When I closed this one, i got the previous error etc. How reproducible: Not sure, but there's a chance it's related with session timeout? Version-Release number of selected component (if applicable): RHEVM 4.0.6-4 and 4.0.6-3 JBEAP 7.0.3 (manual installed non latest version since with latest 7.0.4 there's bug 1400619 related) Steps to Reproduce: 1. install & start RHEVM 2. open UI and wait 3. Actual results: Error popup you can't get rid of Expected results: Working UI Additional info: Logs attached (4.0.6-4 and 4.0.6-3 were tried on same engine database so they're in same log)
Can you please attach the complete server, engine and ui logs?
Created attachment 1227880 [details] logs from engine
Alexander - can you take a look? Dusan, can you please clear your cache, close the browser, open it and then try the same?
Looking at the engine log, I see a very sick system. The engine cannot communicate with HOST1 or 2. Also looking at the server.log it appears the browser is running a client permutation that doesn't exist on the server anymore, and thus all of the requests are being rejected (maybe you upgraded/downgraded while the browser was still open?). I would do 2 things: 1. restart the engine to hopefully clear out the task queue, and maybe restore communication with the hosts. 2. Refresh the browser to load the correct permutation.
Reducing the severity, as it doesn't seem like a real issue (see last comment). Let's wait for the needinfo to be resolved and if it is a real issue I'll raise the severity accordingly.
Alexander, the "sickness" of system came probably because of experimental switching rhev for 4.0.6-3 while preserving engine database, but error itself occured before that, while system was fine and clean. Nevertheless, after cleaning browser cache & reopening it works normally. (which is strange because 3 days ago the same cleanup didn't change anything)
Dusan - thanks for testing this. I'm Closing. Please reopen if it happens again.
Actually, this is very likely the problem discussed in bug 1402401 *** This bug has been marked as a duplicate of bug 1402401 ***