It would probably help if we'd be able to get to the containers which are used in CI and check the RPM versions there. Note that the containers in CI have the "updated" part of name *later* than what i have in my working local env, yet they still hit the problem. There might be something fishy in how we build/update containers for CI...
The working container has:
()[mistral@ af2c5169e7cf /]$ rpm -qa | grep tripleo-common tripleo- common- container- base-9. 2.1-0.201808141 23159.042f43d. el7.noarch tripleo- common- containers- 9.2.1-0. 20180814123159. 042f43d. el7.noarch tripleo- common- 9.2.1-0. 20180814123159. 042f43d. el7.noarch tripleo- common- 9.2.1-0. 20180814123159. 042f43d. el7.noarch
openstack-
openstack-
openstack-
python2-
It would probably help if we'd be able to get to the containers which are used in CI and check the RPM versions there. Note that the containers in CI have the "updated" part of name *later* than what i have in my working local env, yet they still hit the problem. There might be something fishy in how we build/update containers for CI...