----- Original Message -----
> From: "Simon Grinberg" <[email protected]>
> To: "Mike Burns" <[email protected]>
> Cc: "node-devel" <[email protected]>
> Sent: Sunday, October 14, 2012 5:10:40 PM
> Subject: Re: [Users] oVirt Node 2.5.2 ISO released
> 
> Hi Mike,
> 
> I was trying to install it and when setting from the TUI I get an
> error message command "hostname" not found.
> Dropping into shell I get the same. /etc/sysconfig/network is getting
> the proper value, but after reboot this is not reflected in the host
> name (though the value in /etc/sysconfig/network is persisted)

OK, I managed to workaround this by directly changing the host name:
echo <new host name>  > /proc/sys/kernel/hostname

This allowed me to register the node with the engine (before that it complained 
on missing proper certificates)
The change does not sustain reboot, but it seems that the connection with VDSM 
does. 

I guess the next time point I'll be hit by this issue is live migration, but 
not sure about that (I don't remember if libvirt still validates the host name 
before migration).

> 
> Any idea?
> 
> Thanks,
> Simon.
> 
> ----- Original Message -----
> > From: "Mike Burns" <[email protected]>
> > To: "node-devel" <[email protected]>, "users" <[email protected]>
> > Sent: Friday, October 5, 2012 6:23:11 PM
> > Subject: [Users] oVirt Node 2.5.2 ISO released
> > 
> > The long awaited and much anticipated oVirt Node 2.5.2 ISO is now
> > available on ovirt.org.  This build includes the fixed vdsm to
> > allow
> > nfs
> > based domains to be attached.
> > 
> > Thanks for the patience while we worked out the issue with NFS.
> > 
> > The oVirt Node Team
> > 
> > http://ovirt.org/releases/3.1/tools/ovirt-node-iso-2.5.2-0.1.fc17.iso
> > 
> > 
> > _______________________________________________
> > Users mailing list
> > [email protected]
> > http://lists.ovirt.org/mailman/listinfo/users
> > 
> 
_______________________________________________
node-devel mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/node-devel

Reply via email to