[1.9.0] Document need to recommission nodes that were deployed when upgrading from 1.8.3
Bug #1535690 reported by
Adam Collard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
Critical
|
Unassigned |
Bug Description
The release notes stated that "If upgrading from MAAS 1.8, only VM nodes with VirtIO storage devices need to be re-commissioned." - however even with real physical hardware, one still needs to recommission to avoid MAAS UI complaining about missing networks, missing disks and preventing deployment.
Re-commissioning a node remedied these complaints.
tags: | added: kanban-cross-team |
tags: | removed: kanban-cross-team |
tags: | added: landscape |
Changed in maas: | |
status: | Triaged → New |
Changed in maas: | |
status: | New → Triaged |
Changed in maas: | |
milestone: | 1.9.1 → 1.9.2 |
Changed in maas: | |
milestone: | 1.9.2 → 1.9.3 |
Changed in maas: | |
milestone: | 1.9.3 → 1.9.4 |
Changed in maas: | |
milestone: | 1.9.4 → 1.9.5 |
To post a comment you must log in.
Hi Adam,
Do you have any logs or screenshots displaying such behavior. Can you provide information about the hardware which you saw this issue with? Was the hardware deployed at upgrade time?
Thanks.