Public bug reported: With https://bugs.launchpad.net/nova/+bug/1773225 we addressed a better way to lookup HTTP headers but unfortunately the WebOb change wasn't backwards compatible with webob versions older than 1.8.
Since upstream requirements still support WebOb in 1.7.1 and higher (up to 1.8.2) [1], some Placement deployments could still using this 1.7 version and throw an AttributeError exception. For example, TripleO CI is reporting an incompatible usage in [2] [1] https://github.com/openstack/requirements/blob/6766f353b2e814ecbd36dd08216022cf2024c03b /lower-constraints.txt#L18 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1596308 ** Affects: nova Importance: High Assignee: Sylvain Bauza (sylvain-bauza) Status: Confirmed ** Tags: placement -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1779287 Title: placement can throw exception if webob<1.8 in use Status in OpenStack Compute (nova): Confirmed Bug description: With https://bugs.launchpad.net/nova/+bug/1773225 we addressed a better way to lookup HTTP headers but unfortunately the WebOb change wasn't backwards compatible with webob versions older than 1.8. Since upstream requirements still support WebOb in 1.7.1 and higher (up to 1.8.2) [1], some Placement deployments could still using this 1.7 version and throw an AttributeError exception. For example, TripleO CI is reporting an incompatible usage in [2] [1] https://github.com/openstack/requirements/blob/6766f353b2e814ecbd36dd08216022cf2024c03b /lower-constraints.txt#L18 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1596308 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1779287/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
