Re: [openstack-dev] [telemetry] Gate broken by openstack/requirements

2016-05-16 Thread Yuriy Taraday
>From IRC discussion I got that Telemetry team opted out of using global-requirements and upper-constraints altogether a while ago, so I understand why my proposal is not an option. On Mon, May 16, 2016 at 3:33 PM Yuriy Taraday wrote: > Isn't it just a matter of updating upper-constraints? It se

Re: [openstack-dev] [telemetry] Gate broken by openstack/requirements

2016-05-16 Thread Yuriy Taraday
Isn't it just a matter of updating upper-constraints? It seems latest generate-constraints CR [0] that includes this update is stuck for some reason so why not just update gnocchiclient in upper-constraints separately instead of dropping it from globar-requirements guard altogether? Later seems lik

Re: [openstack-dev] [telemetry] Gate broken by openstack/requirements

2016-05-16 Thread Davanum Srinivas
Julien, Cleaned up g-r/u-c in: https://review.openstack.org/#/c/316356/ -- Dims On Mon, May 16, 2016 at 6:43 AM, Julien Danjou wrote: > Hi folks, > > Just to let you know that one of our telemetry test job is broken > because of openstack/requirements capping gnocchiclient to 2.3.0 (for no > go

[openstack-dev] [telemetry] Gate broken by openstack/requirements

2016-05-16 Thread Julien Danjou
Hi folks, Just to let you know that one of our telemetry test job is broken because of openstack/requirements capping gnocchiclient to 2.3.0 (for no good reason obviously). Until this cap is moved to 2.3.1 (that fixes the gnocchiclient bug we're hitting) or gnocchiclient is removed from openstack