#theforeman

Hey all, having a problem finding information online for a problem I'm having. Details here: http://pastebin.com/Gbx4Ze70

PXEprobs: and what are the permissions on the boot dir?

gwmngilfen: drwxr-xr-x 2 foreman-proxy root 73 Apr 29 15:58 boot

worth a try :)

Sorry, grabbed the whole line

sure np

hmm, so the client can get the mac file and not the kernel

oh i see it

typo

The closest thing I found was someone saying that they were showing a size of 0, and he had to wget the files

you're getting vmlinuX but your file is vmlinuZ

i assume thats just in your pastebin

ah yes, zero-size files, i missed that

that'll be it

sorry, that typo is just me. Had to grab that from the client I couldn't copy past from :)

you get that when the proxy can't download the initrd/vmlinuz files

So one person said he could wget the files, but then another page said never write the files in yourself. So I was a little gunshy.

you can just delete them and toggle build state to have the proxy retry (and maybe tail the logs)

oh that's it... I know for a fact that my firewall probably stopped that

if that doesnt work, it's fine to supply your own (and which page said you shouldn't, out of interest?)

That would have resulted in it creating the files at a size of 0, right?

let me see if I can find that tab

yes, if the wget fails for any reason it'll leave zero (or larger) files behind

it's using wget -c in the background for good reasons but this is a side effect

https://www.redhat.com/archives/rhos-list/2013-... this is the page that had that info. It references https://www.redhat.com/archives/rhos-list/2013-... which was close to my exact issue so for better or worse I put a little more weight behind it :/ but thanks for the info!

fair enough, so long as it's not one of our pages :)

nope. that was my problem hahaha

Have a good night!

you too ;)

I'm having an issue with the foreman proxy giving a "No client SSL certificate supplied" after I try to do a simple curl -k https://foreman-proxy:8443/features

The cert is valid if I do an openssl s_client -connect

The foreman application was able to connect to the foreman-proxy to see it's features. When the discovery image boots it's failing with the same error.

krizzo: you have to supply a cert with the --cert and --key options to curl

try it with foreman's own key/cert (default to /var/lib/puppet/ssl iirc)

gwmngilfen: Interesting that worked from the foreman app server using it's keys but failed on the localhost foreman proxy due to the trusted hosts. Yet the localhost works on another foreman proxy that is setup the same way as this foreman-proxy with it's trusted hosts.

is it an older proxy?

Nope same version. Thought I just tested it again and now it's not working. There must be a setting that was changed manually that I didn't know was changed.

that would also explain it ;)

I know another team member was refreshing our certs could be related.

Thanks

np

Can I search all of my Foreman reports for a particular string?

when you tell foreman to create a new VM in VMware, what is it using under the hood?

is it just fog or is there some other voodoo?