Discovery : "fixed" policy not working as expected
Bug #1341533 reported by
Hari Prasad Killi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R1.1 |
Fix Committed
|
Undecided
|
Deepinder Setia | |||
| Trunk |
Fix Committed
|
High
|
Deepinder Setia | |||
Bug Description
In a three control node, three compute, one config node setup, configured the dns-server service policy as "fixed". The expected behavior in this case is that all compute nodes get the same DNS server. But the compute nodes are getting different set of dns servers. Tried with restart of discovery, agent before checking the above behavior.
Also, upon further restarts of agent, two agents didnt receive dns configuration.
Our current DNS strategy works only with two DNS servers in the cluster. So "fixed" policy is expected to be configured for dns-server in a multi-control node setup.
| Changed in juniperopenstack: | |
| assignee: | nobody → Nipa (nipak) |
| Changed in juniperopenstack: | |
| milestone: | none → r1.10-fcs |
| tags: | added: blocker |
| information type: | Proprietary → Public |
| Changed in juniperopenstack: | |
| importance: | Undecided → High |
To post a comment you must log in.
Fixed with https:/