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

fix: Do not restart logind unless absolutely necessary

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: Generate New Ti...SWIFT: POC ConversionSync 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
      .Podman role does not fail with `UNREACHABLE` error

      Previously, the `podman` role did not wait enough for the user state to be in `closing` status when disabling linger for non-root users. The `podman` role then restarted `systemd-logind` to force it to cancel. On some systems, this started a timer that killed the session for root, causing the `sshd` session to terminate and the Ansible play to fail with `UNREACHABLE` error.

      With this fix, the system now waits much longer for users to be in the `closing` state, and only restarts `logind` if absolutely necessary. As a result, the role does not fail with `UNREACHABLE` error when removing resources.
      Show
      .Podman role does not fail with `UNREACHABLE` error Previously, the `podman` role did not wait enough for the user state to be in `closing` status when disabling linger for non-root users. The `podman` role then restarted `systemd-logind` to force it to cancel. On some systems, this started a timer that killed the session for root, causing the `sshd` session to terminate and the Ansible play to fail with `UNREACHABLE` error. With this fix, the system now waits much longer for users to be in the `closing` state, and only restarts `logind` if absolutely necessary. As a result, the role does not fail with `UNREACHABLE` error when removing resources.
    • Done
    • Done
    • Done
    • Not Required
    • None

      Cause: When disabling linger for non-root users, we did not wait long
      enough for the user state to be "closing". Then we restart
      systemd-logind to force linger to be cancelled.

      Consequence: On some systems, this starts a timer which will kill
      the session for root, causing the sshd session to be terminated,
      and the Ansible play to fail with `UNREACHABLE`.

      Fix: Wait much longer for the user linger to be cancelled, and only
      restart logind if absolutely necessary.

      Result: The role does not fail with `UNREACHABLE` errors when
      removing resources.

      Signed-off-by: Rich Megginson <rmeggins@redhat.com>

              rmeggins@redhat.com Richard Megginson
              rmeggins@redhat.com Richard Megginson
              Richard Megginson Richard Megginson
              David Jez David Jez
              Mugdha Soni Mugdha Soni
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: