API outputs bad status_message not reflecting current state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
Low
|
Unassigned |
Bug Description
I commissioned a machine several times, and this machine failed a few times. After it had failed, I also re-commissioned the machine and succeeded the last time.
However, the status_message still shows a message from a previous failure on a previous commissionning not reflecting reality:
See that status_name is 'Ready' but status_message still shows 'Node commissioning failure'.
[
{
"pool": {
"name": "default",
"id": 0,
},
{
],
],
}
],
"status": 4,
"domain": {
"ttl": null,
"name": "maas",
"id": 0,
},
"name": "ens3",
"tags": [],
{
}
],
"type": "physical",
"vlan": {
},
"id": 8,
},
},
"bcaches": [],
"netboot": true,
"memory": 1024,
{
],
],
}
],
],
"fqdn": "generic.maas",
"hostname": "generic",
"locked": false,
"pod": {
"id": 2,
"name": "brave-gator",
},
"uuid": null,
"name": "sda",
"tags": [
],
"path": "/dev/disk/
{
}
],
"size": 21474836480,
"type": "physical",
"id": 5,
},
"osystem": "",
"storage": 21474.83648,
"raids": [],
{
],
},
}
],
"zone": {
"name": "default",
"id": 1,
},
"ipv4": {
},
"ipv6": {
}
},
"owner": null,
}
]
description: | updated |
summary: |
- [2.6] status_message has message even though it belongs to a previous - state + [2.6] API outputs bad status_message not reflecting current state |
summary: |
- [2.6] API outputs bad status_message not reflecting current state + API outputs bad status_message not reflecting current state |
Changed in maas: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Let's see if this still occurs - we should make sure we clear the status_message when we move to different statuses