-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
windows_service resource prints ruby warnings from win32-service gem #7335
Comments
This was fixed in win32-service here chef/win32-service@7b1720f. We just need to get that gem released and then bump our dep to fix that. Thanks for the report @flakzilla. These are annoying and easy to get rid of. |
Well enough. We'll keep an eye on this and update to the newer client version when it becomes available. I can confirm the issue is still present in 14.2. Speaking of, the 14.2 client spits a bunch of these out unexpectedly:
Do you want another bug report for this? |
That last one we already have a fix for. It's in master and that'll get resolved with 14.3's release. |
Sounds good to me. Thanks for taking care of it. |
Resolved by #7405 |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
We are in the process of upgrading from chef-client 13.x to 14.x. We encountered an unexpected behavior in the 14.x client where the windows_service resource prints out a bunch of warnings from the win32-service-0.8.10 gem. The warnings all deal with one particular service (CDPUserSvc) which apparently is checked each time the windows_service resource is used in a recipe. As far as I can tell, these warnings are just warnings and don't actually cause the windows_service resource to not work properly. It's an annoyance to see the warnings in the run output though, makes it much harder to read the logs or STDOUT of a chef run quickly.
Chef Version
chef-client 14.1.12
Platform Version
Windows Server 2016 (long term servicing build 1607, w/ desktop experience)
Replication Case
Client Output
Stacktrace
No stacktrace, the issue does not result in an error condition.
The text was updated successfully, but these errors were encountered: