Description of problem:
In the default systemd unit puppet.service the following constraint is configured:
After=network.target

However in a case where a teaming interface takes longer to come up, the puppet run starts before network is available and thus can't gather accurate facts.

As a workaround have copied the unit to /etc/systemd/system and overridden the constraint to:
After=network-online.target

Version-Release number of selected component (if applicable):
Satellite 6.9

Actual results:
1.) Without network-online there is no point in puppet agent running, since it can't reach the puppet master anyway, so why not wait?
2.) When puppet facts are used in the puppet run and can't be gathered accurately, this falsifies the run's outcome and thus causes configuration issues.