You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Michal Fojtik (JIRA)" <ji...@apache.org> on 2013/03/18 15:16:15 UTC
[jira] [Closed] (DTACLOUD-475) Cannot connect to Deltacloud server
started on Fedora 18 from a machine other than the host
[ https://issues.apache.org/jira/browse/DTACLOUD-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michal Fojtik closed DTACLOUD-475.
----------------------------------
Resolution: Cannot Reproduce
Assignee: Michal Fojtik
I tried hard to reproduce this but no luck. I think it was some routing/firewall problem. If not, please feel free to re-open this issue.
> Cannot connect to Deltacloud server started on Fedora 18 from a machine other than the host
> -------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-475
> URL: https://issues.apache.org/jira/browse/DTACLOUD-475
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: Fedora 18
> Deltacloud server - any frontend
> Deltacloud gem 1.1.1 - under test
> Reporter: Ronelle Landy
> Assignee: Michal Fojtik
>
> Start a Deltacloud server using the -r option on a Fedora 18 machine:
> >> cat /etc/redhat-release
> Fedora release 18 (Spherical Cow)
> >> deltacloudd -i mock -r qeblade39.rhq.lab.eng.bos.redhat.com -p 3005
> Starting Deltacloud API :: mock :: http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api
> >> Thin web server (v1.5.0 codename Knife)
> >> Debugging ON
> >> Maximum connections set to 1024
> >> Listening on qeblade39.rhq.lab.eng.bos.redhat.com:3005, CTRL+C to stop
> Open a second terminal on the same host machine where the server was started and execute a curl command against the Deltacloud server:
> >> hostname
> qeblade39.rhq.lab.eng.bos.redhat.com
> >> curl -X GET --user "un:pw" "http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api?format=xml"
> <api driver='mock' version='1.1.1'>
> <link href='http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api/instance_states' rel='instance_states'>
> </link>
> <link href='http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api/addresses' rel='addresses'>
> </link>
> <link href='http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api/metrics' rel='metrics'>
> </link>
> <link href='http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api/images' rel='images'>
> </link>
> <link href='http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api/storage_volumes' rel='storage_volumes'>
> </link>
> <link href='http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api/keys' rel='keys'>
> </link>
> <link href='http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api/hardware_profiles' rel='hardware_profiles'>
> </link>
> <link href='http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api/drivers' rel='drivers'>
> </link>
> <link href='http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api/realms' rel='realms'>
> </link>
> <link href='http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api/buckets' rel='buckets'>
> </link>
> <link href='http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api/instances' rel='instances'>
> <feature name='metrics' rel='create'>
> <param name='metrics' />
> </feature>
> <feature name='realm_filter' rel='index'>
> <param name='realm_id' />
> </feature>
> <feature name='user_name' rel='create'>
> <param name='name' />
> </feature>
> <feature name='user_data' rel='create'>
> <param name='user_data' />
> </feature>
> <feature name='authentication_key' rel='create'>
> <param name='keyname' />
> </feature>
> </link>
> <link href='http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api/storage_snapshots' rel='storage_snapshots'>
> </link>
> </api>
> [root@qeblade39 ~]#
> Using localhost w/o the -r option works as well for executing commands on the same host.
> Try the same command from a different host machine:
> >> hostname
> cloud-qe-3.idm.lab.bos.redhat.com
> >> curl -X GET --user "un:pw" "http://qeblade39.rhq.lab.eng.bos.redhat.com:3005/api?format=xml"
> curl: (7) couldn't connect to host
> The -r option works to connect on RHEL 6.3 and Fedora 16, 17.
> Tried disabling SELinux didn't do much for me.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira