[Discovery-3.0]: With 2 space characters between Publisher and subscriber while mentioning the rule, rule is misinterpreted and functions incorrectly

[Pulkit Tandon]

BUG Template

OS version: 3.13.0-40-generic #69-Ubuntu
Contrail Version: 3.0-2699

Setup details:
Multinode setup.
TestBed file attached for details.

Configurations:
Discovery server running and it does auto assignments of services to clients.
Rules were created over that.

Description:
Initially there was no rule.
Attached "Screen Shot 2016-01-27 at 1.04.09 PM.png” shows the state where no rule is present.
In this case, contrail-DNS and contrail-control running on different nodes use 2 instances from any of the available publishers.

Then, i applied following rule:
root@nodeh4:/opt/contrail/utils# python discovery_cli.py --name default-discovery-service-assignment --rule "10.204.217.52,IfmapServer 10.204.217.52,contrail-control" --op add-rule

Oper = add-rule
Name = ['default-discovery-service-assignment']
UUID = None
API Server = 127.0.0.1:5998
Discovery Server = 127.0.0.1:5998

Empty DSA group!
 10.204.217.52/32,IfmapServer,, /32,,,
Confirm (y/n): y
root@nodeh4:/opt/contrail/utils#

Please note that DSA entry is shown as "10.204.217.52/32,IfmapServer,, /32,,,” in the above output.
At first, i thought its just a display issue.

Then i noticed that all subscriber clients(contrail-dns and contrail-control) running on different nodes forcefully subscribe to 10.204.217.52/32,IfmapServer.
I expected only subscriber “10.204.217.52,contrail-control” will forcefully subscribe to 10.204.217.52/32,IfmapServer.

Please see the snapshot attached with name "Screen Shot 2016-01-27 at 12.46.45 PM.png” to get an idea of the issue.

So, in reality, subscriber entry "/32,,,” is getting treated as a valid entry which include all subscribers in the network.

Logs:
The issue is reproducible and self descriptive.
So no logs have been taken.

[Pulkit Tandon (pulkitt)]

After more debugging, it was found that issue is because of 2 space characters between publisher and Subscriber entries.
Thus, the issue is somewhat similar to #1538503.

Please handle it accordingly.

[Pulkit Tandon (pulkitt)]

This issue is with specific utility which is not customer deliverable.
Hence no fix is required.