#theforeman

maybe im creating the vm incorreclty on foreman? i mean this is my first go at foreman

also getting console blocked through firefox, so i cant see the console there either

btw i appricate you trying to help me

so when i go to the host that foreman creates, i look at the NICs tab and the nic doesnt have an ip

however if i run netdiscover I see it gets an ip...

so its def talking to dhcp at some point, I THINK

are all your logs going to syslog? you might check /var/log/foreman/production.log...

ok wow im making some progress

so i am able to vnc into the box using vncviewer

and it turns out my pxe is working

but it fails to run the kickstart

ok got that working pretty dumb moment really..

didnt have enough mem so the intrfs was dieing

but still have this anoying password onthe consol no clue to to unlock as it would be nice to see the consol directly through virt-manager

what do you mean you cannot see console directly?

ok well just fixed that in two sec too, ok im done lmao

was talking about display through virt-manager

yeah

using the gui

yeah, and?

appearenlty i have to force feed it a vnc password through virt-manager

ah

but thats not cool because i give it a pass in foreman

but ohwel not big deal really

now tomorrow i better figure out puppet as i have one more day to do a demo of this product lmoa

lol

one more day to figure it out

lol

kinda late

well... on paid hours

still

btw, worth to see hammer cli for foreman

i hate the way i spend like 16 hours or so on this and the end lesson is RFM

RTFM

lmao

could be worse, 'the issue is know since 2 years, no fix'

i have to get puppet working now with these things and install some modules... its possible to do in one day if everything goes smoothly

but seriouly frustrated with RHEL7 using the foreman-installer

you can set up foreman and example environment in about 2h if you know what you're doing exackly (commands etc)

well i have a full readme now i can manage that no issues now

but i have to do this on rhel7 now but the install hasnt worked for me yet

something about the foreman gpgkey already on file and doesnt match

_KaszpiR_: ok new thing after my pxe ks is finished it boots right back into pxe... appearently i have to somehow set the storage as first boot device and fail to pxe on first boot

havent done that useing foreman but should be interesting as everything takes hours and hours to figure out

it should always go to pxe

um yeah?

my pxe just does the install

and then it will be presented with different options per vm state, for example if vm is scheduled for provision it will be presented a 'run ks now'

and after provision it reboots and will get new pxe menu, with 'local boot'

oh shoot havent done that

thanks for the heads up!

gosh im in the freakn dark ages here

lol

or maybe twice, like provision with ks, and then finish provisioen (AFAIR) and maybe second reboot (depends on the setup)

ore more thing, make sure vm has enough ram, AFAIR current dracut images require 2GB

but better check it out

yeah that was one of my original issues

same as minimal disk size

though recently I had issues with lvm thin provision and anaconda going mental if not provided with proper %pre script

so i think i want to pxe ks on first boot then manage with puppet after that.. am i missing something?

not sure how to set pxe-boot based on vm state..

you don't have to mess with vm in any way

it should be always booted via pxe

foreman will handle the rest

that is, feeding it proper adjusted grub/pxelinux to execute initial provision or to boot form local disk and run second stage of provisioning

are you goin gto be on tomorrow?

i have to continue this adventure to tomorrow

2 minutes to miiiidniiiiigt!!

ftyninjas maybe

either way ill be here maybe someone else can point me in the right direction if i get lost