OpenStack Compute (nova)

httplib throw "TypeError: an integer is required" when run quantum on fedora and redhat

Bug #993149 reported by Hua Zhang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Low
Hua Zhang
OpenStack Compute (nova) 2012.2 "folsom"

Bug Description

httplib throws exception "TypeError: an integer is required" from following method of file $nova/nova/network/quantum/client.py when run quantum on fedora or redhat.

c.request(method, action, body, headers)

the reason is that following nova code pass a host value to httplib that is not int, it leads to httplib lose the socket connection, then throws above exception.

more details can refer https://answers.launchpad.net/nova/+question/194444

Revision history for this message
Hua Zhang (zhhuabj) wrote :

fixing it is very easy, can just edit file $nova/network/quantum/quantum_connection.py,

self.client = quantum_client.Client(FLAGS.quantum_connection_host,
- FLAGS.quantum_connection_port,
+ int(FLAGS.quantum_connection_port),
                                             format="json",
                                             logger=LOG)

Hua Zhang (zhhuabj)
Changed in nova:
assignee: nobody → Hua Zhang (zhhuabj)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/7015

Changed in nova:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/7015
Committed: http://github.com/openstack/nova/commit/61a515a5a7feeeacd17821456459eb4cc828c695
Submitter: Jenkins
Branch: master

commit 61a515a5a7feeeacd17821456459eb4cc828c695
Author: hua zhang <email address hidden>
Date: Tue May 8 16:38:35 2012 +0800

    httplib throw "TypeError: an integer is required" when run quantum

    Bug 993149

    Change-Id: Ife663ec1cf2b9d094a00c488f849da5857cc34a3

Changed in nova:
status: In Progress → Fix Committed
Revision history for this message
Unmesh Gurjar (unmesh-gurjar) wrote :

I faced this issue on stable/essex, is this fix going to be back-ported ?

Devin Carlen (devcamcar)
Changed in nova:
milestone: none → folsom-1
importance: Undecided → Low
Thierry Carrez (ttx)
Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: folsom-1 → 2012.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.