Description of problem: rhc port-forward oamiintrtpdev -n oaminprd -d ... Checking available ports ... DEBUG: #<RHC::Commands::ForwardingSpec:0x007fb47d0ca538> DEBUG: #<RHC::Commands::ForwardingSpec:0x007fb47d0ca038> DEBUG: #<RHC::Commands::ForwardingSpec:0x007fb47d0c9b60> DEBUG: #<RHC::Commands::ForwardingSpec:0x007fb47d0c9408> DEBUG: #<RHC::Commands::ForwardingSpec:0x007fb47d0c8c60> DEBUG: #<RHC::Commands::ForwardingSpec:0x007fb47d0c83f0> done Forwarding ports ... Version-Release number of selected component (if applicable): 1.35.1 How reproducible: Undetermined Steps to Reproduce: See above Actual results: Forwarding Spec object is displayed instead of port forwarding information. Expected results: Expecting to see port-forwarding information, for each of the ports. Additional info:
Hi, when QE setting up 2.2 env, found it's blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1321858.
Thanks for the quick fix on installation. Build an ose-2.2 env with OpenShiftEnterpriseErrata/2.2/2016-03-29.1, create a jbosseap app with postgresql-9.2 embed, run port-forward in debug mode. [root@broker ~]# rhc port-forward app1 -d DEBUG: Using config file /root/.openshift/express.conf DEBUG: Git config 'git config --get rhc.app-id' returned '' DEBUG: Git config 'git config --get rhc.app-name' returned '' DEBUG: Git config 'git config --get rhc.domain-name' returned '' DEBUG: Authenticating with RHC::Auth::Token DEBUG: Connecting to https://broker.ose22-auto.com.cn/broker/rest/api DEBUG: Getting all domains DEBUG: Client supports API versions 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7 DEBUG: Created new httpclient DEBUG: Request GET https://broker.ose22-auto.com.cn/broker/rest/api DEBUG: SSL Verification failed -- Using self signed cert DEBUG: code 200 46 ms DEBUG: Server supports API versions 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7 DEBUG: Using API version 1.7 DEBUG: Client API version 1.7 is not current. Refetching API DEBUG: Request GET https://broker.ose22-auto.com.cn/broker/rest/api DEBUG: SSL Verification failed -- Using self signed cert DEBUG: code 200 25 ms DEBUG: Using token authentication DEBUG: Request GET https://broker.ose22-auto.com.cn/broker/rest/domains DEBUG: SSL Verification failed -- Using self signed cert DEBUG: code 200 32 ms DEBUG: Using token authentication DEBUG: Request GET https://broker.ose22-auto.com.cn/broker/rest/domain/yes/application/app1 DEBUG: SSL Verification failed -- Using self signed cert DEBUG: code 200 42 ms DEBUG: Using ssh://yes-app1-1.com.cn... Checking available ports ... DEBUG: Found service java with remote host 127.2.93.129 and port 3528 DEBUG: Found service java with remote host 127.2.93.129 and port 4447 DEBUG: Found service java with remote host 127.2.93.129 and port 5445 DEBUG: Found service java with remote host 127.2.93.129 and port 5455 DEBUG: Found service java with remote host 127.2.93.129 and port 8080 DEBUG: Found service java with remote host 127.2.93.129 and port 9990 DEBUG: Found service java with remote host 127.2.93.129 and port 9999 DEBUG: Found service postgresql with remote host 127.2.93.130 and port 5432 done Forwarding ports ... DEBUG: [3528, "127.2.93.129", 3528] DEBUG: [4447, "127.2.93.129", 4447] DEBUG: [5445, "127.2.93.129", 5445] DEBUG: [5455, "127.2.93.129", 5455] DEBUG: [8080, "127.2.93.129", 8080] Address already in use - bind(2) while forwarding port 8080. Trying local port 8081 DEBUG: [8081, "127.2.93.129", 8080] DEBUG: [9990, "127.2.93.129", 9990] DEBUG: [9999, "127.2.93.129", 9999] DEBUG: [5432, "127.2.93.130", 5432] To connect to a service running on OpenShift, use the Local address Service Local OpenShift ---------- -------------- ---- ----------------- java 127.0.0.1:3528 => 127.2.93.129:3528 java 127.0.0.1:4447 => 127.2.93.129:4447 java 127.0.0.1:5445 => 127.2.93.129:5445 java 127.0.0.1:5455 => 127.2.93.129:5455 java 127.0.0.1:8081 => 127.2.93.129:8080 java 127.0.0.1:9990 => 127.2.93.129:9990 java 127.0.0.1:9999 => 127.2.93.129:9999 postgresql 127.0.0.1:5432 => 127.2.93.130:5432 Press CTRL-C to terminate port forwarding
The rhc package version is rhc-1.38.6.1-1.el6op.noarch.
Closing this bug since it has been confirmed to be resolved.