On 13/11/15 02:49, Tony Breeds wrote: > On Thu, Nov 12, 2015 at 02:40:19PM +0100, Alan Pevec wrote: > >> AFAICT there are at least two blockers for 2014.2.4: - horizon - >> django_openstack_auth issue Tony mentions in >> https://review.openstack.org/172826 > > Horizon itself is fine BUT gets caught up in a mess of g-r updates. > The issue at hand is that DOA has an uncapped requirement on > oslo.config which then gets a 2.x release which doesn't contain the > oslo namespace. The *right* way to fix it is to cut a new relases > of DOA including the a g-r sync. > > There was some discussion on this in #openstack-stable: > http://eavesdrop.openstack.org/irclogs/%23openstack-stable/%23openstack-stable.2015-11-12.log.html > > An alternate hack would be: > https://review.openstack.org/#/c/244950/ but that seems fragile to > me. > Looking at http://logs.openstack.org/periodic-stable/periodic-horizon-python27-juno/1f5b282/console.html it's obvious, horizon falls down the same way like doa. Speaking of your "hacky" patch: yes and no. It makes the gate passing, it doesn't change the code itself. For most people, this will work fine. The right way to do it, would be to create a juno branch for doa and cap requirements there. How to do this? Is there a procedure to request a branch? Matthias