Tried to allocate an IP to MAC but its cluster interface is not known
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Confirmed
|
Medium
|
Unassigned |
Bug Description
I upgraded to 1.7.0~beta5+
This pastebin has a console log of what happens when I click on "start node":
https:/
Basically it comes up, downloads an image, installs it, reboots, and then the network doesn't work anymore.
In the maas logs, the only interesting thing that I could find was this:
==> maas.log <==
Oct 7 18:20:05 atlas maas.macaddress: [ERROR] mino: Tried to allocate an IP to MAC 2c:59:e5:3b:f0:fe but its cluster interface is not known
Oct 7 18:20:05 atlas maas.macaddress: [ERROR] mino: Tried to allocate an IP to MAC 2c:59:e5:3b:f0:ff but its cluster interface is not known
==> maas-django.log <==
ERROR 2014-10-07 18:23:53,800 maasserver Unable to identify boot image for (ubuntu/
"mino" has 4 nics, and two are connected to the maas-eth0 network which is fully managed by maas (dns + dhcp). The two MAC addresses above are from the two NICs that are connected elsewhere or not connected.
This was a working cluster before the upgrade, and images are there in the "Images" tab.
summary: |
- Upgraded to 1.7.0~beta5+bzr3199+3164+318~ppa0~ubuntu14.04.1 can't reach + Upgraded to 1.7.0~beta5+bzr3199+3164+318~ppa0~ubuntu14.04.1, can't reach nodes |
tags: | added: landscape |
summary: |
- Upgraded to 1.7.0~beta5+bzr3199+3164+318~ppa0~ubuntu14.04.1, can't reach - nodes + Tried to allocate an IP to MAC but its cluster interface is not known |
Changed in maas: | |
milestone: | none → 1.7.0 |
Changed in maas: | |
status: | Incomplete → Confirmed |
Changed in maas: | |
importance: | Undecided → Medium |
Hang on, I'm not sure this is a valid bug, this —I assume— is a result of the testing you've done on a package built from https:/ /code.launchpad .net/~rvb/ maas/fix- etc-hosts- bug-1087183- 2/+merge/ 236709; correct (see the MP for details)?