Unable to see IP leases in MAAS UI

Bug #1756781 reported by Mark Shuttleworth
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Medium
Unassigned

Bug Description

I have MAAS providing DHCP and monitoring the network. When I look at the interface, I see a number of observed nodes, but I can't see which of those have been given addresses by the MAAS DHCP server and which are genuinely rogue.

Ideally:

 * the subnet listing would show leases currently outstanding on that subnet
 * the vlan reserved range would show number / percentage used and link to a list
 * the discovery dashboard would flag items that got their IP from MAAS DHCP

Revision history for this message
Mike Pontillo (mpontillo) wrote :

Good ideas. We'll see what we can do for MAAS 2.4.

In the case of MAAS-managed DHCP, we can join the discovery view with the StaticIPAddress table and check for an allocation type of DHCP to determine whether or not a MAAS DHCP server handed out the lease.

I wonder if it would also be appropriate to highlight addresses that did NOT come from MAAS DHCP, and do NOT have an entry in the StaticIPAddress table. That would indicate a "likely rogue" address (if the subnet is a managed subnet).

Changed in maas:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 2.4.x
Revision history for this message
Mark Shuttleworth (sabdfl) wrote :

Yes, I think that would be very helpful. Addresses that are on the network but not recorded in MAAS are 'rogue' even if they don't conflict with anything else, because we want MAAS to be a full and accurate record of every device on the LAN.

Revision history for this message
Jerzy Husakowski (jhusakowski) wrote :

Feature request, moved to the internal product feedback backlog (internal ref. PF-3875)

Changed in maas:
milestone: 2.4.x → none
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.