Bug 1141567

Summary:	[CISCO RHEL-OSP] Glance image-list Fails to list the image from remote host
Product:	Red Hat OpenStack	Reporter:	satya routray <satroutr>
Component:	openstack-packstack	Assignee:	Martin Magr <mmagr>
Status:	CLOSED DUPLICATE	QA Contact:	Ami Jeain <ajeain>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.0 (RHEL 7)	CC:	aortega, derekh, eglynn, fpercoco, yeylon
Target Milestone:	---	Keywords:	ZStream
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-15 07:16:05 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 satya routray 2014-09-14 20:49:20 UTC

When trying glance image-list getting: 
Error finding address for http://192.168.131.7:9292/v1/images/detail?sort_key=name&sort_dir=asc&limit=20: ('Connection aborted.', error(113, 'No route to host'))

Semi dist' setup installed using packstack
Selinux Permissive.

Version-Release number of selected component (if applicable):
RHEL 7
python-glance-2014.1.2-1.el7ost.noarch
python-glanceclient-0.13.1-1.el7ost.noarch
openstack-glance-2014.1.2-1.el7ost.noarch

How reproducible:
1. Install Redhat openstack platform 5
2. install another machine (say machine 2) with all clients
3. copy the keystonerc_admin file on machine 2
4. source the keystonerc_admin file
5. do a glance image-list

Actual results:

Error finding address for http://192.168.131.7:9292/v1/images/detail?sort_key=name&sort_dir=asc&limit=20: ('Connection aborted.', error(113, 'No route to host')) 

Expected results:

Should complete glance command.

Additional info:

Comment 2 satya routray 2014-09-14 21:06:02 UTC

it seems to be an IPTABLES issue where port 9292 is not open
opening the port 9292 make it works fine

Comment 3 Flavio Percoco 2014-09-15 07:16:05 UTC


*** This bug has been marked as a duplicate of bug 1129742 ***