[Bug 1368545] Re: Value Type of http_connect_timeout is Wrong

[Launchpad Bug Tracker]

This bug was fixed in the package python-keystoneclient -
1:0.7.1-ubuntu1.3

---------------
python-keystoneclient (1:0.7.1-ubuntu1.3) trusty; urgency=medium

  * debian/patches/fix-1368545.patch: hanging the value type of
    http_connect_timeout to IntOpt. (LP: #1368545)

 -- Jorge Niedbalski <jorge.niedbalski at canonical.com>  Fri, 07 Aug 2015
10:50:46 -0300

** Changed in: python-keystoneclient (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to python-keystoneclient in Ubuntu.
https://bugs.launchpad.net/bugs/1368545

Title:
  Value Type of http_connect_timeout is Wrong

Status in keystonemiddleware:
  Fix Released
Status in python-keystoneclient:
  Won't Fix
Status in python-keystoneclient package in Ubuntu:
  Fix Released
Status in python-keystoneclient source package in Trusty:
  Fix Released
Status in python-keystoneclient source package in Vivid:
  Fix Released

Bug description:
  [Impact]

  we can't configure http_connect_timeout more than 1.
  http_connect_timeout is defined as Boolean value in python-
  keystoneclient and keystonemiddleware since python can treat a value
  more than 1 as True. But oslo config defines Boolean values as 'true',
  1, 'yes' and 'on'.

  To be able to configure the value, keystoneclient and
  keystonemiddleware should change the type of the config to Int.

  [Test Case]
  - Edit the [keystone_authtoken] section (nova or ceilometer config), adding the parameter:
  http_connect_timeout = 900
  - Restart the service
  - If debug is enabled the following entries should be printed on log:

  - 2015-08-10 13:50:16.372 11612 INFO urllib3.connectionpool [-]
  Starting new HTTPS connection (1): 10.93.68.29

  2015-08-10 13:50:16.403 11612 DEBUG urllib3.connectionpool [-] Setting
  read timeout to 900 _make_request /usr/lib/python2.7/dist-
  packages/urllib3/connectionpool.py:390

  Without the patch the read timeout is set to an incorrect boolean
  value.

  [Regression Potential]
  The change is minimal. That said, however, since the timeout value has only been set to limited values in the past, the fix enables a wider range of timeout values.  This needs to be considered as part of the SRU testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystonemiddleware/+bug/1368545/+subscriptions