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

Systemd unmask should run at the begin to allow the role to manage the units

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • rhel-system-roles
    • 0
    • QE ack, Dev ack
    • False
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Red Hat Enterprise Linux
    • None
    • Bug Fix
    • Hide
      .The `systemd` role unmasks and starts units in a single run

      Before this update, the `systemd` RHEL system role failed to enable and start services when units were masked because the role could not unmask the units first. As a result, users had to run the role twice. With this release, the `systemd` role correctly unmasks and starts services, eliminating the need for double runs.
      Show
      .The `systemd` role unmasks and starts units in a single run Before this update, the `systemd` RHEL system role failed to enable and start services when units were masked because the role could not unmask the units first. As a result, users had to run the role twice. With this release, the `systemd` role correctly unmasks and starts services, eliminating the need for double runs.
    • Done
    • Done
    • Done
    • Not Required
    • None

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

      We are using the role to unmask, enable and start, however, if the unit is masked, we cannot enable, start until umask.

      What is the impact of this issue to you?

      Customer is having to run the role twice, first to umaks, secondly to enable/start the services

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

      rhel-system-roles-1.88.9-0.1.el9_5.noarch

      How reproducible is this bug?:

      Mask some units and run the role to with the following variables.

       

        roles:
          - role: rhel-system-roles.systemd
            vars:
              systemd_unmasked_units:
                - autofs.service
                - rpcbind.service
                - rpcbind.socket
              systemd_enabled_units:
                - autofs.service
                - rpcbind.service
              systemd_started_units:
                - autofs.service
                - rpcbind.service 

      Steps to reproduce

       

      1. mask autofs or rpcbind
      2. run the role

      Expected results

      We should be able to umask the units previous to start.

      Actual results

      It fails to start if we do not umask it previously.

              rmeggins@redhat.com Richard Megginson
              rhn-support-rbertolj Rudnei Bertol Junior
              Richard Megginson Richard Megginson
              David Jez David Jez
              Valentina Ashirova Valentina Ashirova
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: