This issue occurs due to a change in Pulse One appliance registration URL
- api.<customerdomain>.com (Prior to Pulse One 2.0.1743)
- <hostname>.<customerdomain>.com" (Pulse One 2.0.1743 and above)
The issue will only occur if the Pulse One (On-Premise) appliances are clustered prior to the upgrade and after the Active node failed over to the Passive node performed either automatically or manually. This does not impact stand-alone Pulse One (On-Premise) environments.