Symptom
This is a sister bug for CSCvs10266 Cat9K/16.11.1c/SDA- Ingress QOS Service Policy not applying to interface.
Scope of this new bug-
With access-session sticky, we are still seeing same issue. Service-policy fails to get installed manually/automatically, if the specific order of provisioning is followed. Shut/no shut on port will not make a difference. The issue is not seen on ports, where ISE never pushed any session attribute/template name. if we remove the sticky and clear the access-session, it installs the policy.
As per current behaviour, if template application fails, smd is not notified. So, smd is not aware of success or failure of template application. Since sticky config is there, when new session comes up, smd assumes that template is already bond to the interface and does not ask template code to apply the template. So, at this point of time template is not getting applied.
Conditions
Step 1- It is important that fabric is provisioned first with endpoints attached to edge switch with QOS policy template name applied through ISE.
Step-2 Application policy is not pushed yet, so actual ingress QOS policy-map under that template does not exist on the device yet.
Step-3 After provisioning application policy, when QOS policy configuration is pushed, then policy-map fails to get installed on interface.
Before application policy is provisioned, the interface template is referencing a service policy that does not exist on the switch,
Workaround
Remove the sticky and clear the access-session, it then installs the policy.
Further Problem Description
The issue is not seen on ports, where ISE never pushed any session attribute/template name.
