designate: rndc client information for worker is generated by the wrong service
Bug #1971991 reported by
Brent Eagles
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Confirmed
|
High
|
Brent Eagles | ||
Bug Description
Currently the rndc files that are meant to be used by designate workers to talk to bind backends are generated along with the bind pool file in the central container. These should be generated for the designate workers not central. Also, we need to specify source addresses on the workers to allow the rndc access control rules on the bind servers to work properly.
| Changed in tripleo: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| assignee: | nobody → Brent Eagles (beagles) |
| milestone: | none → yoga-1 |
To post a comment you must log in.
