[2.3, UI, UX, HWTv2] No confirmation message is asked when attempting to run hardware tests on deployed machines

Hi,

While I agree it would be nicer to have a warning when trying to test a deployed machine, could you please share a bit more what your expectation is or what problem you actually got?

Did you attempted to run hardware tests on the specific machine from the Machine details page, or were you trying to run hardware tests on multiple machines from the Node listing page?

Hi Andres,
It seems that the user was working on Nodes listing page and had multiple nodes selected but got confused on the filter selection (the left-hand side) and ran Memory/CPU stress tests on the wrong set of nodes.

I guess the expectation would be to alert the user before running any testing on live nodes (mandatory for destructive nodes) so that he knows what he is doing?

Regards,
Nusrath

Correction: (mandatory for destructive tests)

Ok. For destructive tests it should have definitely given a warning.
Anyway, thanks for the input.

On Sat, Feb 17, 2018 at 11:30 AM Nusrath Mohammed <
<email address hidden>> wrote:

> Hi Andres,
> It seems that the user was working on Nodes listing page and had multiple
> nodes selected but got confused on the filter selection (the left-hand
> side) and ran Memory/CPU stress tests on the wrong set of nodes.
>
> I guess the expectation would be to alert the user before running any
> testing on live nodes (mandatory for destructive nodes) so that he knows
> what he is doing?
>
> Regards,
> Nusrath
>
> --
> You received this bug notification because you are subscribed to MAAS.
> https://bugs.launchpad.net/bugs/1750160
>
> Title:
> [2.3, UI, UX, HWTv2] No confirmation message is asked when attempting
> to run hardware tests on deployed machines
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1750160/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=maas; milestone=2.4.x; status=Triaged;
> importance=High; assignee=None;
> Launchpad-Bug-Tags: canonical-bootstack internal
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: andreserl nusrath.mohammed
> Launchpad-Bug-Reporter: Nusrath Mohammed (nusrath.mohammed)
> Launchpad-Bug-Modifier: Nusrath Mohammed (nusrath.mohammed)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For: andreserl
>
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

It would be cool if it could talk to juju and know that a node was juju deployed and give an explicit warning of as much if someone was trying to run a possibly production impacting action (anything from a memtest to a reboot). If someone is aware it's in machine in a production env and choose to do so anyway, a warning to click through can be a very minor annoyance, but if someone accidentally selects a deployed node rather than the one they are targeting while working on machines that are going to be added to a cloud or have been removed from a cloud,.. well that can be a very big issue and something, I for one, would be very thankful to receive a warning about prior to actioning.

In my particular use of MAAS, I primarily interact with it in the later situations and almost only use it on production machines to get information about them. When adding or removing a bunch of machines, it's easy to accidentally de-select a tag or select the wrong machine. I have workflows with triple checking in place but it would still be an appreciated feature.

Thanks Andres, for making maas what it is either way. Being able to run the hardware tests from this interface and have so much information in an easily navigable interface makes my life much easier :)
Really appreciate all of y'all's work