[2.3rc2, UI]There is an action override failed testing in the controller but there is no hardware testing informatio
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
[2.3rc2, UI]There is an action override failed testing in the controller but there is no hardware testing information
The controller page doesn't have a hardware tests section and health information in the summary so that the user knows the machine health. Also, the controller's status is not visible in the details page or the controller listing. The action Override failed testing might be confusing until this information is surfaced.
Bug description:
* Current result:
Given I am in the controller summary page
When I click on Take action
Then I see an action Override failed testing even though I don't know the health of the machine
* Expected/ correct result:
Given I am in the controller summary page
When I click on Take action
Then I see an action Override failed testing only if the health of the machine is exposed
[Ubuntu 16.04 running on VM]
Firefox 56.0 (64-bit)
| Maria Vrachni (m-vrachnis) wrote | #1 |
| Changed in maas: | |
| milestone: | none → 2.3.0rc2 |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in maas: | |
| milestone: | 2.3.0rc2 → 2.3.0 |
| Mike Pontillo (mpontillo) wrote | #2 |
| Maria Vrachni (m-vrachnis) wrote | #3 |
| Alberto Donato (ack) wrote | #4 |
| Changed in maas: | |
| status: | Triaged → Invalid |
| Changed in maas: | |
| milestone: | 2.3.0 → 2.3.x |
We discussed this during our stand-up today. To clarify, our interpretation is:
- We should allow overriding failed testing from a details page only if there is a "negative" health status that would prevent other actions.
- We should hide the "Override failed testing" action for both machines and controllers (on the details page) unless there is something to override.
Does this sound good?