[2.3] Comissioning didn't remove disks that no longer exist
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Triaged
|
Critical
|
Blake Rouse | ||
Bug Description
I had a machine in MAAS with 4 disks. I re-ran commissioning + testing and noticed bug [1]. Whne I manually logged into the machine, I noticed that only 2 disks were discovered. In other words, MAAS only discovered 2 disk instead of 4. This meant that disks either failed or were removed but a following commissioning did not delete the disks that were missing.
Note that this is the same machine of [2], where the machine was actually failing to commission because it was unable to update the disks. I think we need to evaluate that the fix for [3] may have suppressed raising the actual issues, provided that the machine no longer failed to commission.
[1]: https:/
[2]: https:/
[3]: https:/
| Changed in maas: | |
| importance: | Undecided → Critical |
| status: | New → Triaged |
| milestone: | none → 2.3.0rc1 |
| description: | updated |
| description: | updated |
| summary: |
- [2.3] Comissioning didn't not remove disks that no longer exist + [2.3] Comissioning didn't remove disks that no longer exist |
| Changed in maas: | |
| assignee: | nobody → Blake Rouse (blake-rouse) |
| Changed in maas: | |
| milestone: | 2.3.0rc1 → 2.3.0rc2 |
| Björn Tillenius (bjornt) wrote | #1 |
Unless you have any logs to prove otherwise, I'm quite sure this is a duplicate of bug 1662343. That would happen if the first two disks were removed.