Details
-
Bug
-
Status: Closed
-
Medium
-
Resolution: Duplicate
-
puppet-agent 5.5.14
-
Puppet environment: 5.5.14
Windows OS verisons: 2012R2, 2016, 2019
-
-
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.