| Summary: | Support running JBoss AS 7 testsuite against OpenShift (tracking) | ||
|---|---|---|---|
| Product: | OKD | Reporter: | Ondřej Žižka <ozizka> |
| Component: | Containers | Assignee: | Dan Mace <dmace> |
| Status: | CLOSED UPSTREAM | QA Contact: | libra bugs <libra-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.x | CC: | dmcphers, kraman, mmcgrath, mpatel |
| 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: | 2013-02-14 19:32:15 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: | |
|
Description
Ondřej Žižka
2012-04-09 17:38:08 UTC
1) There's a timeout which kills the build. I need to be able to configure this. 2) I need to be able to get to the results of the build. 3) The build runs with -DskipTests. I need to be able to override this. 4) I can风t connect to management. I've tried jboss-cli.sh and
connect as7ts2-ondra.rhcloud.com
but got:
The controller is not available at as7ts2-ondra.rhcloud.com:9999
Dan, any update on this one? (In reply to comment #2) > 4) I can风t connect to management. I've tried jboss-cli.sh and > > connect as7ts2-ondra.rhcloud.com > > but got: > > The controller is not available at as7ts2-ondra.rhcloud.com:9999 Perhaps using the cli tools and port forwarding will solve this rhc port-forward $APPNAME Then try to connect to localhost. Port 9999 is not exposed to the world. I created a new jbossas-7 app, and then forwarded ports: $ rhc port-forward jbossapp -pp Checking available ports... Forwarding ports Service Connect to Forward to ==== ================== ==== ================== java 127.0.250.129:3528 => 127.0.250.129:3528 java 127.0.250.129:4447 => 127.0.250.129:4447 java 127.0.250.129:5445 => 127.0.250.129:5445 java 127.0.250.129:5455 => 127.0.250.129:5455 java 127.0.250.129:8080 => 127.0.250.129:8080 java 127.0.250.129:9990 => 127.0.250.129:9990 java 127.0.250.129:9999 => 127.0.250.129:9999 Press CTRL-C to terminate port forwarding Then, I connected to the instance through the tunnel using the JBoss CLI tool: $ ./jboss-cli.sh You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. [disconnected /] connect 127.0.250.129:9999 [standalone.250.129:9999 /] version JBoss Admin Command-line Interface JBOSS_HOME: /home/dmace/Applications/jboss-as-7.1.0.Final JBoss AS release: 7.1.0.Final "Thunder" JAVA_HOME: null java.version: 1.7.0_06-icedtea java.vm.vendor: Oracle Corporation java.vm.version: 23.2-b09 os.name: Linux os.version: 3.6.1-1.fc17.x86_64 [standalone.250.129:9999 /] So, #4 works as expected. Converting to user story US3446 to be tracked upstream. |