[2.0] The IP of a Machine's BMC is not listed on the subnet details page

Bug #1616417 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Mike Pontillo

Bug Description

A BMC has an ip such: 192.168.122.2
The Subnet details page does not list it:

192.168.122.1 Static unleashed virbr0 Rack and region controller MAAS Wed, 24 Aug. 2016 11:39:14
192.168.122.190 Observed node03 eth0 Machine MAAS Wed, 24 Aug. 2016 11:39:12
192.168.122.191 Observed node02 eth1 Machine MAAS Wed, 24 Aug. 2016 11:39:12
192.168.122.192 Observed node01 eth0 Machine MAAS Wed, 24 Aug. 2016 11:39:15

So, I tried to add a device in MAAS with the IP above, and the result was:

2016-08-24 11:40:55 [-] Error on request (88) device.create: IP address is already in use.
        Traceback (most recent call last):
          File "/usr/lib/python3.5/threading.py", line 862, in run
            self._target(*self._args, **self._kwargs)
          File "/usr/lib/python3/dist-packages/provisioningserver/utils/twisted.py", line 790, in worker
            return target()
          File "/usr/lib/python3/dist-packages/twisted/_threads/_threadworker.py", line 46, in work
            task()
          File "/usr/lib/python3/dist-packages/twisted/_threads/_team.py", line 190, in doWork
            task()
        --- <exception caught here> ---
          File "/usr/lib/python3/dist-packages/twisted/python/threadpool.py", line 246, in inContext
            result = inContext.theWork()
          File "/usr/lib/python3/dist-packages/twisted/python/threadpool.py", line 262, in <lambda>
            inContext.theWork = lambda: context.call(ctx, func, *args, **kw)
          File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 118, in callWithContext
            return self.currentContext().callWithContext(ctx, func, *args, **kw)
          File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 81, in callWithContext
            return func(*args,**kw)
          File "/usr/lib/python3/dist-packages/provisioningserver/utils/twisted.py", line 823, in callInContext
            return func(*args, **kwargs)
          File "/usr/lib/python3/dist-packages/maasserver/utils/orm.py", line 602, in call_within_transaction
            return func_outside_txn(*args, **kwargs)
          File "/usr/lib/python3/dist-packages/maasserver/utils/orm.py", line 421, in retrier
            return func(*args, **kwargs)
          File "/usr/lib/python3.5/contextlib.py", line 30, in inner
            return func(*args, **kwds)
          File "/usr/lib/python3/dist-packages/maasserver/websockets/handlers/device.py", line 279, in create
            INTERFACE_LINK_TYPE.STATIC, subnet, ip_address=ip_address)
          File "/usr/lib/python3/dist-packages/maasserver/models/interface.py", line 819, in link_subnet
            alloc_type=alloc_type, user=user)
          File "/usr/lib/python3/dist-packages/maasserver/models/interface.py", line 765, in _link_subnet_static
            "IP address is already in use.")
        maasserver.exceptions.StaticIPAddressUnavailable: IP address is already in use.

Related branches

no longer affects: maas/2.0
Revision history for this message
Mike Pontillo (mpontillo) wrote :

As of MAAS 2.2, these are actually listed on the subnet details page, but they show up as "Unknown".

We could do a better job indicating the usage of each IP address.

Changed in maas:
status: Fix Committed → Fix Released
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.