Comment 11 for bug 1851587

Hi Nick,

I hear you and IMHO revealing the FQDN is kind of a "soft" problem, as it could only hurt you (the deployer) if you've got your hypervisor exposed to the public internet and revealing its address is going to give someone the opportunity to launch a targeted attack on it to brute force the credentials (or whatever else). Having a hypervisor exposed to the internet isn't typical or recommended and probably (hopefully) nobody does that, but if they do, it could be a problem.

Hence, this is a "hardening opportunity" and we've not proposed a patch to deal with it yet because (1) it's a "soft" problem and (2) it's not trivial to fix unless we just remove the FQDN from the exception message altogether (which I am personally fine with).

To answer your last question, yes a non-admin user can see HypervisorUnavailable if, for example, the libvirt process is stopped or nova otherwise can't reach the libvirt monitor when they attempt to delete their server. This is rare I expect, but could happen.