After upgrading to foreman 1.10, our provisioned VMs seem unable to download their kickstart file. There isn't much in the logs, even with debug turned on, but this is what it looks like: http://pastebin.com/pxxdrV9Y
toi joined the channel
dcaplan joined the channel
hmw has quit
chrispeters is now known as chrispeters|away
chrispeters|away is now known as chrispeters
blackjid joined the channel
aevans joined the channel
Capesteve joined the channel
Guest74_ joined the channel
m_clarkson78 joined the channel
ichimonji10|afk is now known as ichimonji10
m_clarkson78 has left the channel
shimshtein has quit
RobertBirnie joined the channel
oddjob
has anyone seen an issues with Run Puppet, where it wont work on new hosts until the 2nd-3rd try?
"POST /run HTTP/1.1" 500 will always occur for me the first 2-3 tries
sometimes only 1 try, but ALWAYS on the first
beav
is there any log message related to the 500?
oddjob
activemq - java.io.IOException: Connection reset by peer - yet if i watch the host, I can see the port connect, stay established and even accept the first incoming packet
although i dont get the java.io error each time. but i almost always get the 500 failure
is there anything else to check for logs aside from activemq, proxy, production, messages, mcollective? it always tells me to check log files but never says what lol
ada
im using foreman 1.10.2 and im seeing a problem whre my foreman processes start to chew up 100% cpu, even though it doesn't look like foreman is doing any extra work. strace shows tons of calls to mprotect()
if I kill the process and restart foreman it doesn't appear to do this until after 20-30 minutes
LzrdKing
oddjob: sometimes i get a reporting error the first run
oddjob
LzrdKing: first run would be better, not perfect, but this fails on new hosts 2-3 times before it works. i have no idea if its remote, local, network, java, activemq, mcollective, puppet or foreman. my god so many working parts
failed to execute puppetrun: ERF12-4252 [ProxyAPI::ProxyException]: Unable to execute Puppet run ([RestClient::InternalServerError]: 500 Internal Server Error) for proxy
I just happened across that about a minute and a half ago
jtomasek_ joined the channel
jtomasek_ has quit
g2unix- joined the channel
mbacovsk joined the channel
g2unix has quit
ehelms is now known as ehelms-brb
agoldboi has quit
bbuckingham-afk is now known as bbuckingham
kybaker has quit
LzrdKing
hosts won't break if i remove them from foreman, right?
lphiri has quit
chudler joined the channel
jforeman joined the channel
jforeman
Hello, I am using Foreman with oVirt as a compute resource. When I create a VM, it is created as “Thin/Dependent” on the source template. I would like for it to be created as “Clone/Independent.” Essentially a disks.clone=true parameter needs to be added to the VM upon creation. I have found examples on how to do this with the REST and Python APIs, but can not figure out how to do it with Foreman. Does anybody know how I would add a parameter
such as this?
mhulsman joined the channel
rplevka has quit
jforeman_ joined the channel
jforeman has quit
jforeman_ is now known as jforeman
g2unix- is now known as g2unix
acidrainfall
LzrdKing: They shouldn't break, as long as it doesn't delete the VM, you just erased them from Foreman's database. That means the next time Puppet runs it will create a new host entry.
g2unix is now known as Guest66631
you will lose class assignments, notes, hardware/VM association information, etc.
And the reports, I think.
radiocats joined the channel
LzrdKing
uh huh
toi joined the channel
except, as discussed in #puppet, they are managed
so i just wiped out a slew of test mahcines
im gonna go tell my boss
acidrainfall
:( Sorry man
I'm sure we've all made that mistake haha
LzrdKing
i'm just gald i didn't let foreman see the production tenant