better UX to validate KVM host addresses

[Junien F]

Hi,

MAAS 2.7 stable snap.

When editing a KVM host configuration, if I use a domain name (ie qemu+ssh://<email address hidden>/system) instead of an IP, clicking on "Save changes" will start a spinner for "Trying to connect and discover KVM" for a while and only then display a semi-cryptic "failed to detect a valid IP address from 'my-machine.internal'" error message

I think that :
1. the usage of an IP should be checked in Javascript on the browser side, and immediately error when pressing "Save changes"
2. Using a localhost-y IP (so any IP starting by 127. (and fe80::/64 , and ::1/128) ) should either be prohibited, or should trigger a warning about potential confusion if you have multiple controllers.
3. The error message should be better worded (for example : error : 'my-machine.internal' is not a valid IP address)

Thanks

[Lee Trager (ltrager)]

For LXD Pods in 2.8 we made MAAS a bit more forgivable. Both the protocol and port are optional. Instead of fixing this in the Javascript I think we should do the same for libvirt.

[Jerzy Husakowski (jhusakowski)]

Is this issue still present in recent MAAS (3.1 or later) and LXD as the VM host?

[Jerzy Husakowski (jhusakowski)]

The question whether it's still reproducible on recent MAAS still stands. MAAS 2.7 is out of support.

[Launchpad Janitor (janitor)]

[Expired for MAAS because there has been no activity for 60 days.]