|Summary:||IP address of the host can't be changed to FQDN, not while host is active, neither it's under maintenance.|
|Product:||Red Hat Enterprise Virtualization Manager||Reporter:||Nikolai Sednev <nsednev>|
|Component:||ovirt-engine||Assignee:||nobody nobody <nobody>|
|Status:||CLOSED DUPLICATE||QA Contact:|
|Version:||3.4.0||CC:||acathrow, dfediuck, gklein, iheim, lpeer, oourfali, Rhev-m-bugs, yeylon|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2014-05-26 11:24:19 UTC||Type:||Bug|
|oVirt Team:||Infra||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Nikolai Sednev 2014-05-18 07:44:51 UTC
Description of problem: IP address of the host can't be changed to FQDN, not while host is active, neither it's under maintenance. Version-Release number of selected component (if applicable): Host: libvirt-0.10.2-29.el6_5.7.x86_64 sanlock-2.8-1.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.415.el6_5.9.x86_64 vdsm-4.14.7-2.el6ev.x86_64 ovirt-hosted-engine-ha-1.1.2-3.el6ev.noarch Engine: rhevm-3.4.0-0.20.el6ev.noarch How reproducible: 100% Steps to Reproduce: 1.Assemble setup containing 2 hosts and engine, give IP addresses for the hosts instead of FQDN. 2.Try changing IP address for one of the hosts to it's FQDN, while host is active, the field will be greyed out, making impossible to make any changes. 3.Same as 2, only now try to put host in to maintenance first. Actual results: Address can't be changed. Expected results: I host under maintenance, IP should be changeable to FQDN or another IP. Additional info: Attached picture.
Comment 1 Nikolai Sednev 2014-05-18 07:45:26 UTC
Created attachment 896752 [details] picture of greyed out address field.
Comment 2 Oved Ourfali 2014-05-26 11:24:19 UTC
Closed as a duplicate. The interesting use-case here is changing the host address. Not the fact that you have an IP and want to switch it to FQDN. Using IP address is a less interesting use-case anyway, as it probably won't be used in standard environments. *** This bug has been marked as a duplicate of bug 1060215 ***