New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DEBUG statement "Passing on Saltutil error. This may be an error in saltclient." appearing while waiting for provisioning to finish on Windows. #38538
Comments
@chatterbeak the only time i'm able to replicate this is if the minion is not running and attempting to make a call to the minion for example (salt '*' test.ping -ldebug). Looking at the change in this pr: #35446 it seems it checks for ping @cachedout looks like you had a fix in mind to ensure we only enter the block if retcode is present. I'm not seeing if this ever was added or not so not sure if you still want to add this or are intentionally leaving that keyerror exception in there. |
Thanks. I'm configuring a test box that has minion and master running on one box. I haven't tried other configurations because this is our standard test configuration. |
I am having a similar issue but not sure if its directly related to this: During the VM deployment salt enters into a neverending loop: root@sjociara03:/srv/salt# salt-run -l debug virt.init centosTEST 4 2048 salt://centos6-base.img |
I'm running in the same problem. At the end the call is finished and done fine. But I think there is a loop about 4 times which logs on saltmaster with "Passing on saltutil error. This may be an error in saltclient. 'retcode'" On the requested minion I found no errors. May be I don't interpret them as errors.. Both, master and minion are 2016.11.3 (Carbon) I've the following state file which is provided with file_roots on the master :
On my master I start :
As you can see the plain runtime is about 20ms. But the real runtime is about 44 seconds. On my minion side the following debug output is written. At least at timestamp "2017-03-09 16:40:46,188" starts the real action.
I have no clue what the minion is doing before the real action. It looks for me that it hungs a while or do nothing. On the other hand the logging output from the master irritates me : Passing on saltutil error. This may be an error in saltclient. 'retcode' I hope to find here some help. The calls needs to long to run. regards, Tom |
I'm seeing the same message, "This may be an error in saltclient. 'retcode'". Difference from above, I'm operating purely in a CentOS environment right now. I'll note that there's a delay right around each occurrence of it, which leads me to suspect a timeout is in play, possibly a firewall, DNS or other network issue that gets worked around somehow. Everything continues and finishes, so it's frankly the 'retcode' that annoys me; I can't quickly drill down without an actual error code to work with. |
I'm also getting this message in a case where I'm running Carbon salt-master on a CentOS host and Carbon salt-minion on a Windows Server 2012 host. May only be a manifestation of a deeper problem, but it's interfering with my troubleshooting. |
I'm on Cent7 for my testing with Salt 2016.11.4 and seeing this too. |
I'm seeing this with the latest Salt packages available for Debian Stretch ( on the minion
on the master:
Unfortunately I have to way to check newer versions until vmware-archive/salt-pack#183 is fixed. The result is that the master hangs while looping waiting for the job to return. |
I see this issue on salt- version 2016.11.4 and sles12 |
I have the same issue on salt 2016.11.2 on CentOS 6.8, Windows 10 minion running 'salt -l debug winminion state.highstate' |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Description of Issue/Question
While waiting for a (successful!) provisioning of a VirtualBox Centos machine on a Windows 10 host environment we see this message dozens of times:
[DEBUG]"Passing on saltutil error. This may be an error in saltclient. 'retcode'
The full context of how this appears is this:
Everything completed OK. It seems harmless, but it is a relatively new behavior so I thought I'd raise it as an issue because apparently some developer wanted to note when this happened.
Setup
(Please provide relevant configs and/or SLS files (Be sure to remove sensitive info).)
Windows 10 host. Using Vagrant to start salt. Running Salt Minion and Master on one Centos/7 Virtualbox VM that was booted with Vagrant and provisioned with saltstack. Using Powershell.
The same setup works on a Mac host and we don't see the
[DEBUG ] Passing on saltutil error. This may be an error in saltclient. 'retcode'
statement
Steps to Reproduce Issue
(Include debug logs if possible and relevant.)
Bring up a saltstack provisioned master/minion instance on Virtualbox with a Windows 10 host. We see this on all our projects.
Versions Report
(Provided by running
salt --versions-report
. Please also mention any differences in master/minion versions.)Last login: Tue Jan 3 19:53:28 2017
The text was updated successfully, but these errors were encountered: