| 2012-07-12 18:23:39 |
Andres Rodriguez |
bug |
|
|
added bug |
| 2012-07-12 18:23:46 |
Andres Rodriguez |
maas-enlist (Ubuntu): assignee |
|
Andres Rodriguez (andreserl) |
|
| 2012-07-12 18:23:49 |
Andres Rodriguez |
maas-enlist (Ubuntu): importance |
Undecided |
High |
|
| 2012-07-12 18:23:52 |
Andres Rodriguez |
maas-enlist (Ubuntu): status |
New |
In Progress |
|
| 2012-07-12 18:23:58 |
Andres Rodriguez |
nominated for series |
|
Ubuntu Precise |
|
| 2012-07-12 18:23:58 |
Andres Rodriguez |
bug task added |
|
maas-enlist (Ubuntu Precise) |
|
| 2012-07-12 18:23:58 |
Andres Rodriguez |
nominated for series |
|
Ubuntu Quantal |
|
| 2012-07-12 18:23:58 |
Andres Rodriguez |
bug task added |
|
maas-enlist (Ubuntu Quantal) |
|
| 2012-07-12 18:24:06 |
Andres Rodriguez |
maas-enlist (Ubuntu Precise): assignee |
|
Andres Rodriguez (andreserl) |
|
| 2012-07-12 18:24:08 |
Andres Rodriguez |
maas-enlist (Ubuntu Precise): importance |
Undecided |
High |
|
| 2012-07-12 18:24:12 |
Andres Rodriguez |
maas-enlist (Ubuntu Precise): status |
New |
Confirmed |
|
| 2012-07-12 18:35:12 |
Launchpad Janitor |
maas-enlist (Ubuntu Quantal): status |
In Progress |
Fix Released |
|
| 2012-07-12 19:02:13 |
Andres Rodriguez |
description |
In MAAS, there used to be various after_commissioning_actions. These ranged from 0 to 3. Nowadays, the only one left is 0. This needs to be changed in maas-enlist.
If this is not fixed, precise/quantal machines will not be able to enlist against a MAAS server in Quantal, and/or in Precise when it gets backported. |
In MAAS, there used to be various after_commissioning_actions. These ranged from 0 to 3. Nowadays, the only one left is 0. This needs to be changed in maas-enlist.
If this is not fixed, precise/quantal machines will not be able to enlist against a MAAS server in Quantal, and/or in Precise when it gets backported.
[IMPACT]
[TEST CASE]
== Reproduce Failure ==
1. Install a MAAS server in Quantal and maas-enlist:
sudo apt-get install maas maas-enlist
2. Try to enlist own node:
maas-enlist --serverurl=localhost
3. A failure will be shown:
ubuntu@server-13542:~$ maas-enlist --serverurl localhost
{"after_commissioning_action": ["Select a valid choice. 2 is not one of the available choices."]}
== Fixed Version ==
1. Install MAAS and the fixed version of maas-enlist
2. Enlist as above (maas-enlist --serverurl=localhost)
3. Success:
ubuntu@server-13542:~$ maas-enlist --serverurl localhost
{
"status": 0,
"macaddress_set": [
{
"mac_address": "fa:16:3e:0b:f8:be"
}
],
"power_parameters": "",
"netboot": true,
"hostname": "node-fa163e0bf8be.local",
"power_type": "",
"system_id": "node-0b48e4aa-cc54-11e1-9dc6-fa163e0bf8be",
"architecture": "amd64"
[REGRESSION POTENTIAL]
Minimal to None. Current MAAS in precise supports after_commissioning_action=0 as is the default when adding a node. |
|
| 2012-07-12 19:08:37 |
Andres Rodriguez |
description |
In MAAS, there used to be various after_commissioning_actions. These ranged from 0 to 3. Nowadays, the only one left is 0. This needs to be changed in maas-enlist.
If this is not fixed, precise/quantal machines will not be able to enlist against a MAAS server in Quantal, and/or in Precise when it gets backported.
[IMPACT]
[TEST CASE]
== Reproduce Failure ==
1. Install a MAAS server in Quantal and maas-enlist:
sudo apt-get install maas maas-enlist
2. Try to enlist own node:
maas-enlist --serverurl=localhost
3. A failure will be shown:
ubuntu@server-13542:~$ maas-enlist --serverurl localhost
{"after_commissioning_action": ["Select a valid choice. 2 is not one of the available choices."]}
== Fixed Version ==
1. Install MAAS and the fixed version of maas-enlist
2. Enlist as above (maas-enlist --serverurl=localhost)
3. Success:
ubuntu@server-13542:~$ maas-enlist --serverurl localhost
{
"status": 0,
"macaddress_set": [
{
"mac_address": "fa:16:3e:0b:f8:be"
}
],
"power_parameters": "",
"netboot": true,
"hostname": "node-fa163e0bf8be.local",
"power_type": "",
"system_id": "node-0b48e4aa-cc54-11e1-9dc6-fa163e0bf8be",
"architecture": "amd64"
[REGRESSION POTENTIAL]
Minimal to None. Current MAAS in precise supports after_commissioning_action=0 as is the default when adding a node. |
In MAAS, there used to be various after_commissioning_actions. These ranged from 0 to 3. Nowadays, the only one left is 0. This needs to be changed in maas-enlist.
If this is not fixed, precise/quantal machines will not be able to enlist against a MAAS server in Quantal, and/or in Precise when it gets backported.
[IMPACT]
Currently, maas-enlist enlists a node with after_commissioning_action=2. The default is 0. However, in newer MAAS releases the actions 1,2,3 no longer exist. The default is still 0. Enlisting with 2 has really no consequences and is no different to enlisting with 0.
Not enlisting with after_commissioning_action=0 means that precise nodes won't be able to enlist into MAAS running on quantal.
[TEST CASE]
== Reproduce Failure ==
1. Install a MAAS server in Quantal and maas-enlist:
sudo apt-get install maas maas-enlist
2. Try to enlist own node:
maas-enlist --serverurl=localhost
3. A failure will be shown:
ubuntu@server-13542:~$ maas-enlist --serverurl localhost
{"after_commissioning_action": ["Select a valid choice. 2 is not one of the available choices."]}
== Fixed Version ==
1. Install MAAS and the fixed version of maas-enlist
2. Enlist as above (maas-enlist --serverurl=localhost)
3. Success:
ubuntu@server-13542:~$ maas-enlist --serverurl localhost
{
"status": 0,
"macaddress_set": [
{
"mac_address": "fa:16:3e:0b:f8:be"
}
],
"power_parameters": "",
"netboot": true,
"hostname": "node-fa163e0bf8be.local",
"power_type": "",
"system_id": "node-0b48e4aa-cc54-11e1-9dc6-fa163e0bf8be",
"architecture": "amd64"
[REGRESSION POTENTIAL]
Minimal to None. Current MAAS in precise supports after_commissioning_action=0 as is the default when adding a node. |
|
| 2012-07-12 19:09:30 |
Andres Rodriguez |
maas-enlist (Ubuntu Precise): assignee |
Andres Rodriguez (andreserl) |
|
|
| 2012-07-12 19:09:33 |
Andres Rodriguez |
maas-enlist (Ubuntu Precise): status |
Confirmed |
New |
|
| 2012-07-12 19:09:40 |
Andres Rodriguez |
maas-enlist (Ubuntu Precise): importance |
High |
Critical |
|
| 2012-07-12 19:09:49 |
Andres Rodriguez |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2012-07-12 19:17:12 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/maas-enlist |
|
| 2012-07-13 19:27:54 |
Andres Rodriguez |
summary |
After Commission Action 2 no longer exists |
[SRU] After Commission Action 2 no longer exists |
|
| 2012-07-13 19:57:28 |
Clint Byrum |
maas-enlist (Ubuntu Precise): milestone |
|
ubuntu-12.04.1 |
|
| 2012-07-17 02:08:25 |
Adam Conrad |
maas-enlist (Ubuntu Precise): status |
New |
Fix Committed |
|
| 2012-07-17 02:08:28 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
| 2012-07-17 02:08:37 |
Adam Conrad |
tags |
|
verification-needed |
|
| 2012-07-17 02:58:15 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/precise/maas-enlist/precise-proposed |
|
| 2012-07-17 13:01:51 |
Andres Rodriguez |
tags |
verification-needed |
verification-done |
|
| 2012-07-24 05:35:25 |
Launchpad Janitor |
maas-enlist (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
