** Description changed: [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] - ...need to be added... + - 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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368545 Title: Value Type of http_connect_timeout is Wrong To manage notifications about this bug go to: https://bugs.launchpad.net/keystonemiddleware/+bug/1368545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
