Re: [foreman-users] Re: [Katello] Katello 3.1 to 3.2 upgrade error

2017-02-03 Thread Edson Manners
Thanks for replying Stephen. Here's what I found: [root@katello3 puppet]# rpm -q --whatprovides /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/storeconfigs.rb puppetdb-terminus-2.3.8-1.el7.noarch So maybe PuppetDB was the culprit. And yes even though I read in a Katello 3.2

Re: [foreman-users] Re: [Katello] Katello 3.1 to 3.2 upgrade error

2017-02-03 Thread Stephen Benjamin
On Fri, Feb 3, 2017 at 2:36 PM, Edson Manners wrote: > Just an update. It looks like the candlepin migration was looking for Puppet > 4 and not Puppet 3. I can't seem to find any 'foreman-install' arguments > that indicates that you'd like to stick with Puppet 3. So if

Re: [foreman-users] Excessive looping while loading host edit page

2017-02-03 Thread Stefan Lasiewski
Chris, I don't know about you, but this command was showing about 1500 interfaces for Docker named 'vethNNN': $ hammer --output=csv host interface list --host docker0N.example.org |wc -l That not right, and `ip addr show` only shows about ~25 interfaces on each host. I suspect that

[foreman-users] Re: [Katello] Katello 3.1 to 3.2 upgrade error

2017-02-03 Thread Edson Manners
One last update. I created a soft-link from /opt/puppetlabs/puppet/cache/foreman_cache_data/candlepin_db_password to /var/lib/puppet/foreman_cache_data/candlepin_db_password That made the candlepin_migrate complete successfully but I got a bunch of errors in xxx that broke Katello. These are

[foreman-users] DNS records for hosts without DHCP

2017-02-03 Thread Louis Hather
Is DHCP the only way to make foreman automatically update DNS records? I see that foreman gets the IP address, regardless of how it was assigned. If foreman does not have this capability, could someone please direct me to the line of code that calls the dns update module? As a side

Re: [foreman-users] Excessive looping while loading host edit page

2017-02-03 Thread Chris Baldwin
Nice, I hadn't noticed that. If that's the case, this should be a non-issue for us in the long term... once we upgrade :) On Thursday, February 2, 2017 at 6:29:37 PM UTC-5, Stefan Lasiewski wrote: > > How funny. I was just looking this up also. Also running Puppet 3.8 & > Foreman 1.12.x, and a