Comment 5 for bug 1750160

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