We have seen several times migration failing due to having host with same name, usually localhost.localdomain, just because that's the default hostname set by anaconda. In order to avoid later issues, let's refuse to deploy hosts without a hostname set.
I don't mind preventing hostname 'localhost.localdomain', but perhaps we also want to prevent adding a host whose hostname is already registered as the hostname of another host in the db. This is a larger change, requiring patches at least to the engine, perhaps also vdsm or host-deploy (or both). Sandro, what do you say?
(In reply to Yedidyah Bar David from comment #1) > Sandro, what do you say? Make sense to me but such a change involve infra changes at engine level. Oved, what do you think?
BTW, another alternative is to make migration do work in such a case. Not sure that's easy, but we already know what we need to know - we just need to make libvirt not prevent this. See also bug 1107650.
(In reply to Sandro Bonazzola from comment #2) > (In reply to Yedidyah Bar David from comment #1) > > Sandro, what do you say? > > Make sense to me but such a change involve infra changes at engine level. > Oved, what do you think? I don't think this corner case worths the efforts required around that.
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0. If you think this bug should block 4.3.0 please re-target and set blocker flag.
Moving to 4.3.2 not being identified as blocker for 4.3.1.
*** This bug has been marked as a duplicate of bug 1546838 ***