MAAS

[UI] "IP address is already in use" not surfaced in the UI

Bug #1600249 reported by Jacek Nykis
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
MAAS
Triaged
High
Unassigned
2.2
Fix Released
Undecided
Unassigned

Bug Description

When I try to set static IP address for a node in the networks section MAAS reverts last octet to .1 automatically.

In the screenshot network1.png you can see that I set last octet to .21. As soon as the edit box looses focus it reverts to .1 (network2.png screenshot).

This behaviour is potentially catastrophic because .1 is often assigned to routers. If somebody misses this automatic change and deploys servers with .1 IP it can lead to connectivity problems for the whole subnet.

Logs are here: https://private-fileshare.canonical.com/~jacek/lp1600249.tgz
please don't share outside of company.

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===========================================================-=============================================-============-===============================================================================
un maas <none> <none> (no description available)
ii maas-cli 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS command line API tool
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS server common files
un maas-dhcp <none> <none> (no description available)
ii maas-dns 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.3+bzr4577-0ubuntu1~trusty1 all MAAS server provisioning libraries

See original description
Revision history for this message
Jacek Nykis (jacekn) wrote :
Revision history for this message
Jacek Nykis (jacekn) wrote :
Jacek Nykis (jacekn)
description: updated
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi Jacek,

This may be due to one of two things:

1. It takes a bit to update in the DB and refresh the UI.
2. There's is an error that's not being surfaced in the UI, but should be available in the logs. Can you please check both ?

Changed in maas:
status: New → Incomplete
Revision history for this message
Jacek Nykis (jacekn) wrote :

1. It did not happen within 30 seconds or so and there was no error message to indicate any problems.

I any case if changes need time to make it to the DB it would be better to have "Save" button with confirmation that the operation was successful. It's network settings so if they are wrong potential impact is very high.

2. I did not find anything interesting in the logs. There is a link in the bug report to where to find them, one of the developers can go through them in case I missed something.

Changed in maas:
status: Incomplete → New
Revision history for this message
LaMont Jones (lamont) wrote :

If MAAS is managing the subnet, it should really be told about all of the machines/devices/etc on the network, or their IPs should be marked as reserved, at a minimum.

Revision history for this message
LaMont Jones (lamont) wrote :

Based on regiond.log, it would appear that the error we're not surfacing is:
2016-07-08 14:18:12 [-] Error on request (1149) node.link_subnet: IP address is already in use.

Revision history for this message
LaMont Jones (lamont) wrote :

Which is apparently an unrelated log entry.

Revision history for this message
Jacek Nykis (jacekn) wrote :

Actually after more careful investigation it could be related...

I check on another machine and MAAS also will not allow me to change IP address, I can see the following in the logs when I try:

maasserver.exceptions.StaticIPAddressUnavailable: IP address is already in use.

But the message above is definitely a lie, the IP does not respond to ping or anything else on the network.

It may or may not be related but the IP causing problems used to be used by the same physical server I'm trying to redeploy now

Revision history for this message
Paul Gear (paulgear) wrote : Re: Static IP assignement reverts last octet to "1"

This sounds like a duplicate of #1569683.

summary: - Static IP assignement reverts last octed to "1"
+ Static IP assignement reverts last octet to "1"
Paul Gear (paulgear)
summary: - Static IP assignement reverts last octet to "1"
+ Static IP assignment reverts last octet to "1"
Revision history for this message
Mike Pontillo (mpontillo) wrote : Re: Static IP assignment reverts last octet to "1"

I saw similar issues while testing a separate bug fix earlier today. I'll dig deeper tomorrow.

Changed in maas:
status: New → Triaged
importance: Undecided → High
Andres Rodriguez (andreserl)
summary: - Static IP assignment reverts last octet to "1"
+ [UI] "IP address is already in use" not surfaced in the UI
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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