Bug 891632 - RHEV-M 3.1 instance died after RHSA-2012:1592-1 installation
Summary: RHEV-M 3.1 instance died after RHSA-2012:1592-1 installation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 3.1.3
Assignee: Juan Hernández
QA Contact: Pavel Stehlik
URL:
Whiteboard: integration
Depends On: 889217
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-03 13:17 UTC by Chris Pelland
Modified: 2013-03-12 14:27 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, out of date index files left over from a JBoss service would cause updating the Red Hat Enterprise Virtualization environment using yum update to completely crash the environment, displaying 404 errors when the manager tried to load. Now, a copy is made of the JBoss modules directory (a shallow copy, using symlinks) but excluding the indexes. The copy is used instead of the original, thus there is no problem even if the indexes are out of date.
Clone Of: 889217
Environment:
Last Closed: 2013-03-12 14:27:09 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0557 0 normal SHIPPED_LIVE rhevm 3.1.3 bug fix update 2013-03-12 18:26:15 UTC
oVirt gerrit 10292 0 None None None Never

Comment 5 David M. Lloyd 2013-01-23 15:00:59 UTC 
Can someone please remove MODULES-105?  As far as I can tell there is absolutely no relationship between this bug and that, and the BZ<->JIRA integration is causing every status change and comment to be reflected in JIRA, annoyingly.
Comment 6 Juan Hernández 2013-01-23 15:56:36 UTC 
(In reply to comment #5)
> Can someone please remove MODULES-105?  As far as I can tell there is
> absolutely no relationship between this bug and that, and the BZ<->JIRA
> integration is causing every status change and comment to be reflected in
> JIRA, annoyingly.

I removed MODULES-105.

However there is a relation, as the fix for MODULES-105 was intended to resolve an issue (out of date .index.jar files in the modules directory) that still exists in some situations in EAP6.
Comment 7 David M. Lloyd 2013-01-23 21:37:04 UTC 
Okay, that's fair.  I am separately requesting that an enhancement be enacted to prevent all status changes and comments from cross-propagating between the two trackers though.  Hopefully that will cut down on things.

Thanks though.
Comment 8 Juan Hernández 2013-02-26 07:43:57 UTC 
Jodi, the doc text is not accurate. The initial suggestion to fix the issue was to remove the out of date indexes as you describe in the doc text, but that was rejected. Instead of removing the out of date indexes what we are doing is making a copy of the JBoss modules directory (a shallow copy, using symlinks) but excluding the indexes. Then we use this copy instead of the original, thus there is no problem even if the indexes are out of date.
Comment 9 Jodi Biddle 2013-02-26 08:05:34 UTC 
Juan - thank you very much for reviewing my doc text, it's greatly appreciated. 

Can you please take a look at the new doc text and confirm I've worded it correctly?
Comment 10 Juan Hernández 2013-02-26 08:14:06 UTC 
Jodi, the doc text is accurate now in my opinion. Thanks for the prompt reaction!
Comment 13 errata-xmlrpc 2013-03-12 14:27:09 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0557.html
Note You need to log in before you can comment on or make changes to this bug.