Comment 2 for bug 1531612

This is in the midst of being fixed upstream in pbr. It looks like it'll land soon in stable/kilo.

Here's the upstream bug: https://bugs.launchpad.net/pbr/+bug/1375048
And here's the upstream patch review: https://review.openstack.org/#/c/263928/

I'm not sure why we started hitting this all of a sudden. I couldn't find a recent commit in stable/kilo.

To get the fix is a little tricky at the moment, unfortunately, because the charms perform shallow git clones (for performance), and therefore the pip version of packages installed from git become 0.0.0.

To pick up the fix in the charms, I cherry-picked the upstream fix from the patch review above to my own repo (git://github.com/coreycb/pbr), and added it to neutron-kilo.yaml as follows:

repositories:
  - {name: requirements,
     repository: 'git://github.com/openstack/requirements',
     branch: stable/kilo}
  - {name: pbr,
     repository: 'git://github.com/coreycb/pbr',
     branch: stable/kilo}
  - {name: neutron-fwaas,
     repository: 'git://github.com/openstack/neutron-fwaas',
     branch: stable/kilo}
  - {name: neutron-lbaas,
     repository: 'git://github.com/openstack/neutron-lbaas',
     branch: stable/kilo}
  - {name: neutron-vpnaas,
     repository: 'git://github.com/openstack/neutron-vpnaas',
     branch: stable/kilo}
  - {name: neutron,
     repository: 'git://github.com/openstack/neutron',
     branch: stable/kilo}
directory: /mnt/openstack-git
http_proxy: http://squid.internal:3128
https_proxy: http://squid.internal:3128

This *should* fix the issue and run with the new pbr, *however* the charms do shallow git clones, so the version of the pip installed pbr results in 0.0.0, and the ensuing install of neutron-api re-installs the bad pbr because it requires a higher version that 0.0.0.

For this bug I want to add an option to the openstack-origin-git yaml for all of the charms to enable full git clones, which will allow pip to see the real version of pbr in this situation.