Re: [Openstack-stable-maint] [openstack-dev] Stable/grizzly
2013/10/10 Gary Kotton <gkotton@vmware.com>:
The problem seems to be with the boto python library. I am not really familiar with this but I have seen this is the last – we may need to update the requirements again to exclude a specific version.
Yeah, it's bad boto update again: -boto==2.13.3 +boto==2.14.0 Let's cap it as a quickfix, it's stable/grizzly freeze today so we need gates fixed asap! Cheers, Alan
Alan Pevec wrote:
2013/10/10 Gary Kotton <gkotton@vmware.com>:
The problem seems to be with the boto python library. I am not really familiar with this but I have seen this is the last – we may need to update the requirements again to exclude a specific version.
Yeah, it's bad boto update again: -boto==2.13.3 +boto==2.14.0
Let's cap it as a quickfix, it's stable/grizzly freeze today so we need gates fixed asap!
Do we have a bug filed for this yet ? I'd like to mention it to QA/CI folks when they are up. -- Thierry Carrez (ttx)
On 10/10/2013 06:00 AM, Thierry Carrez wrote:
Alan Pevec wrote:
2013/10/10 Gary Kotton <gkotton@vmware.com>:
The problem seems to be with the boto python library. I am not really familiar with this but I have seen this is the last – we may need to update the requirements again to exclude a specific version.
Yeah, it's bad boto update again: -boto==2.13.3 +boto==2.14.0
Let's cap it as a quickfix, it's stable/grizzly freeze today so we need gates fixed asap!
Do we have a bug filed for this yet ? I'd like to mention it to QA/CI folks when they are up.
Hmph. So boto changed their connection function signatures to have a 3rd argument, and put it second, and nothing has defaults. The unit tests that blow up here already have some boto special casing, my inclination is to add more of it for the version at hand. I'm going to propose something and see if that fixes it (which should be easy to backport). -Sean -- Sean Dague http://dague.net
2013/10/10 Sean Dague <sean@dague.net>:
Hmph. So boto changed their connection function signatures to have a 3rd argument, and put it second, and nothing has defaults.
So isn't that a boto bug? Not sure what their backward-compatibility statement is but it is silly to break API just like that[1] Cheers, Alan [1] https://github.com/boto/boto/commit/789ace93be380ecd36220b7009f0b497dacdc1cb
Trunk - https://review.openstack.org/50904 Stable/Grizzly - https://review.openstack.org/#/c/50905/ There is an alternative patch - https://review.openstack.org/#/c/50873/7 I recall seeing the same problem a few month ago and the bot version was excluded - not sure why the calling code was not updated. Maybe someone who is familiar with that can chime in. Thanks Gary On 10/10/13 12:20 PM, "Alan Pevec" <apevec@gmail.com> wrote:
2013/10/10 Gary Kotton <gkotton@vmware.com>:
The problem seems to be with the boto python library. I am not really familiar with this but I have seen this is the last we may need to update the requirements again to exclude a specific version.
Yeah, it's bad boto update again: -boto==2.13.3 +boto==2.14.0
Let's cap it as a quickfix, it's stable/grizzly freeze today so we need gates fixed asap!
Cheers, Alan
_______________________________________________ Openstack-stable-maint mailing list Openstack-stable-maint@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint
On 10/10/2013 04:42 AM, Gary Kotton wrote:
Trunk - https://review.openstack.org/50904 Stable/Grizzly - https://review.openstack.org/#/c/50905/ There is an alternative patch - https://review.openstack.org/#/c/50873/7 I recall seeing the same problem a few month ago and the bot version was excluded - not sure why the calling code was not updated. Maybe someone who is familiar with that can chime in. Thanks Gary
On 10/10/13 12:20 PM, "Alan Pevec" <apevec@gmail.com> wrote:
Missed the chance to weigh in on the stable review, but is there a reason we're also bumping the minimum required boto version for a stable point update? Adam
On 10/10/2013 02:20 AM, Alan Pevec wrote:
2013/10/10 Gary Kotton <gkotton@vmware.com>:
The problem seems to be with the boto python library. I am not really familiar with this but I have seen this is the last – we may need to update the requirements again to exclude a specific version. Yeah, it's bad boto update again: -boto==2.13.3 +boto==2.14.0
Let's cap it as a quickfix, it's stable/grizzly freeze today so we need gates fixed asap!
Cheers, Alan
Gary just proposed: https://review.openstack.org/#/c/50985/1 I'm in favor of this approach rather than adding a strict version requirement to boto in stable. IMHO, adding such an explicit requirement in a stable update is a bad idea that should be added to the stable branch blacklist. Adam
participants (5)
-
Adam Gandelman
-
Alan Pevec
-
Gary Kotton
-
Sean Dague
-
Thierry Carrez