barbican_worker and barbican_keystone_listener have old version of python2-pyasn1 that causes them to fail

[Danil Zhigalin]

Package python2-pyasn1-0.1.9-7.el7.noarch in kolla queens centos containers barbican_worker and barbican_keystone_listener is of old version that causes them to fail with the following stack trace:

docker logs -f barbican_worker
+ sudo -E kolla_set_configs
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Copying service configuration files
INFO:__main__:Copying /var/lib/kolla/config_files/barbican.conf to /etc/barbican/barbican.conf
INFO:__main__:Setting permission for /etc/barbican/barbican.conf
INFO:__main__:Writing out command to execute
INFO:__main__:Setting permission for /var/log/kolla/barbican
++ cat /run_command
+ CMD=barbican-worker
+ ARGS=
+ [[ ! -n '' ]]
+ . kolla_extend_start
++ LOG_DIR=/var/log/kolla/barbican
++ [[ ! -d /var/log/kolla/barbican ]]
+++ stat -c %U:%G /var/log/kolla/barbican
++ [[ barbican:barbican != \b\a\r\b\i\c\a\n\:\k\o\l\l\a ]]
++ chown barbican:kolla /var/log/kolla/barbican
+++ stat -c %a /var/log/kolla/barbican
++ [[ 2755 != \7\5\5 ]]
++ chmod 755 /var/log/kolla/barbican
++ . /usr/local/bin/kolla_barbican_extend_start
+ echo 'Running command: '\''barbican-worker'\'''
Running command: 'barbican-worker'
+ exec barbican-worker
Traceback (most recent call last):
  File "/usr/bin/barbican-worker", line 6, in <module>
    from barbican.cmd.worker import main
  File "/usr/lib/python2.7/site-packages/barbican/cmd/worker.py", line 41, in <module>
    from barbican.queue import server
  File "/usr/lib/python2.7/site-packages/barbican/queue/server.py", line 36, in <module>
    from barbican.tasks import resources
  File "/usr/lib/python2.7/site-packages/barbican/tasks/resources.py", line 29, in <module>
    from barbican.tasks import certificate_resources as cert
  File "/usr/lib/python2.7/site-packages/barbican/tasks/certificate_resources.py", line 16, in <module>
    from ldap3.utils.dn import parse_dn
  File "/usr/lib/python2.7/site-packages/ldap3/__init__.py", line 138, in <module>
    from .core.connection import Connection
  File "/usr/lib/python2.7/site-packages/ldap3/core/connection.py", line 37, in <module>
    from ..extend import ExtendedOperationsRoot
  File "/usr/lib/python2.7/site-packages/ldap3/extend/__init__.py", line 45, in <module>
    from .standard.whoAmI import WhoAmI
  File "/usr/lib/python2.7/site-packages/ldap3/extend/standard/whoAmI.py", line 27, in <module>
    from pyasn1.type.univ import NoValue
ImportError: cannot import name NoValue

updating this package to a newer version, e.g. python2-pyasn1-0.3.2-2 solves this problem and this trace does not happen. This package is old in Centos repos, meaning that it needs to be added into container by some other means than just installing it from the repos.

[Mark Goddard (mgoddard)]

I think this is more of a problem of RDO than kolla.

[Launchpad Janitor (janitor)]

[Expired for kolla because there has been no activity for 60 days.]