[2.5, enhancement] Allow selecting which tests to run during enlistment

Bug #1794289 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Unassigned

Bug Description

It would be nice to be able to select which tests I would like to run by default. This would include:

1. Option to select which tests to run on enlistment
2. Option to select which tests to run by default during commissioning.

Changed in maas:
milestone: none → 2.5.0
status: New → Triaged
tags: added: enhancement track
tags: added: wishlist
removed: enhancement
summary: - [2.5] Allow selecting which tests to run during enlistment
+ [2.5, enhancement] Allow selecting which tests to run during enlistment
tags: added: bmc-enlistment
Revision history for this message
Lee Trager (ltrager) wrote :

We already have the commissioning tag which selects which tests are run by default during commissioning. Originally when I implemented commissioning during enlistment I actually added any test tagged commissioning. That was removed during review but I could add it back.

We have to decide two questions:
1. Should we use keep using the 'commissioning' tag or use a new 'enlisting' tag? I think reusing commissioning works as the set of tests a user wants to be run during enlistment will be the same as commissioning(smartctl-validate by default).
2. Should users be allowed to set destructive tests to be run by default? Its a valid use case that a user may want destructive tests run during enlistment however I would NOT add any destructive tests to be run by default.

Changed in maas:
assignee: nobody → Lee Trager (ltrager)
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Removing you as an assignee as this is not (yet) targeted for fixing.

That said, “commissioning” is *NOT* testing so we shouldn’t combine things together. We will discuss and design this enhancement once scheduled.

Changed in maas:
assignee: Lee Trager (ltrager) → nobody
Changed in maas:
milestone: 2.5.0 → 2.5.x
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.