Skip to content
Snippets Groups Projects
Select Git revision
  • ca5496918a699863412173fad281fe49f8a4ef0a
  • master default protected
  • v1.15.0
  • v1.14.7
  • v1.14.6
  • v1.14.5
  • v1.14.4
  • v1.14.3
  • v1.14.2
  • v1.14.1
  • v1.14.0
  • v1.13.2
  • v1.13.1
  • v1.13.0
  • v1.12.1
  • v1.12.0
  • v1.11.1
  • v1.11.0
  • v1.10.0
  • v1.9.2
  • v1.9.1
  • v1.9.0
22 results

plugins

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Rafael Guterres Jeffman authored
    If a playbook to ensure the existence of a user contains 'random:false'
    and 'update_password: always' is executed twice, the second execution
    will raise an exception due to "No modifications to perform", as there
    is actually nothing to modify.
    
    The fix for the issue is to remove 'random' if it is not set to true, as
    setting it to 'false' would have no effect on the user object.
    
    Related: https://issues.redhat.com/browse/RHEL-4934
    ca549691
    History
    Name Last commit Last update
    ..