-
Type:
New Feature
-
Status: Resolved
-
Priority:
Normal
-
Resolution: Fixed
-
Affects Version/s: puppet-agent 6.14.0
-
Fix Version/s: puppet-agent 5.5.20, puppet-agent 6.15.0
-
Component/s: None
-
Labels:
-
Template:customfield_10700 353391
-
Team:Night's Watch
-
Story Points:5
-
Sprint:NW - 2020-04-15
-
Zendesk Ticket IDs:38661,39128,39298
-
Zendesk Ticket Count:3
-
Release Notes:Bug Fix
-
Release Notes Summary:
-
QA Risk Assessment:Needs Assessment
Recently upgraded the Puppet agent on Windows Server 2016 to 6.14.0 after upgrading the Puppet master to 2019.5.0. It appears the Puppet Agent upgrade is still continuing to restart the DHCP Server service after an upgrade.
- relates to
-
PA-2701 Windows Network Components restart following Puppet agent Upgrade
-
- Resolved
-
-
MODULES-10818 puppet_agent : upgrading windows agent from 5.5.16 to 5.5.21 is failing with `ScriptHalted` error.
-
- Resolved
-
-
PA-3261 msi_move_locked_files property does not function upgrading Puppet agent from 5.5.14 to 5.5.20 (using Forge module)
-
- Closed
-
-
MODULES-10694 puppet_agent module should detect of nssm.exe is loaded into svchost
-
- Resolved
-
-
PA-3263 Puppet Agent should ignore nssm.exe during an upgrade
-
- Resolved
-