David Murphy

Closing this, since it appears to be fixed, please reopen if other points to raise

The salt-master's configuration file only contains **_log_level_logfile: debug_**, all git fs settings are in raas, and this appears to be sseapi related. Will talk with raas team to investigate this...

Have a new master log file with the lock error's. I am seeing a large number of Traceback errors in the file due to jinja2 rendering errors, this may be...

See probable cause, for example: process 50973 obtains a lock but never releases it, and gets killed, SIGTERM, and then another process attempts to obtain lock but finds process 509732...

The current testing for gitfs is only relying on _master_lock, and exercising it ``` _master_lock = multiprocessing.Lock() ``` and use acquire and release. this doesn't really test the locking in...

Have changes and tests in PR https://github.com/saltstack/salt/pull/65937 for handling GitFS lock files, and droppings from when the process is terminated, getting cleaned up.

in https://github.com/saltstack/salt/issues/65264#issuecomment-1737765147 @barneysowood mentioned using debconf to prompt for a user, (even with defautls etc.) , not going to do, since too many existing installations which would have issues with...

@OrangeDog Don't control users, so **should** and **do**, two different things :)

@alexholodak python not being available, and having to use python3 is very much an OS issue, for example: arch has python has python3, but older OS's got rid of python...

@lee-harmonic Can you check if the problem occurs with user: root as previously mentioned, it would help a lot in identifying the cause.