Bug 922572

Summary: Console Configuration Script adds invalid 'security' configuration for ENGINEDataSource in JBoss
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Jason Shepherd <jshepherd>
Component: rhscAssignee: Aravinda VK <avishwan>
Status: CLOSED ERRATA QA Contact: Prasanth <pprakash>
Severity: high Docs Contact:
Priority: medium    
Version: 2.0CC: juan.hernandez, pprakash, rhs-bugs, sabose, shaines, shireesh
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: rhsc-2.0.techpreview1-4 Doc Type: Known Issue
Doc Text:
Cause: Update of Jboss after RHS console is installed Consequence: Application is not deployed. Accessing the RHS console results in an HTTP 500 error Workaround (if any): Edit the standalone.xml under jbossas/standalone/configuration/standalone.xml Remove <user-name> tag from security element under datasource element Result: Able to access the RHS console web application
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-28 22:29:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jason Shepherd 2013-03-18 00:27:37 UTC
Description of problem:

After running the console installation script, the Web GUI fails to start. There is an error like this JBoss server.log:

14:16:54,475 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 27) JBAS014613: Operation ("enable") failed - address: ([
    ("subsystem" => "datasources"),
    ("data-source" => "ENGINEDataSource")
]) - failure description: "JBAS010436: Failed to create DataSource instance for [{
    \"operation\" => \"enable\",
    \"address\" => [
        (\"subsystem\" => \"datasources\"),
        (\"data-source\" => \"ENGINEDataSource\")
    ],
    \"persistent\" => true
}]
 reason: IJ010073: Invalid <security> configuration"

Version-Release number of selected component (if applicable):


How reproducible:
Follow the installation guide, then try to access the Web GUI in the browser. 

Steps to Reproduce:
1. Follow 

https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Storage/2.0/html-single/Console_Installation_Guide/index.html#sect-Installation_Guide-Installing_the_RHEV_Manager-Configuration

2. Try to access the Web GUI at:

webadmin/webadmin/WebAdmin.html#login
  
Actual results:

You get an 500 ERROR Page

Expected results:

The Web GUI is displayed

Additional info:

the 'security' element of the 'datasource' cannot have a 'user-name', and 'security-domain'. It works fine without a 'user-name', and only 'security-domain'.

Comment 2 Shireesh 2013-03-18 09:41:11 UTC
Hi Juan, have you come across any issue like this in RHEV-M?

Comment 3 Juan Hernández 2013-03-18 10:34:56 UTC
I believe this is a problem with a redundant user name, that is accepted by older versions of JBoss but not by new versions. See more details here:

http://gerrit.ovirt.org/8611

I think that the file affected by this change doesn't exist in the RHS-C, as it was forked before the file was added. You will probably need to modify the engine-setup script instead, something like this:

diff --git a/packaging/fedora/setup/engine-setup.py b/packaging/fedora/setup/engine-setup.py
index 8bd3f69..f507375 100755
--- a/packaging/fedora/setup/engine-setup.py
+++ b/packaging/fedora/setup/engine-setup.py
@@ -2032,9 +2032,6 @@ def configJbossDatasource(xmlObj):
             </prefill>
         </pool>
         <security>
-            <user-name>
-                engine
-            </user-name>
             <security-domain>
                 EncryptDBPassword
             </security-domain>

Note that this patch is for the upstream engine_3.0, it will probably need adjustment for RHS-C.

For existing installations the user will probably need to manually modify the /usr/share/jbossas/standalone/configuration/standalone.xml file to remove the <user-name> tag.

Comment 4 Aravinda VK 2013-03-20 07:25:46 UTC
Patch sent for review. 
https://code.engineering.redhat.com/gerrit/#/c/4304/

Comment 5 Prasanth 2013-03-21 05:59:03 UTC
Is this fix available in the rhsc channel? If not, please let me know how to verify this bug.

Comment 6 Prasanth 2013-03-21 12:24:13 UTC
Verified as fixed in rhsc-2.0.techpreview1-4.el6rhs.noarch

Comment 8 errata-xmlrpc 2013-03-28 22:29:01 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/RHSA-2013-0691.html