dhcp lease rollover causes loss of access to managment IP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Julian Edwards | ||
maas (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I've seen this a few times (and I thought we had a bug raised but it would appear not).
MAAS is attached to a /24 network with a DHCP pool limited to say 10->100 (90 IP's); the iLO/DRAC/AMT cards get a IP via DHCP OK, but then the pool is exhausted, the IP's which should of been allocated to the management cards are leased to other clients.
Its entirely possible that the management cards are not renewing leases (12 hours by default I think) resulting in this behaviour.
We worked around this by fixing the IP address allocations in /etc/maas/
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: maas 1.4+bzr1820+
ProcVersionSign
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.1-0ubuntu2
Architecture: amd64
Date: Thu Jan 30 13:08:45 2014
InstallationDate: Installed on 2014-01-23 (7 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016)
PackageArchitec
SourcePackage: maas
UpgradeStatus: Upgraded to trusty on 2014-01-23 (7 days ago)
Related branches
- Julian Edwards (community): Approve
-
Diff: 109 lines (+45/-5)4 files modifiedetc/maas/templates/power/amt.template (+3/-4)
src/maasserver/power_parameters.py (+2/-1)
src/provisioningserver/tasks.py (+2/-0)
src/provisioningserver/tests/test_tasks.py (+38/-0)
- Jeroen T. Vermeulen (community): Approve
-
Diff: 102 lines (+21/-8)6 files modifiedetc/maas/templates/power/ipmi.template (+6/-0)
src/maasserver/models/node.py (+2/-2)
src/maasserver/models/tests/test_node.py (+6/-4)
src/maasserver/power_parameters.py (+5/-1)
src/provisioningserver/power/tests/test_poweraction.py (+1/-1)
src/provisioningserver/tasks.py (+1/-0)
Changed in maas: | |
assignee: | nobody → Julian Edwards (julian-edwards) |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
This appears to have happened in the Garage MAAS. Attached is the leases
file, which contains 141 static host maps, and references 145 different
hardware addresses. Below is a snippet from the dhcpd.conf file that was
being used at the time:
subnet 192.168.9.0 netmask 255.255.255.0 {
ignore- client- uids true; class-identifie r, 0, 3) = "PXE";
default- lease-time 30;
max- lease-time 30;
filename "pxelinux.0";
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.9.255;
option domain-name-servers 192.168.1.25;
option domain-name "cloud.mallards";
option routers 192.168.9.1;
option ntp-servers 91.189.94.4;
range dynamic-bootp 192.168.9.10 192.168.9.150;
class "PXE" {
match if substring (option vendor-
}
}