Comment 7 for bug 1366726

Can you please clarify what you mean by host {} block.

We are not not doing anything specific for any of the host. So all the
hosts in the environment should behave the same AFAICT. In the past, both
of these hosts had previously deployed OK with an IP address allocated at
deploy times rather than the dynamic IP. Mokoi is also now deploying OK
with a different static IP.

Maas version is 1.7.0~rc1+bzr3295-0ubuntu1~trusty1.

On Sun, Nov 2, 2014 at 4:37 PM, Julian Edwards <email address hidden>
wrote:

> Which version of MAAS are you using?
>
> On Friday 31 October 2014 11:13:47 you wrote:
> > I am seeing this in our environment with phelps and mokoi servers which
> > deployed with dynamic IP associated with mac address as shown by the
> > dhcpd.lease file rather than the static IP address shown on each node's
> > page in the maas Web UI. .
> >
> > On the maas server, their DNS names resolved with the correct static IP
> > address. However, that static address was not present in the dhcpd.lease
> > file and I could only access the server through the dynamic IP address.
>
> Was there a host {} block for the static IP for the node(s)? If not the
> help
> depends on the version of MAAS you're using.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1366726
>
> Title:
> CI breakage: Deployed nodes don't get a static IP address
>
> Status in MAAS:
> Fix Committed
>
> Bug description:
> The failure in http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-
> adt-maas/612/ indicates that the deployed nodes didn't get a static IP
> address. They kept their dynamic IP address from the commissioning
> phase.
>
> It seems that there is a race somewhere as it doesn't happen all the
> time.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1366726/+subscriptions
>