Uploaded image for project: 'Puppet Agent'
  1. Puppet Agent
  2. PA-3261

msi_move_locked_files property does not function upgrading Puppet agent from 5.5.14 to 5.5.20 (using Forge module)

    XMLWordPrintable

Details

    • Hide

      Discovering conclusively if it is possible to upgrade the Windows Puppet Agent from 5.5.14 to 6.1.4, whether in one step or more, without having causing a restart of the major Network Services stack on the OS.

      Show
      Discovering conclusively if it is possible to upgrade the Windows Puppet Agent from 5.5.14 to 6.1.4, whether in one step or more, without having causing a restart of the major Network Services stack on the OS.
    • Needs Assessment
    • Needs Assessment

    Description

      I've been working with my team to test a Puppet Agent upgrade to version 6.14, however we are trying to avoid a restart of the Windows Network services stack during the process and would like to make use of the Forge Puppet Agent property to get around this called 'msi_move_locked_files'. 

      We learned that a direct upgrade from 5.5.14 to 6.14 require the network services restart, but that if we could get to version 5.5.18-5.5.20 then upgrading to 6.14 would work and avoid the services restart.

      From what I have read of release notes and previous tickets, I should be able to set the 'msi_move_locked_files' property for an upgrade of 5.5.14 to 5.5.20 and also avoid a restart of network services, however in every test I have tried so far (Win2012R2, Win2016, Win2019) I see those services go down during the install.

       

      I would like to either find out if the versions I'm working with are not compatible, or if I should be able to upgrade to 5.5.20 without the network service restart but can't because an existing bug in the Forge Module or agent install for 5.5.20.

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              calebcox Caleb Cox
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support