ATTWorkflowDriver Service Instances status message remains same as ONU not found in whitelist after pushing ONU Whitelist with wrong PON port

"ATTWorkflowDriver Service Instances" status message remains same as "ONU not found in whitelist" after pushing ONU Whitelist with wrong PON port. 

Steps to Reproduce:

1. Bring up the SEBA PoD along with ONU and OLT connected, but do not configure ONU in whilelist yet. Also, Rcord subscriber model entry can be omitted.
2. ONU should be detected and visible in XOS GUI but in Disabled state. A ATTWorkflowDriverServiceInstance entry would also be visible but in Disabled state and Status message as "ONU not found in whitelist".
3. Now push TOSCA with ONU Whitelist and Rcord subscriber model. But, put wrong PON port (different than on which ONU is connected to OLT) in ONU Whitelist entry.
4. The ATTWorkflowDriverServiceInstance would remain in Disabled state but Status message should change to "ONU activated in wrong location".
5. Status message remains the same as "ONU not found in whitelist".

Please note if we manually update the PON port to an Invalid one in XOS GUI directly (after everything is up), the XOS works fine to disable the ONU and change the status message to "ONU activated in wrong location".