-
**Describe the bug**
When we do a takeover with rundeck API, job is executed on both rundeck nodes
**My Rundeck detail**
* Rundeck version: 4.16.0
* install type: deb
* OS Name/version: Ub…
-
Not sure if this is the right place, in case if not please let me know.
We´re using an Ansible Resource Model Source with netbox as inventory.
As soon as I adjust the filter the Windows nodes ar…
-
**Describe the bug**
Execution notification variables are not filled correctly after a job timeout. Nodes where the job didn't have time to run appears in the "${execution.succeededNodeListString}" t…
-
**Describe the bug**
A clear and concise description of what the bug is.
Don't know the exact order or cause:
RWX volume is detaching causing attached pod to restart, restarted pod is unable to…
eckra updated
3 years ago
-
Hi
I just setup a new server to be able to run ansible 'natively' from rundeck.
I have set up a project only for my windows machines.
I setup the executor, file copier and node source to use …
-
Evicted POD's do not have a status and therefore the PODs resource model is not able to iterate over them. This causes it to fail and return an old cached set of PODs'
https://github.com/rundeck-pl…
-
**Description**
The JSON path filter described in the [documentation](https://docs.rundeck.com/4.14.1/manual/job-options.html#json-format) does not return the intended key-value pair, but the root ke…
-
Hi,
I have a puppet entreprise 3.3.2 on a linux box. Another box with a puppet entreprise agent and rundeck 2.0.
I install puppet-rundeck in puppet env:
# /opt/puppet/bin/gem install puppet-rundeck
…
-
I have installed 1.5.2 on 2.6.6 and am not seeing any nodes populating.
I tried a false key and received and error. Fixed it, no nodes.
I checked the key is authorised to run describe-instances
And …
-
3.3.6
**Is your feature request related to a problem? Please describe.**
The default job output in email notification doesn't have proper format:
![Sin nombre](https://user-images.githubuserconte…