[Discovery-Rel3.0-Centos-1]: All clients re-subscribe to a different publisher when a rule is added which was supposed to affect only 1 subscriber (No Auto load balance)
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Fix Released
|
High
|
Deepinder Setia | |||
Trunk |
Fix Committed
|
High
|
Deepinder Setia |
Bug Description
Bug Template : Centos
OS version: 3.10.0-
Contrail Version: 3.0-1.el7.centos
Setup details:
Multinode setup.
Testbed file attached
Configurations:
Discovery server running and it does auto assignments of services to clients.
Description:
3 dns-servers are present in topology:
nodeh4: 77.77.1.10
nodeg12: 77.77.2.10
nodec10: 77.77.3.10
3 vrouter compute nodes are present in the topology:
nodeh8: 77.77.1.11
nodeg31: 77.77.2.11
nodec28: 77.77.3.11
Step 1: contrail-
Step 2: Please see the default assignment of services in attached file named
“Screen shot before rule.png”.
Step 3: Created Rule 1 as follows:
77.77.3.
As expected, as soon as this rule is created, "77.77.
Step 4: Noted the following:
Other subscribers "77.77.
Please see attached screenshot "Screen Shot after rule.png” to understand what has happened.
Step 5: Tried deletion and addition of similar rules and changing the value of publisher in the rule.
Each time, all subscribers were getting affected.
There is definitely some link of one with all that trigger re-subscription.
Logs:
The issue is reproducible and self descriptive.
So no logs have been taken.
information type: | Proprietary → Public |
summary: |
[Discovery-Rel3.0-Centos-1]: All clients re-subscribe to a different publisher when a rule is added which was supposed to affect only 1 - subscriber + subscriber (No Auto load balance) |
Changed in juniperopenstack: | |
milestone: | r3.0-fcs → none |
tags: | added: blocker |
tags: | removed: blocker |
Pulkit, what is the policy set for dns-server?