#theforeman

rimma: what kind of timeout?

linux-ninja: i have, wouldn't say i do it regularly

jsherrill: Unable to verify server's identity: timed out

rimma: did a task get created in the UI?

yes, it did

rimma: how long did it take from start to finish?

ActiveRecord::RecordInvalid: Validation failed: Interfaces some interfaces are invalid

oh it errored?

hello, is there a way to bulk "Change domain" for hosts ? after migration of Satellite 6.1.9 to 6.2, i've to udpate the domain for all of my hosts :/

jsherrill: yes, it errored, but i can't determine which interface and what might be wrong with it

We migrate vcenter from a previous build into a newer one, now provisiong appears to be broken

rimma: can you send me the output of subscripion-manager facts ?

jsherrill, any clues as to what might be causing the issue

linux-ninja: not my expertise, sorry

rclsilver: likely through hammer

jsherrill: http://paste.fedoraproject.org/397310/69803054/

I am trying to use Pulp 2.9.x to setup the repositories for foreman 1.12 ... has anyone else messed with that?

Whenever I try to provision a VM I am getting the following error

422 Unprocessable Entity: {

"error": {"id":null,"errors":{"base":["Could not find virtual machine network interface matching eth0"]},"full_messages":["Could not find virtual machine network interface matching eth0"]}

I added foreman and foreman-plugins for 1.12 ... but the foreman-release-scl RPM doesn't have any repo files?

TommyTheKid: it depends on centos-release-scl{,-rh} which do

oooh

What could be causing this issue?

linux-ninja: I can't answer precisely with regard to vSphere, but the error means that the network interfaces on the created VM don't match the ones that it intended to provision - either some are missing, or on the wrong network or similar.

linux-ninja: if you enable debugging (http://theforeman.org/manuals/1.12/index.html#7...) then you should get an entry "Trying to match network interfaces [..]" with info about the interfaces on the created VM

Dominic: do the RPM GPG keys change for each release?

TommyTheKid: yes, https://theforeman.org/security.html#GPGkey has a list

and they should be in each release dir on yum.tf.org

Dominic, it looks like we are hitting this bug. Bug #11106

Dominic: #11106 is http://theforeman.org/issues/11106 "Bug #11106: Foreman 1.8.2 with VMware errors with: Could not find virtual machine network interface matching x.x.x.x - Foreman"

ok, at least that makes sense, I was like, but I HAVE the freaking key already

rimma: hrmmm, give me a bit, i've got a meeting in about 10 minutes will investigate more afterwards

Reference: http://projects.theforeman.org/issues/11106

jsherrill: thanks

Dominc, we might have hit a bug that might impact many people that patch and keep vcenter on the newer builds.

I'm having some trouble with a hook. I have a hook installed under ~foreman/config/hooks/host/managed/after_build but its not being executed. When i check the production.it tells me it has finished discovering 1 hook but that takes a while after issuing the build. Any suggestions about what could be causing this?

Im using foreman 1.11.3 btw.

Is there a rake task in the Foreman to export our all hosts YAML file as see on the Host page?

maybe a script/hammer

makudaku: no, but there's usually a cache on the puppetmaster

have a look in /opt/puppetlabs/server/data/puppetserver/yaml/node or similarly in /var/lib/puppet for puppet3

i'm getting an error trying to view certificates on my (only) smart proxy: "Failure: ERF50-5345 [Foreman::WrappedException]: Unable to connect ([ProxyAPI::ProxyException]: ERF12-5356 [ProxyAPI::ProxyException]: Unable to get PuppetCA certificates ([RestClient...)"

and i've fully restarted katello-services, too.

i'm getting an error trying to view certificates on my (only) smart proxy: "Failure: ERF50-5345 [Foreman::WrappedException]: Unable to connect ([ProxyAPI::ProxyException]: ERF12-5356 [ProxyAPI::ProxyException]: Unable to get PuppetCA certificates ([RestClient...)"

i discovered that i accidentally killed /etc/sudoers.d/foreman-proxy, so i put it back. but it still isn't working.

proxy.log says: "Failed to list certificates: Execution of puppetca failed, check log files"

and i've verified that the sudo command by foreman-proxy is executing properly.

at least, it can if i change the foreman-proxy shell to bash, switch users, and run the sudo'ed command myself.

when i try to load the smartproxy page, nothing shows up at all in /var/log/secure -- no sign that it's even trying.

how can I rename my foreman server?

what does subscription-manager use to determine the hostname?

all of a sudden a couple of my hosts will only register with shortname.

brentg: i uses a python library, which i think in the end grabs the output of 'hostname'

subscription-manager facts do indeed show fqdn.

ok, weird things are happening. besides the smart proxy cert issues, this is now the third time today that my server has just stopped responding on port 443.

huh, at least this time it came back on its own.

is there a way to get puppet to run on a client under rvm?

brentg: what for