Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/

Bug 1159265

Summary: glance-api get ECONNREFUSED when connecting to glance registy when using bind_host in glance-registry.conf
Product: [Community] RDO Reporter: Daniel <liquidsmail>
Component: openstack-glanceAssignee: Flavio Percoco <fpercoco>
Status: CLOSED NOTABUG QA Contact: nlevinki <nlevinki>
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: eglynn, fpercoco, liquidsmail, yeylon
Target Milestone: ---   
Target Release: Juno   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-31 13:35:36 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:
Attachments:
Description Flags
Extended information none

Description Daniel 2014-10-31 10:36:01 UTC
Created attachment 952451 [details]
Extended information

Description of problem:

When I use the bind_host option, so glance-registry port is only binded to and IP address, I get exception.ClientConnectionError from the the glance-api when it tries to connect with glance-registry.

 File "/usr/lib/python2.6/site-packages/glance/common/client.py", line 550, in _do_request
    raise exception.ClientConnectionError(e)
ClientConnectionError: [Errno 111] ECONNREFUSED

Using strace on glance-api,looks like it allways tries to connect against 0.0.0.0:9191, altough we are only listening on one binded IP(192.168.X.X).

# cat strace-glance-api.txt | grep 9191
connect(7, {sa_family=AF_INET, sin_port=htons(9191), sin_addr=inet_addr("0.0.0.0")}, 16) = -1 EINPROGRESS (Operation now in progress)

I have attached a .txt with all the logs and config info.

I have only tried it, in two installations using Virtual Machines.

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

openstack-glance-2014.1.2-5.el6.noarch
python-glance-2014.1.2-5.el6.noarch


How reproducible:

Steps to Reproduce:
1.edit /etc/glance/glance-registry.conf bind it to a configured IP on the server(192.168.124.X)
2.Restart service glance-registry
3.glance image-list Fails to connect

Actual results:

ClientConnectionError: [Errno 111] ECONNREFUSED

Expected results:

The output of the glance command, as you get when you don't use the bind_port  in glance-registry.conf

Additional info:

Attached in .txt

Comment 1 Flavio Percoco 2014-10-31 10:46:39 UTC
Hey Daniel,

Thanks for the report. I've a question for you.

Did you also update the `registry_host`[0] option in `glance-api.conf` after you changed the bind_ip for the registry service?

This option needs to be updated and the glance-api service ought to be restarted for it to work.

Let me know!

[0] https://github.com/openstack/glance/blob/master/etc/glance-api.conf#L149

Comment 2 Daniel 2014-10-31 13:35:36 UTC
Hi Flavio,

I tested on both enviroments as you suggested and it works fine, I looked for 0.0.0.0 in all the glance .conf files to try and see if it was a conf option, but somehow I missed the registry_host.

Sorry for waisting your time.

Thanks.

Regards.

Comment 3 Flavio Percoco 2014-10-31 13:51:52 UTC
Daniel,

Thanks for getting back, you didn't waste anyone's time, if anything I'm happy you reported the issue you were having.

Cheers