Salt-minion running as my user cant access network drive mounted by my user[BUG]
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description
I have mounted a network drive on my windows 2019 server. I did this through the gui with my user which is an administrator.
On my salt master i have tried to list the contents of this mounted drive simply using the this:
"salt MY_MINION cmd.run "ls W:/" shell=powershell"
This command reports
Cannot find drive. A drive with the name 'W' does not exist.
This same drive does exist if i log onto the server as the same user salt-minion is running as.
Setup
(Please provide relevant configs and/or SLS files (be sure to remove sensitive info. There is no general set-up of Salt.)
Please be as specific as possible and give set-up details.
salt version: 3007.0 (Chlorine) on master and minion.
Master OS rocky linux 9
Minion OS Windows Server 2019
Steps to Reproduce the behavior
Mount a network drive on salt minion machine. Attempt to execute remote command from master on the minion using the mounted drive.
Expected behavior
Should be able to access the network drive.
Additional context
I also tried to create the network mount from cmd by executing a remote command from the master using the "net use" command. which gives the error:
System error 67 has occurred.
The network name cannot be found.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported salt MY_MINION cmd.run "ls W:/" shell=powershell command on Windows Server 2019, comparing it with the same user's interactive session. Investigate the execution context used by the salt-minion and the reported net use failure; done means the mounted network drive is consistently accessible through remote execution or the limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100