Plugin does not send ROLE_REQUEST when cluster services are stopped but device is not disconnected

If cluster services are stopped on a member (now acting as non-owner) for an openflow device no role request is sent. The next time the member becomes the owner for that device it will not send the set role request to become master because the last known role was master.

2017-09-15 02:57:55,067 | INFO | lt-dispatcher-46 | DeviceContextImpl | 290 - org.opendaylight.openflowplugin.impl - 0.3.3.Boron-SR3 | This controller instance is now acting as a non-owner for node openflow:2030001

...

2017-09-16 12:17:30,550 | INFO | ult-dispatcher-2 | LifecycleServiceImpl | 290 - org.opendaylight.openflowplugin.impl - 0.3.3.Boron-SR3 | Starting clustering MASTER services for node openflow:2030001

...

2017-09-16 12:17:30,611 | INFO | ult-dispatcher-2 | SalRoleServiceImpl | 290 - org.opendaylight.openflowplugin.impl - 0.3.3.Boron-SR3 | SetRole called with input:SetRoleInput [_controllerRole=BECOMEMASTER, _node=NodeRef [_value=KeyedInstanceIdentifier

{targetType=interface org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node, path=[org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.Nodes, org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node[key=NodeKey [_id=Uri [_value=openflow:2030001]]]]}

], augmentation=[]]
2017-09-16 12:17:30,611 | INFO | ult-dispatcher-2 | SalRoleServiceImpl | 290 - org.opendaylight.openflowplugin.impl - 0.3.3.Boron-SR3 | Role to be set is same as the last known role for the device:BECOMEMASTER. Hence ignoring.