On Tue, Sep 09, 2014 at 11:42:21PM -0000, Julian Edwards wrote:
> Everything looks fine from a MAAS pov;
> c0:3f:d5:63:ff:41 has got IP 10.14.100.2
> c0:3f:d5:60:4e:f2 has got IP 10.14.100.11
>
> DNS is linking node1.maas to 10.14.100.2
I think maybe I missed telling a key piece of information:
node1.maas (c0:3f:d5:60:4e:f2) should be 10.14.100.11
but DNS thinks it's 10.14.100.2
node9.maas c0:3f:d5:60:4e:f2 I have no idea about, but it probably
wasn't turned on at the time.
Anyway, in the leases file, *:4e:f2 is 10.14.100.11 and is the only
entry in there, yet the dns mapping was wrong.
On Tue, Sep 09, 2014 at 11:42:21PM -0000, Julian Edwards wrote:
> Everything looks fine from a MAAS pov;
> c0:3f:d5:63:ff:41 has got IP 10.14.100.2
> c0:3f:d5:60:4e:f2 has got IP 10.14.100.11
>
> DNS is linking node1.maas to 10.14.100.2
I think maybe I missed telling a key piece of information:
node1.maas (c0:3f:d5:60:4e:f2) should be 10.14.100.11
but DNS thinks it's 10.14.100.2
node9.maas c0:3f:d5:60:4e:f2 I have no idea about, but it probably
wasn't turned on at the time.
Anyway, in the leases file, *:4e:f2 is 10.14.100.11 and is the only
entry in there, yet the dns mapping was wrong.
This is the bug.
Maas version: 1.7.0~beta2+ bzr2916- 0ubuntu1~ ppa1
--
David Britton <email address hidden>