Systems can't be recommissioned as part of releasing
Bug #1459405 reported by
Jason Hobbs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Wishlist
|
Unassigned | ||
Bug Description
Sometimes we need to recommission systems - for example, if MAAS added a feature that detects hardware during commissioning, or if a system got some more storage or had a network cable plugged in.
For OIL, we have to take systems out of the pool of available systems by removing their tag to do this. It's a pretty big pain - we end up just stopping OIL for a few hours to do this.
It would be nice if we could instead configure MAAS to recommission systems on the next release - or on release in general. It doesn't take long, and since OIL would see these systems as already in use, it wouldn't mess with how OIL schedules jobs based on available systems.
| summary: |
- Systems have to be taken out of rotation to be recommissioned + Systems can't be recommissioned as part of releasing |
| Changed in maas: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| milestone: | none → next |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Invalid |
| Changed in maas: | |
| milestone: | next → none |
To post a comment you must log in.
Hi!
We believe this is no longer an issue in the latest MAAS releases. As such, we are marking this bug report as invalid. If you believe this is still an issue, please re-open this bug report.
Thanks