Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-61238

sanlock user is created too late

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • rhel-10.0
    • rhel-10.0
    • sanlock
    • None
    • sanlock-3.9.5-4.el10
    • None
    • Moderate
    • rhel-sst-logical-storage
    • ssg_filesystems_storage_and_HA
    • 21
    • 23
    • 5
    • QE ack
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • All
    • None

      What were you trying to do that didn't work?

      Installability gating CI test for libvirt failed on RHEL-10.0 complaining /var/lib/libvirt/sanlock is not owned by sanlock group even though the spec files says so. This happens because sanlock group does not exist at the time the directory is created:

      Running transaction
  Preparing        :                                                        1/1 
  Installing       : sanlock-lib-3.9.4-2.el10.x86_64                        1/5 
  Running scriptlet: sanlock-3.9.4-2.el10.x86_64                            2/5 
  Installing       : sanlock-3.9.4-2.el10.x86_64                            2/5 
warning: user sanlock does not exist - using root
warning: group sanlock does not exist - using root

  Running scriptlet: sanlock-3.9.4-2.el10.x86_64                            2/5 
  Installing       : augeas-libs-1.14.1-1.el10.x86_64                       3/5 
  Installing       : augeas-1.14.1-1.el10.x86_64                            4/5 
  Installing       : libvirt-daemon-plugin-sanlock-10.8.0-1.el10.x86_64     5/5 
warning: group sanlock does not exist - using root

  Running scriptlet: libvirt-daemon-plugin-sanlock-10.8.0-1.el10.x86_64     5/5 
Creating group 'sanlock' with GID 179.
Creating user 'sanlock' (sanlock) with UID 179 and GID 179.

      This should be reproducible by just installing sanlock on a clean system as well.

      I suspect this is caused by RHEL-8273: before the change %pre script directly created both sanlock user and group, while now it creates them using systemd-sysusers and they don't seem to be created immediately. They are created when all packages are already installed with incorrect ownership of directories.

      Please provide the package NVR for which the bug is seen:

      sanlock-3.9.4-2.el10

      How reproducible is this bug?:

      100%

      Steps to reproduce

      On a clean system installation without sanlock

      1. dnf install sanlock

      Expected results

      /var/run/sanlock should be owned by sanlock:sanlock and installation should not report any warnings about missing sanlock user and group

      Actual results

        Installing       : sanlock-3.9.4-2.el10.x86_64                            2/5 
warning: user sanlock does not exist - using root
warning: group sanlock does not exist - using root

              cmarthal@redhat.com Corey Marthaler
              jdenemar@redhat.com Jiri Denemark
              David Teigland David Teigland
              Cluster QE Cluster QE
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: