Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-9604

Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • None
    • None
    • None
    • None
    • Night's Watch
    • Customer Feedback
    • Reviewed
    • 34399
    • 1
    • Needs Assessment

    Description

      **This is spin-off ticket of PUP-7326.

      Steps to reproduce:

      1. Setup Active Directory with Domain Functional level 2016
      2. Spin up a Win2012R2 machine and connect to AD
      3. Create a test user (e.q. testadmin1) in Active Directory
      4. Add testadmin1 user to local administrators group in Win2012R2
      5. Delete testadmin1 user in AD
      6. Run

        puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }"

      Or

      1. Setup Active Directory with Domain Functional level 2012 R2
      2. Spin up a Win2016 machine and connect to AD
      3. Create a test user (e.q. testadmin1) in Active Directory
      4. Add testadmin1 user to local administrators group in Win2016
      5. Delete testadmin1 user in AD
      6. Run

        puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }

      Puppet apply returns error below

      Note the error occurs only on Windows client machine with condition its OS version is different with the AD Domain Functional level. E.q. Client OS Win2012R connected to AD Domain Functional level 2016 or Client OS Win2016 connected to AD Domain Functional level 2012R2.

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              halim.wijaya Halim Wijaya
              Votes:
              4 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support