[PA-1850] PXP fails to start after a Puppet Agent upgrade with SSL library errors - Puppet Tickets

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: puppet-agent 1.10.12, puppet-agent 5.3.6, puppet-agent 5.5.0
Component/s: Windows
Labels:
- customer-escalation
- manage-service
Environment:

TEST_TARGET=windows2008r2-64a
SUITE_VERSION=1.6.2.135.g8a48f21
SUITE_COMMIT=8a48f210f6901be0edba16eb49c1bfbfb07d338b

CS Priority:
Major
CS Frequency:
3 - 25-50% of Customers
CS Severity:
4 - Major
CS Business Value:
5 - $$$$$$
CS Impact:

Hide
If openssl libraries(of a different version than ours) are installed in the Windows system folders then the PXP agent will fail to start. The workaround is to is to reorder the path or remove or replace those library files in other locations.

This has come up with 5-10x in the last few weeks, a very high rate of occurrence.

Show
If openssl libraries(of a different version than ours) are installed in the Windows system folders then the PXP agent will fail to start. The workaround is to is to reorder the path or remove or replace those library files in other locations. This has come up with 5-10x in the last few weeks, a very high rate of occurrence.

Release Notes:
Bug Fix
Release Notes Summary:
All of the .dll files that the pxp-agent binary depends on are now copied over to the executable's directory (the <pxp-agent-install-root>/bin directory).

This issue was created from ~~PUP-6702~~

—

Steps to reproduce;
Unknown at this stage. Looks like it could be made to happen after the puppet_agent module does an agent upgrade.

relates to

PUP-6702 Windows service in Paused state cannot be managed