| 2017-10-28 21:51:07 |
Andres Rodriguez |
bug |
|
|
added bug |
| 2017-10-28 21:51:12 |
Andres Rodriguez |
maas: importance |
Undecided |
Critical |
|
| 2017-10-28 21:51:14 |
Andres Rodriguez |
maas: status |
New |
Triaged |
|
| 2017-10-28 21:51:24 |
Andres Rodriguez |
maas: milestone |
|
2.3.0rc1 |
|
| 2017-10-28 21:53:52 |
Andres Rodriguez |
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. |
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]. 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://bugs.launchpad.net/maas/+bug/1728304
[2]: https://bugs.launchpad.net/maas/+bug/1727561
[3]: https://bugs.launchpad.net/maas/+bug/1718517 |
|
| 2017-10-28 21:54:11 |
Andres Rodriguez |
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]. 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://bugs.launchpad.net/maas/+bug/1728304
[2]: https://bugs.launchpad.net/maas/+bug/1727561
[3]: https://bugs.launchpad.net/maas/+bug/1718517 |
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://bugs.launchpad.net/maas/+bug/1728304
[2]: https://bugs.launchpad.net/maas/+bug/1727561
[3]: https://bugs.launchpad.net/maas/+bug/1718517 |
|
| 2017-10-28 22:00:00 |
Andres Rodriguez |
summary |
[2.3] Comissioning didn't not remove disks that no longer exist |
[2.3] Comissioning didn't remove disks that no longer exist |
|
| 2017-10-30 13:36:52 |
Andres Rodriguez |
maas: assignee |
|
Blake Rouse (blake-rouse) |
|
| 2017-11-03 14:56:42 |
Andres Rodriguez |
maas: milestone |
2.3.0rc1 |
2.3.0rc2 |
|
| 2017-11-07 16:05:08 |
Björn Tillenius |
marked as duplicate |
|
1662343 |
|
