Here's the bug for Glance: https://bugs.launchpad.net/glance/+bug/1298039
----- Original Message ----- From: "Clark Boylan" <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Sent: Wednesday, March 26, 2014 4:04:12 PM Subject: Re: [openstack-dev] [depfreeze] Exception: limit psutil to <2.0.0 On Wed, Mar 26, 2014 at 12:32 PM, Solly Ross <[email protected]> wrote: > What bug tracker should I file under? I tried filing one under the openstack > common infrastructure tracker, > but was told that it wasn't the correct place to file such a bug. > > Best Regards, > Solly Ross > > ----- Original Message ----- > From: "Sean Dague" <[email protected]> > To: "OpenStack Development Mailing List (not for usage questions)" > <[email protected]> > Sent: Wednesday, March 26, 2014 3:28:32 PM > Subject: Re: [openstack-dev] [depfreeze] Exception: limit psutil to <2.0.0 > > Where is the RC bug tracking this? > > If it's that bad, we really need to be explicit about this with a > critical bug at this stage of the release. > > -Sean > > On 03/26/2014 01:14 PM, Solly Ross wrote: >> Code which breaks: >> >> Glance's mutliprocessing tests will break (the reason we should limit it >> now). >> For the future, people attempting to use psutil will have no clear version >> target >> (Either they use 1.x and break with the people who install the latest >> version from pip, >> of they use 2.0.0 and break with everything that doesn't use the latest >> version). >> >> psutil's API is extremely unstable -- it has undergone major revisions going >> from 0.x to 1.x, and now >> 1.x to 2.0.0. Limiting psutil explicitly to a single major version (it was >> more or less implicitly limited >> before, since there was no version major version above 1) ensures that the >> requirements.txt file actually >> indicates what is necessary to use OpenStack. >> >> The alternative option would be to update the glance tests, but my concern >> is that 2.0.0 is not available >> from the package managers of most distros yet. >> >> Best Regards, >> Solly Ross >> >> ----- Original Message ----- >> From: "Sean Dague" <[email protected]> >> To: "OpenStack Development Mailing List (not for usage questions)" >> <[email protected]> >> Sent: Wednesday, March 26, 2014 10:39:41 AM >> Subject: Re: [openstack-dev] [depfreeze] Exception: limit psutil to <2.0.0 >> >> On 03/26/2014 10:30 AM, Solly Ross wrote: >>> Hi, >>> I currently have a patch up for review >>> (https://review.openstack.org/#/c/81373/) to limit psutil be <2.0.0. >>> 2.0.0 just came out a couple weeks ago, and breaks the API in a major way. >>> Until we can port our code to the >>> latest version, I suggest we limit the version of psutil to 1.x (currently >>> there's a lower bound in the 1.x >>> range, just not an upper bound). >> >> Which code will be broken by this if it's not done? Is there an RC bug >> tracking it? >> >> -Sean >> > > > -- > Sean Dague > Samsung Research America > [email protected] / [email protected] > http://dague.net > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev You should file the bug against the projects that don't work with latest psutil. The bug is in particular projects being incompatible with a dependency and belongs to those projects. Clark _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
