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

Upgrading Puppet Agent on Windows when MCO is configured and running restarts the network stack - can cause issues with Exchange servers

    XMLWordPrintable

    Details

    • Template:
    • Acceptance Criteria:
      Hide

      puppetres.dll remains after upgrade or uninstall of puppet-agent on Windows

      Show
      puppetres.dll remains after upgrade or uninstall of puppet-agent on Windows
    • Team:
      Agent
    • Story Points:
      3
    • Sprint:
      AP 2017-02-08, AP 2017-02-22, AP 2017-03-08
    • CS Priority:
      Reviewed
    • QA Risk Assessment:
      No Action
    • QA Risk Assessment Reason:
      Tested in PA-768

      Description

      During an upgrade of the Puppet agent on Windows servers, when MCO is configured and running it will always cause IP Helper, DHCP and other network services to shut down and restart as part of the upgrade.

      Details

      There is no direct dependency on those services in Puppet agent or any of its components, they are chosen by the Microsoft MsiExec Restart Manager to restart as part of the upgrade (which means this technically falls into Microsoft's area). If we determine WHY Restart Manager is choosing to restart the network stack, we can possibly look at shutting some stuff down prior to allowing Restart Manager to make its determinations - it's a slippery slope I know. We've discussed similar issues and did some work in PA-65, which is a similar issue.

      Implications

      This is particularly troublesome for Exchange boxes because Exchange can be extremely finicky and if the network goes down, even for periods less than a second (possibly milliseconds), it goes into failover mode which can wreak all kinds of havoc.

      Options

      • Option 1 - Document this as upgrade considerations so that it becomes a well-known issue for folks upgrading. (We should probably do this anyway). That way there are no surprises that this technical limitation exists.
      • Option 2 - See what workarounds we can find to overcome this limitation. We've done some work to look at possibilities with PA-65, but none of those options were any good as a manageable path forward.

        Attachments

        1. get-eventlog-puppetres.png
          get-eventlog-puppetres.png
          133 kB
        2. listdlls-puppetres.png
          listdlls-puppetres.png
          147 kB
        3. msi-interactive.png
          msi-interactive.png
          55 kB
        4. no-puppetres.png
          no-puppetres.png
          55 kB
        5. puppet_agent_windows_preflight.zip
          2 kB
        6. puppetres-procmon.png
          puppetres-procmon.png
          57 kB
        7. rammap-post-load.png
          rammap-post-load.png
          61 kB
        8. rammp-empty-work.png
          rammp-empty-work.png
          30 kB
        9. screenshot-1.png
          screenshot-1.png
          51 kB
        10. some-puppetres.png
          some-puppetres.png
          56 kB

          Issue Links

            Activity

              People

              Assignee:
              ethan Ethan Brown
              Reporter:
              rob Rob Reynolds
              Votes:
              3 Vote for this issue
              Watchers:
              17 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support