Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

loginctl disable-linger runs even when disabled #301

Open
jcpunk opened this issue Dec 1, 2022 · 0 comments
Open

loginctl disable-linger runs even when disabled #301

jcpunk opened this issue Dec 1, 2022 · 0 comments

Comments

@jcpunk
Copy link
Contributor

jcpunk commented Dec 1, 2022

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet:7.17.0
  • Ruby:ruby-3.0.4-160.el9_0.x86_64
  • Distribution: AlmaLinux 9
  • Module version: 3.10.0

How to reproduce (e.g Puppet code you use)

stdlib::manage::create_resources:
  loginctl_user:
    sysoptmgmt:
      linger: disabled

What are you seeing

Every puppet run sets this to disabled even though it is already disabled. Seems like the check to see if it is already disabled isn't actually working....

What behaviour did you expect instead

Already disabled linger users shouldn't trigger a corrective action

Output log

Notice: /Stage[main]/Stdlib::Manage/Loginctl_user[sysoptmgmt]/linger: defined 'linger' as 'disabled' (corrective)

Any additional information you'd like to impart

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant