Provision conflict error in Cisco DNAC

[riah]

While provision a switch to the fabric site I came across this issue of the provision conflict. Although the provision template is the same used by the other switches but they had no issue.

Attached is the error which pops up in the DNAC.  

In order to fix this issue I  deprovisioned the switch, resynched it but still it shows the same issue. Is it some sort of a bug ? 

Thank you.

[Preston Chilcote]

Look for the failed Provision task in Activities->Task (from main menu) and click "See Details".  Keep drilling down on the Failed stages until you get the specifics of the failure.  Most often it's related to one of the commands in the template and this procedure will show you exactly which command the network device complained about.

[riah]

The switch do get provisioned successfully 

once I change the focus to the template its shows that there is a conflict. 

and then i view configuration for this particular switch it highlights following lines.

vtp mode transparent
vtp domain xyz.ad

The are many devices which are running with the same template and they didn't encounter any issue. Is there a way to fix this issue? 

[Preston Chilcote]

"and then i view configuration for this particular switch it highlights following lines."

A screen capture of this page you mentioned would be helpful

[riah]

Below  is the config for that switch: 

[Preston Chilcote]

Does it give a hint if you hover over the warning sign on line 44?

[riah]

Yes, it does say Conflicts with Intent. 

[p11l]

I get the same error but with the line of the interface name. "interface TwoGigabitEthernet1/0/1" is marked as a conflict status.

The Template with even these line are written down to the interface, therese is'nt the problem.

But Catalyst Center give me the same output like in the posts above.

Does anyone can help to solve the issue?

flow record SW_FLOW_RECORD
  description NetFlow record format to send to SW
   match ipv4 version
   match ipv4 protocol
   match application name
   match connection client ipv4 address
   match connection client transport port
   match connection server ipv4 address
   match connection server transport port
   match flow observation point
   collect flow direction
   collect connection initiator
   collect connection new-connections
   collect connection client counter packets long
   collect connection client counter bytes network long
   collect connection server counter packets long
   collect connection server counter bytes network long
   collect timestamp absolute first
   collect timestamp absolute last

flow exporter NETFLOW_TO_SW_FC
  description Export NetFlow to SW FC
  destination [IP]
  source Loopback0
  transport udp 6007
  template data timeout 30
  option interface-table
  option exporter-stats
  option application-table
  option cts-sgt-table

flow monitor IPv4_NETFLOW
  record SW_FLOW_RECORD
  exporter NETFLOW_TO_SW_FC
  cache timeout active 60
  cache timeout update 60
  cache timeout inactive 45

et-analytics
  ip flow-export destination [IP] 6007
  inactive-timeout 45



interface TwoGigabitEthernet1/0/1
  ip nbar protocol-discovery
  ip flow monitor IPv4_NETFLOW input
  et-analytics enable