Re: [foreman-users] Puppet platform 5

2017-09-14 Thread Angel L. Mateo
El 13/09/17 a las 16:06, jp10...@gmail.com escribió: With this out, does anyone know if this will be an easier new version support in Foreman, or another long wait to get it functional? I'm using it with puppet 5.1 without any problem, although I'm using foreman just as a report console. --

[foreman-users] Re: Foreman with Puppet in a wildcard domain leads to nodes mistaken identity

2017-09-14 Thread Justin DynamicD
Quick update ... it really DOES look like its a cname thing. setting an ip for the wildcard entry looks to have been ok (unless things just havn't replicated yet). Time will tell. On Thursday, September 14, 2017 at 9:20:48 PM UTC-7, Justin DynamicD wrote: > > So a curious problem was discovere

[foreman-users] Foreman with Puppet in a wildcard domain leads to nodes mistaken identity

2017-09-14 Thread Justin DynamicD
So a curious problem was discovered today and I"m not entirely sure if it's a puppet or a foreman issue, so I figured I'd break out the layout: *The Design* We have a foreman/puppet all-in-one server. It has been setup in the domain samplecompany.com. We are leveraging Foreman as an ENC, so if

[foreman-users] Re: Puppet platform 5

2017-09-14 Thread Justin DynamicD
Fantastic question ... I"m waiting on foreman announcements myself. On Wednesday, September 13, 2017 at 7:06:06 AM UTC-7, jp1...@gmail.com wrote: > > With this out, does anyone know if this will be an easier new version > support in Foreman, or another long wait to get it functional? > -- You

[foreman-users] Lots of "Mysql2::Error: Deadlock found when trying to get lock" under increased load

2017-09-14 Thread 'Konstantin Orekhov' via Foreman users
Hi, all! Under increased load (which comes in spikes), I noticed lots of mysql deadlock errors resulting in failed transactions and incorrectly discovered systems (duplicate and/or empty entries in discovered_hosts I reported in this group some time ago, just can't find those posts for some re

Re: [foreman-users] Re: "No templates were configured" for image builds?

2017-09-14 Thread Mike Wilson
On Tuesday, September 12, 2017 at 1:12:17 AM UTC-5, Ivan Necas wrote: > > In order to be able to assign the template to the OS, you need first > go to the template's associations tab, and add the OS there. > Then it should make it possible to set that in the OS. > Indeed. That was why I attac

[foreman-users] Environment not being inherited from Host Group

2017-09-14 Thread James Denton
Hi I have setup a new environment named "legacy" and set it as the default env for a host group. After adding a number of nodes to the host group none of them inherit this environment instead they default to the "production" environment. Under foreman settings i have these: Default Puppet env

[foreman-users] Auto deletion of HostParameters on Foreman 1.15 causing non-consistent rebuilds

2017-09-14 Thread Jason Unovitch
Good day folks! I didn't see this discussed earlier or see a bug for this just yet. After updating to Foreman 1.15 I no longer saw deterministic builds of my hosts. Turns out "HostParameters" for that host are disappearing when a build call is triggered on that host. This worked on Foreman 1.1