Bug 797963

Summary:

Need to resolve differences between new 7.1.0 standalone.xml and migrated standalone.xml

Product:

OKD

Reporter:

Dan McPherson <dmcphers>

Component:

Containers

Assignee:

Bill DeCoste <wdecoste>

Status:

CLOSED CURRENTRELEASE

QA Contact:

libra bugs <libra-bugs>

Severity:

high

Docs Contact:

Priority:

high

Version:

2.x

CC:

rmillner, xtian

Target Milestone:

---

Keywords:

Triaged

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2012-03-02 21:56:25 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Attachments:

Description	Flags
7.0.2_standalone.xml	none
7.1.0 standalone.xml	none
migrated standalone.xml	none

Description Dan McPherson 2012-02-27 16:21:41 UTC

Description of problem:
Opening this bug so we don't forget to make any necessary changes.

Known issues:
- Remoting
- Was the copyright removed on purpose?
- Are we going to turn off console?
- Are we going to use env. consistently and migrate all the existing apps so we can change our code?



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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Dan McPherson 2012-02-27 16:22:15 UTC

Created attachment 566082 [details]
7.0.2_standalone.xml

Comment 2 Dan McPherson 2012-02-27 16:22:41 UTC

Created attachment 566083 [details]
7.1.0 standalone.xml

Comment 3 Dan McPherson 2012-02-27 16:23:03 UTC

Created attachment 566084 [details]
migrated standalone.xml

Comment 4 Dan McPherson 2012-02-28 04:21:23 UTC

From Scott:

1. Yes, copyright was removed as it is now located in the jboss-as-7.1.0.Final/LICENSE.txt file. I guess this is a general move we are making with projects.
2. We can remove the management-interfaces/http-interface section to not expose the web version of the management console, even though this is not usable by default because there are no admin users defined.
3. Yes, we should use the env. prefix consistently. We should be migrating or simply have users to that.

Comment 5 Bill DeCoste 2012-02-28 21:30:26 UTC

Disabled remoting, management, and console logging. Also updated the xslt.

Comment 6 Dan McPherson 2012-02-28 21:44:17 UTC

What about the env vars?

Comment 7 Bill DeCoste 2012-02-28 22:04:44 UTC

Just updated ${OPENSHIFT...} to ${env.OPENSHIFT...}

Comment 8 Dan McPherson 2012-02-29 00:26:53 UTC

I'm still not seeing env. in the migrated ones.

Comment 9 Xiaoli Tian 2012-02-29 10:36:40 UTC

Yeah, I also not seeing env. after migration. the following is copied from the merged one after migration:


      <loopback-address value="${OPENSHIFT_INTERNAL_IP}"/>
    </interface>
    <interface name="public">
      <loopback-address value="${OPENSHIFT_INTERNAL_IP}"/>

Comment 10 Bill DeCoste 2012-02-29 13:07:20 UTC

Dan and I fixed this last night - should be in the next build.

Comment 11 Xiaoli Tian 2012-03-01 07:06:05 UTC

Have tested this on devenv-stage_139 , environment variables have been changed to env.OPENSHIFT... like:
      <user-name>${env.OPENSHIFT_DB_USERNAME}</user-name>
      <password>${env.OPENSHIFT_DB_PASSWORD}</password>