[2.1,2.2] Anonymous auto-enlistment fails to contact metadata service
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Mike Pontillo | ||
2.1 |
Fix Released
|
High
|
Mike Pontillo |
Bug Description
Per the attached diagram.
MaaS is receiving DHCP PXE calls via the router's DHCP helper address/forwarder, but fails to boot nodes for acceptance.
Region:
root@juju-
Ubuntu 16.04.2 LTS \n \l
root@juju-
Linux juju-rack2.
rack ping,
root@juju-
PING 192.168.199.6 (192.168.199.6) 56(84) bytes of data.
64 bytes from 192.168.199.6: icmp_seq=1 ttl=64 time=0.400 ms
64 bytes from 192.168.199.6: icmp_seq=2 ttl=64 time=0.402 ms
^C
--- 192.168.199.6 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.400/0.
root@juju-
Package: maas-region-
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 52
Maintainer: Ubuntu Developers <email address hidden>
Architecture: all
Source: maas
Version: 2.2.0~beta2+
Depends: avahi-utils, dbconfig-pgsql, iputils-ping, maas-dns (= 2.2.0~beta2+
Recommends: openssh-server
Suggests: nmap
Description: Region Controller for MAAS
The MAAS region controller (maas-regiond) is the REST API server for
all MAAS clients, and the postgres database that maintains machine
state for the entire data centre (or “region”). The region controller
an be scaled-out and highly available given the appropriate postgres
setup and additional API servers.
.
This package installs the postgres database and the API server, so it
is appropriate for the initial installation of a new MAAS region. To
scale out the controller or make it highly available, install
maas-region-
postgres database is HA too.
Homepage: http://
Rack:
root@rack2-
Ubuntu 16.10 \n \l
root@rack2-
Linux rack2-maas-rack0 4.8.0-37-generic #39-Ubuntu SMP Thu Jan 26 02:27:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
region ping,
root@rack2-
PING 192.168.199.2 (192.168.199.2) 56(84) bytes of data.
64 bytes from 192.168.199.2: icmp_seq=1 ttl=64 time=0.422 ms
64 bytes from 192.168.199.2: icmp_seq=2 ttl=64 time=0.414 ms
^C
--- 192.168.199.2 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1025ms
rtt min/avg/max/mdev = 0.414/0.
root@rack2-
Package: maas-rack-
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 103
Maintainer: Ubuntu Developers <email address hidden>
Architecture: all
Source: maas
Version: 2.2.0~beta2+
Replaces: maas-cluster-
Depends: authbind, avahi-utils, bind9utils, distro-info, freeipmi-tools, grub-common, iputils-ping, maas-cli (= 2.2.0~beta2+
Suggests: amtterm, ipmitool, libvirt-bin, nmap, wsmancli
Breaks: maas-cluster-
Conflicts: tftpd-hpa
Conffiles:
/etc/logrotate
/etc/sudoers.
Description: Rack Controller for MAAS
The MAAS rack controller (maas-rackd) provides highly available, fast
and local broadcast services to the machines provisioned by MAAS. You
need a MAAS rack controller attached to each fabric (which is a set of
trunked switches). You can attach multiple rack controllers to these
physical networks for high availability, with secondary rack controllers
automatically stepping to provide these services if the primary rack
controller fails.
.
A common configuration is to have a rack controller in each rack, with
a fast primary network interface to the rack switch and secondary
network interfaces on one or two other nearby racks for high
availability redundancy.
.
This package depends on the necessary components to provide iSCSI,
DHCP, TFTP and power management.
Homepage: http://
Dashboard MaaS Version:
MAAS Version 2.2.0 (beta2+bzr5717)
Related branches
- Lee Trager (community): Approve
-
Diff: 55 lines (+34/-0)2 files modifiedsrc/maasserver/models/subnet.py (+3/-0)
src/maasserver/models/tests/test_subnet.py (+31/-0)
- Mike Pontillo (community): Approve
-
Diff: 96 lines (+57/-0)3 files modifieddocs/changelog.rst (+23/-0)
src/maasserver/models/subnet.py (+3/-0)
src/maasserver/models/tests/test_subnet.py (+31/-0)
description: | updated |
Changed in maas: | |
status: | New → Invalid |
Changed in maas: | |
status: | Invalid → New |
summary: |
- MaaS devel bad request routing on PXE + [2.2] Anonymous auto-enlistment fails to contact metadata service |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
It attempts to use a self-signed IP address to fetch OS components (image attached.) I am not sure how much of this is normal expected behavior having not seen this work correctly before.