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.
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
This is solved upstream in https://github.com/puppetlabs/puppet/commit/1d65d0780ec87a1f66d4e1a92669299d1ea01f62 and landed in puppet-agent 7.17.0. (In reply to Vedashree Deshpande from comment #0) > As a workaround have copied the unit to /etc/systemd/system and overridden > the constraint to: > After=network-online.target For future reference, it's recommended to use drop in configurations. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/assembly_working-with-systemd-unit-files_configuring-basic-system-settings#proc_extending-the-default-unit-configuration_assembly_working-with-systemd-unit-files describes this.
*** Bug 2213207 has been marked as a duplicate of this bug. ***