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
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
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*
triggering it. Even a simple race condition should result in some successes
if Lave
Disabling NetworkManager hasn't caused any issues for me so far. That said,
EL7.3 might break that, so Fedora may already be broken.
Trevor
On Tue, Mar 28, 2017 at 9:00 AM, Rob Nelson wrote:
> That wiki page says that all you should need to do is have NetworkManager
> or systemd-networkd servic
That wiki page says that all you should need to do is have NetworkManager
or systemd-networkd services enabled. Do you by any chance have them both
disabled on the affected node? I know many of us don't like NetworkManager,
but disabling it entirely can cause some problems. Just a guess, as I
haven
This does seem to be the fix that is required both for Fedora and EL7.
Trevor
On Mon, Mar 27, 2017 at 11:33 PM, Laverne Schrock
wrote:
> I have a box on which puppet-agent does not start correctly on reboot.
> Well, to be more precise, the puppet-agent starts, but never contacts the
> server.
>
I have a box on which puppet-agent does not start correctly on reboot.
Well, to be more precise, the puppet-agent starts, but never contacts the
server.
$ sudo journalctl -b 0 -u puppet -f
> -- Logs begin at Wed 2017-02-01 18:27:11 CST. --
> Mar 06 12:42:03 localhost.localdomain systemd[1]: Sta
