pip >= 10.0.0b2 drops support for --allow-unverified

[Ryan Beisner]

Pip just revved up past 10.0, and since pip >= 10.0.0b2 drops support for --allow-unverified, there are several things affected.

The unit, lint tests for OpenStack charms are now failing, with the dev/test gate completely blocked.

Inspection of tox.ini files across the charms reveals that python-apt was previously and explicitly added with --allow-unverified. The python-apt pip package used to be needed for some unit tests, which arguably weren't mocked appropriately anyway. Those appear to be resolved, and if they are not, they should be.

The python-apt pip package needs --allow-unverified because of the download url as listed here:

https://pypi.python.org/pypi/python-apt/

So, short of python-apt doing a full pypi distribution --or-- all users and CI expressly permitting launchpad ip addresses and hostnames via global pip config, the python-apt pip package is unusable.

But to repeat: we think we don't need it in this case.

[Ryan Beisner (1chb1n)]

See:

https://github.com/juju/charm-helpers/issues/143

[Ryan Beisner (1chb1n)]

This docfix (trivial) illustrates how the gate is currently bust:

https://review.openstack.org/#/c/558239/

[Ryan Beisner (1chb1n)]

Some additional unnecessary and accidental occurrences of this flag in use:

https://github.com/openstack-charmers/charm-test-infra/pull/13

https://github.com/openstack-charmers/bot-control/pull/62

[Ryan Beisner (1chb1n)]

This batch of gerrit reviews represents the approach to resolve and unblock the charm test gates:

https://review.openstack.org/#/q/topic:update-tox-files+(status:open+OR+status:merged)

[Ryan Beisner (1chb1n)]

Fixes for this issue have now landed in master for all OpenStack Charms, except the tempest charm, which is delayed due to an unrelated error @ charm-tempest/master.

https://bugs.launchpad.net/charm-tempest/+bug/1760949

I've selectively raised stable/18.02 backports for charms which are likely to have other stable backports soon.

The remainder of the charms will need to have stable/18.02 backports of this --allow-unverified fix, before any other backports will be possible to those charms.