javascript problem: Can't change nodes when trying to run a saved job

[gschueler]

Re-opened from Lighthouse issue 538

When trying to run a saved Job, there's the "Nodes" section, and a checkbox for "Change the Target Nodes", and a "Matched Nodes" rollup. If you expand "Matched Nodes", you see the matched nodes with greyed out checkboxes that cant be changed, and checking "Change the Target Nodes" doesn't change anything.

I would expect to be able to deselect existing matched nodes, and by checking "change", change the filter for nodes, but neither appears to be the case.

If you check "Change" and the "Run Jobs Now" button, you get a running job status screen that reports "failed" and has the one output line:

Step 1 of the workflow threw an exception: No nodes matched,Caused by: No nodes matched

Reproduce:

1. Select a saved job
2. Expand the "Matched Nodes" section, see that the checkboxes are greyed out.
3. Click to mark "Change the Target Nodes", note that the matched nodes checkboxes don't change
4. Click the "Run Jobs Now", see the error on the resulting page.

---

Reopened by Craig Smith, July 20th, 2012 @ 03:47 AM:

Hi,
I still seem to have the problem. I'm using rundeck 1.4.3 and see the checkboxes are greyed out on IE9, Chrome 19 and Firefox > 13 on Win 7.
Any ideas?

[noodle10000]

Greg Schueler
July 20th, 2012 @ 10:53 AM

do you get any errors in the javascript console?
also, do you mind continuing this on github, we have migrated the issue tracker there.
i created a new issue for 1.4.3 here: #194

Hello,

no errors in the javascript console on any of the browsers :-(

Rgds,

Craig.

[noodle10000]

Actually I just found that if I set a tag in my resources.xml, 'change target nodes' now works. Previously I had lines with tag="" in resources.xml.

[dsummersl]

Ditto for me - once I defined a tag I could check/uncheck items (using chrome)

[gschueler]

ok, good clues to fixing it then. my guess is the javascript in the page is not working if the node has tag="", and needs to handle that case