On Thursday, February 16, 2012, Michael DeHaan elucidated thus:
> OK, I understand that that there was no hostname assigned.
However,
> how do you assign one when you're installing with koan and
> --profile? I supplied a --virt-name, which I expected to be the
> name it used to auto- register the machine. There could be a way
> to specify a hostname when doing a 'koan --profile' install, but
> I'm not seeing it.
The system failed to detect the hostname from running *inside* the
guest, it has nothing to do with what parameters you set on the
hypervisor. It got "localhost.localdomain" back, more or less,
and decided that wasn't going to be unique enough.
You could possibly use Cobbler with manage_dhcp and manage_dns to
ensure you gave out a particular hostname, though ordinarily I'd
expect you to at least get a dhcpXXX hostname if you have DHCP. In
this way, you would procreate the system before it exists rather
than using koan with --profile, you'd declare the system, assign a
MAC and IP, and use koan with --system instead to bring that system
to life. Much better, IMHO.
Yes, that is what I tried to do (pre-create the systems, configure the
DHCP, hostname, etc.) then used koan --system, but the system did not
inherit its profile's Kickstart Metadata. Is there a way I can
troubleshoot this? Some way I can dump the information koan is passing
to the install so I can see if the kickstart metadata is being "lost"
somewhere in the process?
Keep in mind cobbler-register has *NOTHING* to do with koan at all,
<SNIP>
cobbler-register is more for folks who have a large network of
machines they already provisioned using something else, and need to
get them into cobbler so they can reprovision, etc.
Gotcha.
j
--
Joshua J. Kugler - Fairbanks, Alaska
Azariah Enterprises - Programming and Website Design
joshua(a)azariah.com - Jabber: pedahzur(a)gmail.com
PGP Key:
http://pgp.mit.edu/ ID 0x73B13B6A