Description of problem: After rebooting, the /run/barbican folder which stores the pid is not recreated. This prevents barbican from starting until manually creating this folder and giving barbican permission. Version-Release number of selected component (if applicable): How reproducible: yum -y install centos-release-openstack-queens yum -y install centos-release-openstack-queens reboot /run/barbican folder no longer exists Steps to Reproduce: 1. yum -y install centos-release-openstack-queens 2. yum -y install centos-release-openstack-queens 3. reboot Actual results: /run/barbican folder no longer exists Expected results: /run/barbican should exist according to /usr/lib/systemd/system/openstack-barbican-api.service definition. Additional info: The /var/run folder (and /run) are TempFS and get wiped every reboot. Their contents are created again using package installed scripts in /usr/lib/tmpfiles.d/<package>.conf The openstack-barbican-api package needs to create a barbican.conf which would recreate the /var/run/barbican folder at boot time. Adding the following to a clean and up to date CentOS7 install fixes the issue for me: d /var/run/barbican 0755 barbican barbican -
step 2 for recreating the bug is supposed to be yum -y install openstack-barbican-api