Description This is similar to the issue described in https://github.com/saltstack/salt/issues/62881

Our configuration management setup runs a state to rename the OS when salt-cloud finishes its cloning of a VM.

In 3004.2 and 3005.x we notice that the state.apply of the startup state in Linux and Windows minions (using minion 3005.x) ALWAYS ends in a message timeout. Consequent state.apply of a state also displays the same message timeout. Sometimes it may work, but thats very very rare and in most cases never.

Been debugging this for several months now in various combinations of the OS versions.

Have tried the 3005 version of RHEL9/RHEL8/Debian 11 as master and all of them end in the same problem. It looks like there is something being missed or some other issue which is being overlooked.

I even tried to use 3006-rc version on the master and that displays the same problem.

Setup The error is this

The minion function caused an exception: Traceback (most recent call last):
  File "salt/minion.py", line 1935, in _thread_return
    return_data = minion_instance._execute_job_function(
  File "salt/minion.py", line 1894, in _execute_job_function
    return_data = self.executors[fname](opts, data, func, args, kwargs)
  File "salt/loader/lazy.py", line 149, in __call__
    return self.loader.run(run_func, *args, **kwargs)

… File “<string>”, line 4, in raise_exc_info File “salt/ext/tornado/gen.py”, line 1064, in run yielded = self.gen.throw(*exc_info) File “salt/transport/zeromq.py”, line 624, in send recv = yield future File “salt/ext/tornado/gen.py”, line 1056, in run value = future.result() File “salt/ext/tornado/concurrent.py”, line 249, in result raise_exc_info(self._exc_info) File “<string>”, line 4, in raise_exc_info salt.exceptions.SaltReqTimeoutError: Message timed out

Please be as specific as possible and give set-up details.

• [ X] on-prem machine
• [ X] VM (VMware Vsphere 6.7 and 7.0)
• [X ] VM running on a cloud service, please be explicit and add details
• [X ] classic packaging
• [ X] onedir packaging

Steps to Reproduce the behavior I can attach the logs when you need. I have the VMs up and running now if you need them. I can even setup a fresh environment to reproduce this and share data if needed.

Expected behavior

We have a salt 3003.x master and minion setup in the same environment and things run without this problem. I cannot understand what has been changed to make this behave this way. I need help to find out what it is.

Screenshots Will attach if needed and provide any other info you may need.

Versions Report

PASTE HERE

Additional context Add any other context about the problem here.

Referring back to https://github.com/saltstack/salt/issues/62881, I want to know what the issue in gitfs the user https://github.com/RobinWlund fixed. I did ask, but never got a reply. If you have an idea on what it is, please do let me know

Thanks for helping