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

Windows component DHCP Server service after an upgrade

    XMLWordPrintable

    Details

    • Template:
    • 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:
      Hide
      When performing a puppet agent upgrade, sometimes Windows Network Components are restared. This restart is caused becase nssm.exe was registerd as the EventMessageFile that gets loaded and locked into svchost.exe when viewing events raised by pxp-agent.
      The puppet agent upgrade tries to replace nssm.exe, but fails as it is loaded, and the only way to unload it is to restart windows components like DHCP Client.

      This fix removes the usage of nssm.exe for events and replaces it with EventCreate.exe when generating event messages, so now the EventCreate.exe will get loaded and locked by svchost.exe when viewing puppet events.
      This will no longer interfere with the puppet agent upgrade, so no windows component will get restarted.
      Show
      When performing a puppet agent upgrade, sometimes Windows Network Components are restared. This restart is caused becase nssm.exe was registerd as the EventMessageFile that gets loaded and locked into svchost.exe when viewing events raised by pxp-agent. The puppet agent upgrade tries to replace nssm.exe, but fails as it is loaded, and the only way to unload it is to restart windows components like DHCP Client. This fix removes the usage of nssm.exe for events and replaces it with EventCreate.exe when generating event messages, so now the EventCreate.exe will get loaded and locked by svchost.exe when viewing puppet events. This will no longer interfere with the puppet agent upgrade, so no windows component will get restarted.
    • QA Risk Assessment:
      Needs Assessment

      Description

      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.

       

        Attachments

          Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. PA-2701 Windows Network Components restart following Puppet agent Upgrade

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. MODULES-10818 puppet_agent : upgrading windows agent from 5.5.16 to 5.5.21 is failing with `ScriptHalted` error.

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. PA-3261 msi_move_locked_files property does not function upgrading Puppet agent from 5.5.14 to 5.5.20 (using Forge module)

          • Medium - Has the potential to affect progress.
          • Closed

          Task - A task that needs to be done. MODULES-10694 puppet_agent module should detect of nssm.exe is loaded into svchost

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Resolved

          Task - A task that needs to be done. PA-3263 Puppet Agent should ignore nssm.exe during an upgrade

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Resolved
          mentioned in

          Page Loading...

          Page Loading...

            Activity

              People

              Assignee:
              gheorghe.popescu Gheorghe Popescu
              Reporter:
              selvakumar.subburaj Selvakumar Azhagarsami
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support