Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: ansible-plugin
-
Labels:
-
Environment:- Jenkins ver. 2.110
- Jenkins ver. 2.180
- ansible-plugin ver. 1.0
-
Similar Issues:
Description
After checking on become, it does not seem to be reflected even if apply.
- Build - Invoke Ansible Ad-Hoc Command - check become
- add become user like 'tomcat'
- Apply
- Job - Configuration
- uncheck become
step1~3)
step4~5)
Attachments
Activity
Yes, the problem still exists. Can somebody check this and fix?
Emil Wypych
added a comment - Yes, the problem still exists. Can somebody check this and fix? Hi,
this bug is sill around, the only workaround we've found was to add the -b parameter to the Additional parameters in the Advanced section.
Dennis Philpot
added a comment - Hi,
this bug is sill around, the only workaround we've found was to add the -b parameter to the Additional parameters in the Advanced section. 
I have the same issue with Ansible Plugin version 1.0. I use in Jenkins ver. 2.180.
Please can you fix it ?
Thank you very much.
Best regards,