| 2016-03-08 15:22:11 |
Andres Rodriguez |
bug |
|
|
added bug |
| 2016-03-08 17:04:25 |
Andres Rodriguez |
maas: milestone |
|
2.0.0 |
|
| 2016-03-08 17:04:30 |
Andres Rodriguez |
maas: importance |
Undecided |
Critical |
|
| 2016-03-08 17:04:35 |
Andres Rodriguez |
maas: importance |
Critical |
High |
|
| 2016-03-11 15:32:26 |
Andres Rodriguez |
summary |
[2.0a1] PXE interface is incorrectly determined |
[2.0a1] PXE interface is incorrectly determined or not determined at all |
|
| 2016-03-11 15:49:56 |
Andres Rodriguez |
description |
The PXE interface is incorrectly determine. In this case, eth0 is the PXE interface but MAAS is saying eth1: is:
http://people.canonical.com/~andreserl/pxe-interface.png |
The PXE interface is incorrectly determine. In this case, eth0 is the PXE interface but MAAS is saying eth1: is:
http://people.canonical.com/~andreserl/pxe-interface.png
Machine's output:
[
{
"type": "physical",
"id": 136,
"resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/136/",
"children": [],
"mac_address": "74:d4:35:89:bd:2b",
"params": "",
"vlan": {
"primary_rack": null,
"id": 1,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"mtu": 1500,
"name": "untagged",
"dhcp_on": false,
"secondary_rack": null,
"fabric": "fabric-0",
"vid": 0
},
"tags": [],
"parents": [],
"effective_mtu": 1500,
"enabled": true,
"name": "eth0",
"links": [],
"discovered": null
},
{
"type": "physical",
"id": 137,
"resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/137/",
"children": [],
"mac_address": "74:d4:35:89:bd:2c",
"params": "",
"vlan": {
"primary_rack": null,
"id": 1,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"mtu": 1500,
"name": "untagged",
"dhcp_on": false,
"secondary_rack": null,
"fabric": "fabric-0",
"vid": 0
},
"tags": [],
"parents": [],
"effective_mtu": 1500,
"enabled": true,
"name": "eth1",
"links": [],
"discovered": null
}
]
VLAN output:
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-0
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"secondary_rack": null,
"id": 1,
"fabric": "fabric-0",
"mtu": 1500,
"name": "untagged",
"primary_rack": null,
"dhcp_on": false
}
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-1
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/2/",
"secondary_rack": null,
"id": 2,
"fabric": "fabric-1",
"mtu": 1500,
"name": "untagged",
"primary_rack": null,
"dhcp_on": false
}
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-2
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/3/",
"secondary_rack": null,
"id": 3,
"fabric": "fabric-2",
"mtu": 1500,
"name": "untagged",
"primary_rack": "4y3h7n",
"dhcp_on": true
}
] |
|
| 2016-03-11 15:51:27 |
Andres Rodriguez |
description |
The PXE interface is incorrectly determine. In this case, eth0 is the PXE interface but MAAS is saying eth1: is:
http://people.canonical.com/~andreserl/pxe-interface.png
Machine's output:
[
{
"type": "physical",
"id": 136,
"resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/136/",
"children": [],
"mac_address": "74:d4:35:89:bd:2b",
"params": "",
"vlan": {
"primary_rack": null,
"id": 1,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"mtu": 1500,
"name": "untagged",
"dhcp_on": false,
"secondary_rack": null,
"fabric": "fabric-0",
"vid": 0
},
"tags": [],
"parents": [],
"effective_mtu": 1500,
"enabled": true,
"name": "eth0",
"links": [],
"discovered": null
},
{
"type": "physical",
"id": 137,
"resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/137/",
"children": [],
"mac_address": "74:d4:35:89:bd:2c",
"params": "",
"vlan": {
"primary_rack": null,
"id": 1,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"mtu": 1500,
"name": "untagged",
"dhcp_on": false,
"secondary_rack": null,
"fabric": "fabric-0",
"vid": 0
},
"tags": [],
"parents": [],
"effective_mtu": 1500,
"enabled": true,
"name": "eth1",
"links": [],
"discovered": null
}
]
VLAN output:
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-0
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"secondary_rack": null,
"id": 1,
"fabric": "fabric-0",
"mtu": 1500,
"name": "untagged",
"primary_rack": null,
"dhcp_on": false
}
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-1
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/2/",
"secondary_rack": null,
"id": 2,
"fabric": "fabric-1",
"mtu": 1500,
"name": "untagged",
"primary_rack": null,
"dhcp_on": false
}
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-2
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/3/",
"secondary_rack": null,
"id": 3,
"fabric": "fabric-2",
"mtu": 1500,
"name": "untagged",
"primary_rack": "4y3h7n",
"dhcp_on": true
}
] |
The PXE interface is incorrectly determine. In this case, eth0 is the PXE interface but MAAS is saying eth1: is:
http://people.canonical.com/~andreserl/pxe-interface.png
Interface shows that the PXE MAC is eth1, but the API shows it is eth0.
http://people.canonical.com/~andreserl/interface_mac_pxe.png
Machine's output:
[
{
"type": "physical",
"id": 136,
"resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/136/",
"children": [],
"mac_address": "74:d4:35:89:bd:2b",
"params": "",
"vlan": {
"primary_rack": null,
"id": 1,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"mtu": 1500,
"name": "untagged",
"dhcp_on": false,
"secondary_rack": null,
"fabric": "fabric-0",
"vid": 0
},
"tags": [],
"parents": [],
"effective_mtu": 1500,
"enabled": true,
"name": "eth0",
"links": [],
"discovered": null
},
{
"type": "physical",
"id": 137,
"resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/137/",
"children": [],
"mac_address": "74:d4:35:89:bd:2c",
"params": "",
"vlan": {
"primary_rack": null,
"id": 1,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"mtu": 1500,
"name": "untagged",
"dhcp_on": false,
"secondary_rack": null,
"fabric": "fabric-0",
"vid": 0
},
"tags": [],
"parents": [],
"effective_mtu": 1500,
"enabled": true,
"name": "eth1",
"links": [],
"discovered": null
}
]
VLAN output:
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-0
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"secondary_rack": null,
"id": 1,
"fabric": "fabric-0",
"mtu": 1500,
"name": "untagged",
"primary_rack": null,
"dhcp_on": false
}
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-1
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/2/",
"secondary_rack": null,
"id": 2,
"fabric": "fabric-1",
"mtu": 1500,
"name": "untagged",
"primary_rack": null,
"dhcp_on": false
}
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-2
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/3/",
"secondary_rack": null,
"id": 3,
"fabric": "fabric-2",
"mtu": 1500,
"name": "untagged",
"primary_rack": "4y3h7n",
"dhcp_on": true
}
] |
|
| 2016-03-11 15:52:37 |
Andres Rodriguez |
maas: importance |
High |
Critical |
|
| 2016-03-11 15:52:45 |
Andres Rodriguez |
summary |
[2.0a1] PXE interface is incorrectly determined or not determined at all |
[2.0a1] PXE interface is incorrectly determined |
|
| 2016-03-11 15:58:54 |
Andres Rodriguez |
summary |
[2.0a1] PXE interface is incorrectly determined |
[2.0a1] PXE interface & fabric are incorrectly determined |
|
| 2016-03-11 15:59:37 |
Andres Rodriguez |
summary |
[2.0a1] PXE interface & fabric are incorrectly determined |
[2.0a1] Fabric are incorrectly determined, which may cause PXE interface incorrectly showed in the UI |
|
| 2016-03-11 16:01:40 |
Andres Rodriguez |
description |
The PXE interface is incorrectly determine. In this case, eth0 is the PXE interface but MAAS is saying eth1: is:
http://people.canonical.com/~andreserl/pxe-interface.png
Interface shows that the PXE MAC is eth1, but the API shows it is eth0.
http://people.canonical.com/~andreserl/interface_mac_pxe.png
Machine's output:
[
{
"type": "physical",
"id": 136,
"resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/136/",
"children": [],
"mac_address": "74:d4:35:89:bd:2b",
"params": "",
"vlan": {
"primary_rack": null,
"id": 1,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"mtu": 1500,
"name": "untagged",
"dhcp_on": false,
"secondary_rack": null,
"fabric": "fabric-0",
"vid": 0
},
"tags": [],
"parents": [],
"effective_mtu": 1500,
"enabled": true,
"name": "eth0",
"links": [],
"discovered": null
},
{
"type": "physical",
"id": 137,
"resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/137/",
"children": [],
"mac_address": "74:d4:35:89:bd:2c",
"params": "",
"vlan": {
"primary_rack": null,
"id": 1,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"mtu": 1500,
"name": "untagged",
"dhcp_on": false,
"secondary_rack": null,
"fabric": "fabric-0",
"vid": 0
},
"tags": [],
"parents": [],
"effective_mtu": 1500,
"enabled": true,
"name": "eth1",
"links": [],
"discovered": null
}
]
VLAN output:
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-0
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"secondary_rack": null,
"id": 1,
"fabric": "fabric-0",
"mtu": 1500,
"name": "untagged",
"primary_rack": null,
"dhcp_on": false
}
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-1
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/2/",
"secondary_rack": null,
"id": 2,
"fabric": "fabric-1",
"mtu": 1500,
"name": "untagged",
"primary_rack": null,
"dhcp_on": false
}
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-2
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/3/",
"secondary_rack": null,
"id": 3,
"fabric": "fabric-2",
"mtu": 1500,
"name": "untagged",
"primary_rack": "4y3h7n",
"dhcp_on": true
}
] |
The PXE interface is incorrectly determine. In this case, eth0 is the PXE interface but MAAS is saying eth1: is:
http://people.canonical.com/~andreserl/pxe-interface.png
Interface shows that the PXE MAC is eth1, but the API shows it is eth0.
http://people.canonical.com/~andreserl/interface_mac_pxe.png
Also, after taking a close look at the API output:
1. Fabric on eth0 is determined incorrectly, as this should be 'Fabric-2' instead of 'Fabric-0'. This reflects on both the API and UI.
2. PXE interface is determined correctly on the API, but what the Web UI shows is different.
Machine's output:
[
{
"type": "physical",
"id": 136,
"resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/136/",
"children": [],
"mac_address": "74:d4:35:89:bd:2b",
"params": "",
"vlan": {
"primary_rack": null,
"id": 1,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"mtu": 1500,
"name": "untagged",
"dhcp_on": false,
"secondary_rack": null,
"fabric": "fabric-0",
"vid": 0
},
"tags": [],
"parents": [],
"effective_mtu": 1500,
"enabled": true,
"name": "eth0",
"links": [],
"discovered": null
},
{
"type": "physical",
"id": 137,
"resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/137/",
"children": [],
"mac_address": "74:d4:35:89:bd:2c",
"params": "",
"vlan": {
"primary_rack": null,
"id": 1,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"mtu": 1500,
"name": "untagged",
"dhcp_on": false,
"secondary_rack": null,
"fabric": "fabric-0",
"vid": 0
},
"tags": [],
"parents": [],
"effective_mtu": 1500,
"enabled": true,
"name": "eth1",
"links": [],
"discovered": null
}
]
VLAN output:
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-0
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"secondary_rack": null,
"id": 1,
"fabric": "fabric-0",
"mtu": 1500,
"name": "untagged",
"primary_rack": null,
"dhcp_on": false
}
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-1
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/2/",
"secondary_rack": null,
"id": 2,
"fabric": "fabric-1",
"mtu": 1500,
"name": "untagged",
"primary_rack": null,
"dhcp_on": false
}
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-2
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/3/",
"secondary_rack": null,
"id": 3,
"fabric": "fabric-2",
"mtu": 1500,
"name": "untagged",
"primary_rack": "4y3h7n",
"dhcp_on": true
}
] |
|
| 2016-03-11 16:36:15 |
Andres Rodriguez |
summary |
[2.0a1] Fabric are incorrectly determined, which may cause PXE interface incorrectly showed in the UI |
[2.0a1] Fabric are incorrectly determined during enlistment, which may cause PXE interface incorrectly showed in the UI |
|
| 2016-03-12 04:15:43 |
Andres Rodriguez |
summary |
[2.0a1] Fabric are incorrectly determined during enlistment, which may cause PXE interface incorrectly showed in the UI |
[2.0a1/2.0pre-a2] Fabric are incorrectly determined during enlistment, which may cause PXE interface incorrectly showed in the UI |
|
| 2016-03-12 05:15:22 |
Andres Rodriguez |
summary |
[2.0a1/2.0pre-a2] Fabric are incorrectly determined during enlistment, which may cause PXE interface incorrectly showed in the UI |
[2.0a1/2.0pre-a2] Incorrect fabric on machine interface, causes commissioning to fail |
|
| 2016-03-12 05:20:28 |
Andres Rodriguez |
description |
The PXE interface is incorrectly determine. In this case, eth0 is the PXE interface but MAAS is saying eth1: is:
http://people.canonical.com/~andreserl/pxe-interface.png
Interface shows that the PXE MAC is eth1, but the API shows it is eth0.
http://people.canonical.com/~andreserl/interface_mac_pxe.png
Also, after taking a close look at the API output:
1. Fabric on eth0 is determined incorrectly, as this should be 'Fabric-2' instead of 'Fabric-0'. This reflects on both the API and UI.
2. PXE interface is determined correctly on the API, but what the Web UI shows is different.
Machine's output:
[
{
"type": "physical",
"id": 136,
"resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/136/",
"children": [],
"mac_address": "74:d4:35:89:bd:2b",
"params": "",
"vlan": {
"primary_rack": null,
"id": 1,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"mtu": 1500,
"name": "untagged",
"dhcp_on": false,
"secondary_rack": null,
"fabric": "fabric-0",
"vid": 0
},
"tags": [],
"parents": [],
"effective_mtu": 1500,
"enabled": true,
"name": "eth0",
"links": [],
"discovered": null
},
{
"type": "physical",
"id": 137,
"resource_uri": "/MAAS/api/2.0/nodes/4y3haq/interfaces/137/",
"children": [],
"mac_address": "74:d4:35:89:bd:2c",
"params": "",
"vlan": {
"primary_rack": null,
"id": 1,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"mtu": 1500,
"name": "untagged",
"dhcp_on": false,
"secondary_rack": null,
"fabric": "fabric-0",
"vid": 0
},
"tags": [],
"parents": [],
"effective_mtu": 1500,
"enabled": true,
"name": "eth1",
"links": [],
"discovered": null
}
]
VLAN output:
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-0
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/1/",
"secondary_rack": null,
"id": 1,
"fabric": "fabric-0",
"mtu": 1500,
"name": "untagged",
"primary_rack": null,
"dhcp_on": false
}
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-1
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/2/",
"secondary_rack": null,
"id": 2,
"fabric": "fabric-1",
"mtu": 1500,
"name": "untagged",
"primary_rack": null,
"dhcp_on": false
}
]
ubuntu@trusty-maas9:~$ maas admin vlans read fabric-2
Success.
Machine-readable output follows:
[
{
"vid": 0,
"resource_uri": "/MAAS/api/2.0/vlans/3/",
"secondary_rack": null,
"id": 3,
"fabric": "fabric-2",
"mtu": 1500,
"name": "untagged",
"primary_rack": "4y3h7n",
"dhcp_on": true
}
] |
==> /var/log/maas/regiond.log <==
2016-03-12 00:16:59 [maasserver] ERROR: ################################ Exception: 'NoneType' object has no attribute 'url' ################################
2016-03-12 00:16:59 [maasserver] ERROR: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 132, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/usr/lib/python3/dist-packages/maasserver/utils/views.py", line 180, in view_atomic_with_post_commit_savepoint
return view_atomic(*args, **kwargs)
File "/usr/lib/python3.5/contextlib.py", line 30, in inner
return func(*args, **kwds)
File "/usr/lib/python3/dist-packages/maasserver/api/pxeconfig.py", line 202, in pxeconfig
preseed_url = compose_preseed_url(node)
File "/usr/lib/python3/dist-packages/maasserver/preseed.py", line 704, in compose_preseed_url
base_url = node.get_boot_primary_rack_controller().url
AttributeError: 'NoneType' object has no attribute 'url'
2016-03-12 00:16:59 [-] 127.0.0.1 - - [11/Mar/2016:16:16:58 +0000] "GET /MAAS/api/2.0/pxeconfig/?local=192.168.10.27&bios_boot_method=pxe&mac=74-d4-35-89-bd-2b&ra
ckcontroller_id=4y3h7n&remote=192.168.10.59 HTTP/1.0" 500 40 "-" "provisioningserver.pserv_services.tftp.TFTPBackend" |
|
| 2016-03-12 05:20:57 |
Andres Rodriguez |
summary |
[2.0a1/2.0pre-a2] Incorrect fabric on machine interface, causes commissioning to fail |
[2.0a1/2.0pre-a2] Outdated Fabric may cause commissioning to fail |
|
| 2016-03-12 05:22:30 |
Andres Rodriguez |
summary |
[2.0a1/2.0pre-a2] Outdated Fabric may cause commissioning to fail |
[2.0a1/2.0pre-a2] Fail to commission when Fabric on Machine Interface and Rack Interface dont match |
|
| 2016-03-16 16:01:32 |
Gavin Panella |
maas: status |
New |
Triaged |
|
| 2016-03-16 16:32:32 |
Launchpad Janitor |
branch linked |
|
lp:~blake-rouse/maas/tftp-rpc-boot-config |
|
| 2016-03-16 16:33:34 |
Blake Rouse |
maas: status |
Triaged |
In Progress |
|
| 2016-03-16 16:33:37 |
Blake Rouse |
maas: assignee |
|
Blake Rouse (blake-rouse) |
|
| 2016-03-17 14:55:44 |
MAAS Lander |
maas: status |
In Progress |
Fix Committed |
|
| 2016-03-21 18:59:55 |
Launchpad Janitor |
branch linked |
|
lp:~andreserl/maas/pkg_a3_changelog |
|
| 2016-03-21 19:00:28 |
Andres Rodriguez |
branch unlinked |
lp:~andreserl/maas/pkg_a3_changelog |
|
|
| 2016-08-18 11:20:28 |
Andres Rodriguez |
maas: status |
Fix Committed |
Fix Released |
|
