HI, I have the same issue for my Redhat 7 servers (immutable hypervisors). For
some reasons ppuppet.servise unit is not network depended. I don't know what is
it bug or feature. I override dependency for puppet unit to depend on
network.service (I use lsb network service)
--
You received this
I'm guessing those race conditions are related to not replacing it with
something else. Seems they're "magic" components to not requiring reliance
on network-online.target. Hooray :/
Rob Nelson
rnels...@gmail.com
On Wed, Mar 29, 2017 at 9:24 AM, Trevor Vaughan
wrote:
> I just ditched it.
>
> O
So big surprise to me when I'm looking to move our infrastructure from
openldap to freeipa, and having trouble getting puppetserver to talk
to it, when I find there was a reply to my posts that I'd missed. And
sadly, there was no resolution then either.
Yes, jruby-ldap updating their code would b
Excellent. Good to know. I was told otherwise.
Thanks,
Joshua Schaeffer
On Wednesday, March 29, 2017 at 7:11:55 AM UTC-6, Gabriel Schuyler wrote:
>
> Never fear, external facts work just fine in Puppet 3.
>
> On Tuesday, March 28, 2017 at 10:51:52 AM UTC-4, Joshua Schaeffer wrote:
>>
>> External
I just ditched it.
On Tue, Mar 28, 2017 at 9:23 AM, Rob Nelson wrote:
> Did you replace it with systemd-networkd, or just ditch it? Regardless,
> I've updated us to EL7.3 (CentOS though) and not observed this issue, so
> I'm not sure it's that generic of a problem, there must be *something*
> tr
Never fear, external facts work just fine in Puppet 3.
On Tuesday, March 28, 2017 at 10:51:52 AM UTC-4, Joshua Schaeffer wrote:
>
> External facts are a Puppet v4 feature only. You have to use Ruby to
> create custom facts in Puppet v3.
>
> On Monday, March 27, 2017 at 3:54:00 PM UTC-6, Warron Fr
Thank you for that information Joshua !
On Monday, March 27, 2017 at 11:45:54 AM UTC-5, Joshua Schaeffer wrote:
>
> I'm not sure of any time specific settings in Puppet itself. You could
> restore the VM again and then make sure your time settings are correct
> before connecting anything to it.
Hi,
>From my testing it seems that when managing mount resources puppet only
compares the manifest against fstab and not mtab. For example if I have
mount { '/tmp':
ensure => mounted,
options => 'noexec,nodev,nosuid',
}
And then do mount -o remount,exec /tmp
I would expect the next puppet
