Description of problem: vdsm identifies the host as localhost instead of true hostname Version-Release number of selected component (if applicable): vdsm-4.16.24.5.git290f439 How reproducible: 100% Steps to Reproduce: 1.auto register the engine using BOOTIF=eth0 ssh_pwauth=1 adminpw=ovonFQQPIAM9o storage_init=/dev/sda management_server=192.168.100.100 hostname=node1 ip=192.168.100.111 netmask=255.255.255.0 gateway=192.168.100.1 2.The host will appear on engine as localhost 3.The host TUI shows hostname node1 Actual results: The host will appear on engine as localhost Expected results: The host will appear on engine as node1 Additional info:
Taking now, to review this registration bug.
the occurance is 100% on powerfull machines and around 50% on less powerfull
I am moving to ovirt-node component as this initial patch is in ovirt-node.
Cannot reproduce. Version-Release number of selected component (if applicable): rhev-hypervisor-7-7.1-20150805.0 Steps to Reproduce: 1, PXE install with the following arguments: management_server=192.168.20.134 ip=192.168.20.173 hostname=node1 gateway=192.168.20.2 netmask=255.255.255.0 BOOTIF=enp32s0f1 adminpw=OKr05SbCu3D3g storage_init=/dev/sda reinstall ssh_pwauth=1 Additional info: The host name appear on RHEVM as node1, and the host status is up. The host name appear on TUI as node1. The output of the commands: [root@node1 admin]# hostname node1 [root@node1 admin]# hostname -f localhost.localdomain [root@node1 admin]# hostname --all-fqdn node1 node1
Hi tlitovsk, We cannot reproduce this bug on our site and I notice that there is a patch for this bug. If this patch is merged into RHEV-H target build in the feature, I want to know could you help us to verify this bug on RHEV-H target build ? If you cannot verify this bug, we need to ask patch owner to provide the detail steps to do sanity only test to verify this bug. Thanks, Chaofeng
I wonder if the root cause of this issue is the same as with the other dhcp localhos.localdomain problem like bug 1254580
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
Moving this out for now, because it's not clear what the root cause is.
Lowering the priority because QE can not reproduce it, see comment 5.
Tolik, can you still reproduce this issue? Otherwise I tend to close it and abandon the patch. It might be related to bug 1232338.
Hi Tolik, I have tried to reproduce your report using rhev-hypervisor7-7.2-20151123.0.iso but I couldn't (as Chaofeng Wu tried as well in comment#3). The vdsm in the iso is vdsm-4.16.30-1.el7ev. Closing this bug for now, in case it reappear, please re-open.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days