Kolla rocky pulls requirements-master.tar.gz instead requirements-stable-rocky.tar.gz

[Andreas Merk]

Hi,

like in other bug reports: I had more and more unstable containers because of incompatible packets due to wrong upper limits in the pip installation process. After checking config.py I found that the requirements-master.tar.gz is pulled and not the rocky release.
The issues I have seen so far are:
python-zunclient (master = 3.0.0) is incompatible with the rocky zun-api
oslo.messaging (master = 9.0.1) produces an "ERROR oslo_service.service MessageDeliveryFailure: Unable to connect to AMQP server on xxx.xxx.xxx.xxx:5672 after inf tries: Connection.open: (530) NOT_ALLOWED - access to vhost 'None' refused for user 'openstack'" error.

manual downgrade of the both packages solved the situation, but since oslo.messaging is affecting so many elements a general fix is only a requirements downgrade.

[Andreas Merk (amerk)]

Fix: edit "kolla/common/config.py" and change:
requirements-master.tar.gz -> requirements-stable-rocky.tar.gz

Temporary fix, edit "/etc/kolla/kolla-build.conf" add:
[openstack-base]
location = $tarballs_base/requirements/requirements-stable-rocky.tar.gz

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/610158

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/610158
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=9b1126aedd31cfda610a36257574354c6402159d
Submitter: Zuul
Branch: stable/rocky

commit 9b1126aedd31cfda610a36257574354c6402159d
Author: Eduardo Gonzalez <email address hidden>
Date: Fri Oct 12 22:29:06 2018 +0200

    Use rocky requirements in rocky source builds

    Requirements is pointing to master which causes dependency conflicts.
    Closes-Bug: #1797629

    Change-Id: Ib47f1f6fc793d047f665e811a88fa530ab562e24

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla 7.0.0.0rc3 release candidate.