Uploaded image for project: 'Beaker'
  1. Beaker
  2. BKR-1478

beaker-pe should not backup the client_data directory

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Won't Do
    • None
    • None
    • None
    • None
    • Needs Assessment
    • Needs Assessment

    Description

      As described in BKR-943, beaker-pe will attempt to delete the client_data directory on Windows using a file resource with ensure=absent. However, it doesn't specify backup=false, so the deleted files are backed up the clientbucket directory. This creates the same issue that BKR-943 is trying to solve, where the contents of the directory are owned by Administrator but System does not have permission.

      We should either specify backup=false or just delete the directory using rm -rf.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. BKR-943 beaker-pe with frictionless windows agent does not apply inheritable SYSTEM permissions to directories it manages on Windows under certain circumstances

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. PUP-6729 NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. PUP-8939 Administrators are not able to run puppet agent when installed as SYSTEM in some cases

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              josh Josh Cooper
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support