MAAS 1.8rc3 broken bind's zone files
Bug #1467213 reported by
Ante Karamatić
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
Critical
|
Unassigned |
Bug Description
Upon successful commissioning and (almost) successful 'juju bootstrap', I noticed that nodes can't resolve their own hostnames. Quick look at MAAS's bind files revealed source of the problem. I'm attaching both zone files.
I will try to reproduce it. So far it happened in one out of one attempts.
Changed in maas: | |
importance: | Critical → High |
Changed in maas: | |
importance: | High → Critical |
Changed in maas: | |
status: | Triaged → Won't Fix |
To post a comment you must log in.
On the second attempt, it generated hostname in zonefile just fine.