Salt-master pod (on bootstrap node) not starting if salt-minion failed to start #3022
Assignees
Labels
complexity:easy
Something that requires less than a day to fix
kind:bug
Something isn't working
priority:medium
Medium priority issues, should only be postponed if no other option
severity:medium
Medium impact (usability) on live deployments
topic:operations
Operations-related issues
Comments
thomasdanan
added
topic:operations
TeddyAndrieux
added
the
complexity:easy
TeddyAndrieux
added a commit
that referenced
this issue
Jan 14, 2021
Salt process create a `/var/run/salt` directory at startup this directory is shared between salt-master container and salt-minion running on the host so it's mounted in the container, since this directory does not exists at system boot we need to use `DirectoryOrCreate` so that salt-master does not need salt-minion to start before being able to start Fixes: #3022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component:
'salt', 'bootstrap'
Why this is needed:
If for some reason, salt-minion service failed to start on
bootstrapnode, the podsalt-masterwill fail to start with the following error:Warning FailedMount 4s (x12 over 8m18s) kubelet MountVolume.SetUp failed for volume "run" : hostPath type check failed: /var/run/salt is not a directory [root@zenkotda-bootstrap scality]# systemctl restart kubeletWhat should be done:
salt-master pod should be able to start even if salt-minion is not running (i.e.
/var/run/saltis not available)Implementation proposal (strongly recommended):
Test plan:
The text was updated successfully, but these errors were encountered: