Bug 2015117

Summary: salt-minion does not connect to the master at boot
Product: [Fedora] Fedora Reporter: Ian Collier <imc>
Component: saltAssignee: Bryce Larson <brycel>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: brycel, david-dm.murphy, frederic.pierret, kp
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-07 20:14:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
brim with no yankee kirya.demid: review?

Description Ian Collier 2021-10-18 12:26:51 UTC 
Description of problem:

Salt-minion is not connecting to the Salt master at boot time and
remains unresponsive until the daemon is restarted.

The systemd unit for salt-minion says "After=network.target" but not
"After=network-online.target".  So the daemon is started in parallel
with the process which negotiates the network (which is managed by
NetworkManager and is configured to use DHCP) and comes up before the
network is ready.

"systemctl status salt-minion" says this:

Oct 18 12:53:05 tw01 systemd[1]: Starting The Salt Minion...
Oct 18 12:53:05 tw01 systemd[1]: Started The Salt Minion.
Oct 18 12:53:06 tw01 salt-minion[2875]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Oct 18 12:53:06 tw01 salt-minion[2875]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds

...but the current time is 13:20 and this "retry in 30 seconds" never
happened.

If I now restart the service while the system is online, it initialises
successfully.

Version-Release number of selected component (if applicable):
salt-minion-3003.3-1.fc34.noarch
Comment 1 kirill 2021-12-23 23:03:29 UTC 
Created attachment 1847642 [details]
brim with no yankee
Comment 2 Ben Cotton 2022-05-12 15:00:30 UTC 
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 3 David Murphy 2022-05-12 16:25:28 UTC 
Have Salt Issue tracking this problem for RHEL 8 too https://github.com/saltstack/salt/issues/60490
Issue is being addressed.
Comment 4 Ben Cotton 2022-06-07 20:14:15 UTC 
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.