Comment 10 for bug 1849671

Reviewed: https://review.opendev.org/691046
Committed: https://git.openstack.org/cgit/starlingx/integ/commit/?id=434159142363f319735caa87b0cc7fd6a1f71be1
Submitter: Zuul
Branch: master

commit 434159142363f319735caa87b0cc7fd6a1f71be1
Author: Al Bailey <email address hidden>
Date: Thu Oct 24 11:57:02 2019 -0500

    Ensure barbican user and group exist during installation

    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 <email address hidden>