Created attachment 689817 [details] Errors shown in web page when trying to access AdminPortal of RHS-C Description of problem: I have had an installation of RHS-C running for some time. The patches released to channel last December appear to have broken the console. When I try to servers root webpage, I see the options for Admin/User/Report portals as expected. But selecting any of them results in an error (attached) Version-Release number of selected component (if applicable): 2.0 Tech preview How reproducible: I have repeated the yum update -> reboot process on two different machines, with the same outcome. Steps to Reproduce: 1. Update RHS-C server to latest level with yum update 2. reboot 3. attempt to access the webpages for the console Actual results: Multiple java exceptions raised, and stack trace taken Expected results: Access to the console after routine maintenance should result in a functioning product Additional info: There was a similar bug for RHEVM - 879904 - which may be related to this issue
Yes - the error is exactly same as reported in bug 879904
*** Bug 906960 has been marked as a duplicate of this bug. ***
Actually I just found out that Bug 889217 is almost identical to this bug, but it is on the RHEV-M side.
Per Feb-06 bug triage meeting, targeting for 2.1.0.
Tushar, does the work-around suggested in below conversation acceptable? -------- Original Message -------- Subject: Re: need help Date: Fri, 08 Mar 2013 09:45:49 +0100 From: Juan Hernandez <jhernand> To: Shireesh Anjal <sanjal> CC: Tushar Katarki <tkatarki>, Scott Haines <shaines>, Vijay Bellur <vbellur>, Vinayaga Raman <vraman>, rhsc-dev, Fernando Nasser <fnasser> ... >> >>> 2) Provide a script to customer that must be executed before starting >>> JBoss, to do something similar to what your patch does in >>> engine-service.py ? >> >> If providing an script is an acceptable solution then it is as simple >> as this: >> >> find /usr/share/jbossas/modules -name '*.jar.index' -delete > > IIUC, this is not required every time you restart jboss, but only if you > performed a "yum update" and engine stopped working because of that. Am > I right? If so, I think this is a reasonable work-around that we can > document. > Correct, it is only required after updating JBoss. The problem is that "updating JBoss" means "updating any of the approx 250 packages that contain .jar files used by JBoss". Note that not every update will trigger the issue, as many updates will just change things inside a class and not add/remove classes, thus affecting the correctness of the .jar.index file. All in all I think that documenting this workaround and suggesting to use it after every update is a good compromise, specially taking into account that it won't be needed after the next rebase from upstream, which will include the proper fix.
Documented as Known Issue in RHS-2.0+ Update 4. Refer Doc text for work around.