The issue is mentioned to be observed after updating DNAC from 2.1.2.7 to 2.2.2.9. The same version is also mentioned in the context of the 3-node DNAC cluster where the issue is being observed.
The software version principally discussed in the documents is 2.2.2.9, which is the version of the DNAC being used by the customer when the issue is observed.