The barbican user and group were missing from the setup files.
Adding it ensures consistent uid/gid values across nodes, where
filesystems may be shared.
Adding it also ensures uid/gid exists when barbican is installed.
This will fix sanity issues due to arbitrary rpm ordering during
initial system installation.
openstack-barbican-common has a scriptlet that sets up
barbican user and group if they do not exist, through
shadow-utils.
The shadow-utils requirement is set for openstack-barbican
rather than openstack-barbican-common or python-barbican.
Alternatively the src rpm could be patched, but this would add
source code patching debt, and still not resolve the filesystem
consistency issue.
Change-Id: I67b7c292e4a3356335df6619648284e028625fe6
Closes-Bug: 1849671
Signed-off-by: Al Bailey <Al.Bailey@windriver.com>
4341591423