search

rundeck-plugins / ansible-plugin

Ansible Integration for Rundeck
MIT License
333 stars 100 forks source link

Ansible File Copier configuration not being saved #149

Open martinbydefault opened 7 years ago

martinbydefault commented 7 years ago

The changes in the configuration of the plugin Ansible File Copier aren't saved.

I'm using rundeck 2.8.1-1 and last release of this plugin (2.2.0, but this also happened in 2.0.2) and I have the following problem.
When I go to Project configuration -> Simple Configuration, in the last configuration item: Default Node File Copier, after selecting Ansible File Copier and setting some parameters (in my case I only set: SSH Authentication type, SSH User and SSH Key File path) and hitting the save button, the changes aren't saved.
The only change that is made is the Default FIle Copier option is changed to Ansible File Copier but nothing else.
Also If I go to Edit Configuration File the only thing that changed is: service.FileCopier.default.provider=com.batix.rundeck.plugins.AnsibleFileCopier

Anyhow, I'm not using this option because I still get to copy files in my playbooks, but I think this problem affects the Copy File plugin if I wanted to use as a step it in a workflow.

DerekTBrown commented 7 years ago

Are there errors in the rundeck log?

DerekTBrown commented 7 years ago

@martinbydefault also, if you edit the xml manually, is that saved?

martinbydefault commented 7 years ago

I checked the logs in journalctl and rundeck.log file and I didn't see any error.
If I edit the xml manually (using the "Edit Configuration File" button) the changes are saved, I did this with other fields (not related with the file copier plugin), but the problem is that I don't know what are the fields related to the Ansible File Copier plugin.
I tried to inspect the plugin code but I didn't figure out what are the name of the fields I should edit, for example to set: SSH Authentication type, SSH User and SSH Key File path.

mariuspana commented 3 years ago

I can confirm this is still present with rundeck 3.3.8 and the latest ansible plugin 3.1.1.

Anyone know what the configuration should look like? I need to specify for it to use priv escalation with sudo.

diginote commented 3 years ago

I can confirm that bug also

Does anyone have a solution?

joe-speedboat commented 2 years ago

I can confirm this issue still exists with: OS: Alma Linux8 Rundeck: 4.3.1 RPM Setup Ansible Plugin: 3.1.1 Ansible: core 2.12.3 (pip3 setup as rundeck user)

Does anyone have a solution or workaround to this issue?

kaintaozia commented 1 year ago

Issue Stil present in Rundeck 4.14.0 ansible 2.10.17 ansible-plugin-3.2.5

wwilkins-intlog commented 5 months ago

This is still a bug in v5.4.0-20240618