Comment 9 for bug 1366726
Revision history for this message
| Larry Michel (lmic) wrote Re: [Bug 1366726] Re: CI breakage: Deployed nodes don't get a static IP address | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
In the lease file, I did not see a host{} for that IP/MAC address
combination so answer would be no. There was only an entry for the Dynamic
IP.
To answer your question about the delete/re-add, the answer is yes for
phelps node (we were moving network cards between servers) and a no for
mokoi node.
There was an issue last week that I had reported in 1387859. This had to do
with too many unreleased dynamic leases and a file could not be parsed. So
perhaps, the behaviour I described in this bug was related to these
servers' mac addresses not having been fully synced to cluster as you
indicated. I would have to monitor for recreate since we don't think we're
running into 1387859.
About the cluster not knowing about the mac addresses, I am seeing a flood
of these log messages below and I am wondering whether it's related. We are
seeing failed deployments where the server can not be accessed on the DNS
IP address, but not all servers with this ERROR have failed to come up on
the static IP. I will attach latest maas logs and lease files as well.
...
/var/log/
maas.macaddress: [ERROR] tucker.local: Tried to allocate an IP to MAC
2c:59:e5:41:a8:6d but its cluster interface is not known
/var/log/
maas.macaddress: [ERROR] tucker.local: Tried to allocate an IP to MAC
2c:59:e5:41:a8:6e but its cluster interface is not known
/var/log/
maas.macaddress: [ERROR] tucker.local: Tried to allocate an IP to MAC
2c:59:e5:41:a8:6f but its cluster interface is not known
/var/log/
maas.macaddress: [ERROR] muncie.local: Tried to allocate an IP to MAC
2c:59:e5:3a:47:e5 but its cluster interface is not known
/var/log/
maas.macaddress: [ERROR] muncie.local: Tried to allocate an IP to MAC
2c:59:e5:3a:47:e6 but its cluster interface is not known
/var/log/
maas.macaddress: [ERROR] muncie.local: Tried to allocate an IP to MAC
2c:59:e5:3a:47:e7 but its cluster interface is not known
/var/log/
maas.macaddress: [ERROR] sunset.local: Tried to allocate an IP to MAC
2c:59:e5:3a:65:55 but its cluster interface is not known
/var/log/
maas.macaddress: [ERROR] sunset.local: Tried to allocate an IP to MAC
2c:59:e5:3a:65:56 but its cluster interface is not known
/var/log/
maas.macaddress: [ERROR] sunset.local: Tried to allocate an IP to MAC
2c:59:e5:3a:65:57 but its cluster interface is not known
ubuntu@
...
On Mon, Nov 3, 2014 at 5:46 PM, Julian Edwards <email address hidden>
wrote:
> On Monday 03 November 2014 13:58:12 you wrote:
> > Can you please clarify what you mean by host {} block.
>
> In the leases file, we write a host{} entry which forces an IP for a MAC.
> However it only does this if it knows on which cluster interface the MAC
> resides.
>
> > 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.
>
> Did you delete the node(s) and re-add at all? It sounds like it had not
> picked up the cluster interface link at this stage and when you redeployed
> that knowledge had then been ascertained at that point. It relies on
> scanning
> the dynamic leases to work this out.
>
> >
> > Maas version is 1.7.0~rc1+
>
> Ok, thanks.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> CI breakage: Deployed nodes don't get a static IP address
>
> Status in MAAS:
> Fix Committed
>
> Bug description:
> The failure in http://
> 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:/
>