[2.x] MAAS rack controller cannot auto discover interfaces on whitebox switches
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Unassigned |
Bug Description
I am upgrading whitebox switches to 16.04 and MAAS 2.0 and running ICOS as a snap on these devices. MAAS and Ubuntu and ICOS snaps all work, however, when I create a routing device in ICOS, it is not auto discovered by MAAS. In MAAS 1.9 it would auto detect these interfaces if I created them before installing MAAS, and I could manually create them in 1.9 if I created them after installing MAAS. I have tried both of these on MAAS 2.0 but cannot figure out how to manually create interfaces on the the rack controller.
I have included all the logs from /var/log/maas, but don't see antyhing in there about even trying to discover these interfaces.
The interfaces do show up in ifconfig and I can manage them with ifconfig.
This seems like a regression since in 1.9 this did work.
Changed in maas: | |
status: | New → Incomplete |
importance: | Undecided → High |
summary: |
- MAAS 2.0 cannot auto discover interfaces on whitebox switches + [2.0] MAAS 2.0 cannot auto discover interfaces on whitebox switches |
Changed in maas: | |
milestone: | none → 2.1.0 |
Changed in maas: | |
milestone: | 2.1.0 → 2.1.1 |
Changed in maas: | |
milestone: | 2.1.1 → 2.1.2 |
Changed in maas: | |
milestone: | 2.1.2 → 2.1.3 |
Changed in maas: | |
milestone: | 2.2.0 → 2.2.x |
Changed in maas: | |
status: | Incomplete → Triaged |
Changed in maas: | |
milestone: | 2.2.x → 2.3.0 |
tags: | added: switch |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.x |
Desired= Unknown/ Install/ Remove/ Purge/Hold Not/Inst/ Conf-files/ Unpacked/ halF-conf/ Half-inst/ trig-aWait/ Trig-pend /Reinst- required (Status,Err: uppercase=bad) ======= ======= ======= ======= -====== ======= ======= ======= ===-=== ======= ==-==== ======= ======= ======= ======= ======= ======= === 0ubuntu1~ 16.04.1 all "Metal as a Service" is a physical cloud and IPAM 0ubuntu1~ 16.04.1 all MAAS client and command-line interface controller <none> <none> (no description available) 0ubuntu1~ 16.04.1 all MAAS server common files 0ubuntu1~ 16.04.1 all MAAS DHCP server 0ubuntu1~ 16.04.1 all MAAS DNS server 0ubuntu1~ 16.04.1 all MAAS Caching Proxy controller 2.0.0+bzr5189- 0ubuntu1~ 16.04.1 all Rack Controller for MAAS 0ubuntu1~ 16.04.1 all Region controller API service for MAAS controller 2.0.0+bzr5189- 0ubuntu1~ 16.04.1 all Region Controller for MAAS controller- min <none> <none> (no description available) maas-provisioni ngserver <none> <none> (no description available) 0ubuntu1~ 16.04.1 all MAAS server Django web framework (Python 3) 0ubuntu1~ 16.04.1 all MAAS python API client (Python 3) maas-provisioni ngserver 2.0.0+bzr5189- 0ubuntu1~ 16.04.1 all MAAS server provisioning libraries (Python 3)
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 2.0.0+bzr5189-
ii maas-cli 2.0.0+bzr5189-
un maas-cluster-
ii maas-common 2.0.0+bzr5189-
ii maas-dhcp 2.0.0+bzr5189-
ii maas-dns 2.0.0+bzr5189-
ii maas-proxy 2.0.0+bzr5189-
ii maas-rack-
ii maas-region-api 2.0.0+bzr5189-
ii maas-region-
un maas-region-
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-
ii python3-django-maas 2.0.0+bzr5189-
ii python3-maas-client 2.0.0+bzr5189-
ii python3-