Controller Services impacted when applying specific patches on v22.1.3

Products

• VMware

Issue/Introduction

An issue has been identified in patch releases 22.1.3-2p2, 22.1.3-2p3, and 22.1.3-2p4 that may result in some Controller services being impacted immediately after applying these patches.

In some cases, there may be some service impact due to the DNS resolution on the Controller being non-operational until the Controller can be rebooted.

Resolution

1. The issue will be encountered when installing or rolling-back to the patches 22.1.3-2p2, 22.1.3-2p3 or 22.1.3-2p4. It is therefore recommended not to apply these patches and instead to apply 22.1.3-2p5.
2. The issue will also be encountered when applying the 22.1.3-2p5 patch to a system that is already running the 22.1.3-2p2, 22.1.3-2p3 or 22.1.3-2p4 patch level.
   • In this case, it is recommended to use Flexible Upgrade to apply the 22.1.3-2p5 patch to the Controller only first, then reboot the Controller/Cluster to remediate the issue, then apply the 22.1.3-2p5 patch to Service Engine Groups.
3. The issue will not be encountered when applying the 22.1.3-2p5 patch to a system running 22.1.3 (base release) or 22.1.3-2p1
4. The issue will not be encountered when upgrading to 22.1.3-2p5 directly from an earlier release using the upgrade+patch operation.