John Griffith wrote: > I ran into an issue with Cinder the other week and it turned out it was > due to some conflicts with keystoneclient version. > > Long story short, the issue is that Cinder did the straight sync over > from the common-requirements file which placed an upper bound on > keystoneclient. It looks like other projects haven't done this and most > don't have the upper bound set. There are other mismatches however I > was only working on the one. > > I was going to log a bug against all the projects to do a sync of > requirements and test-requirments to get us all aligned. Before doing > so I thought I should check to see if there are known cases where the > settings in the common requirements file don't work for you currently? > I understand that horizon for example has some upcoming requirements for > keystonclient 0.3.0 so that could be a reason to update the req's file > first. > > Anyway if there are issues that folks already know about then I suppose > the answer is to get that fixed up first and then we can start working > towards getting all of the projects in sync. > > Thoughts, agreement, disagreement etc?
That sounds sane to me. You should push that early this week or wait after havana-2 publication though... since late dep changes have a high regression potential. Regards, -- Thierry Carrez (ttx) _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
