Sean, I'm looking into this and have proposed https://review.openstack.org/#/c/133958/ as an interim measure. As soon as the trove gate passes I'll try and get a couple of other votes and have that change merged. Dims and I had a short chat on IRC and weren't able to come up with a quick solution to the problem; I think the change you identified needs to be reworked. More to come. -amrith | -----Original Message----- | From: Sean Dague [mailto:sean at dague.net] | Sent: Wednesday, November 12, 2014 9:22 AM | To: OpenStack Development Mailing List (not for usage questions) | Subject: Re: [openstack-dev] [all] python-troveclient keystone v3 support | breaking the world | | On 11/12/2014 09:17 AM, Sean Dague wrote: | > https://review.openstack.org/#/c/102315/ was merged yesterday, it | > creates a non functional trove python client. (There are currently no | > tests in python trove client to see if the commands even run after a | > code change). | > | > This means the trove devstack exercise can't work. | > | > Which means everything testing cells (oslo.db, nova, glance, heat, | > etc) can't pass any changes. | > | > I've proposed 2 fixes. | > | > 1) just delete the trove exercise so we can move forward - | > https://review.openstack.org/#/c/133930 - that will need to be | > backported as well. | > | > 2) revert the troveclient change - | > https://review.openstack.org/#/c/102315/ (which I think also should be | > done) and not repropose until there are actual tests in the | > troveclient tree to prevent this kind of breakage. | > | > -Sean | > | | The bug in question - http://status.openstack.org/elastic-recheck/#1391840 | | -Sean | | -- | Sean Dague | http://dague.net | | _______________________________________________ | OpenStack-dev mailing list | OpenStack-dev at lists.openstack.org | http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev