Critical issue with nodefilters

[Xavier Humbert]

Hi,

One of my users reported this (awkwardly translated from the french
ticked he filed to me)

We noticed that node filters do not appear in interface. This problem is
present in PagerDuty Automation as well in Rundeck community. I already
filed a ticket to the PägerDuty support, but perhaps someone here has
some ideas.

Although a job has a node filter defined in a job reference (tab
"override node filter") when you edit the job, it does not appear
anymore in the "node filter" field. Critical impact is that if you save
the job without setting again the node filter, Rundeck considers the
former as empty, and removes the previously set node filter

That means that you can inadvertently remove node filters. Most, you
cannot see the previously defined node filter, you have to download the
job definition (in XML, eg.), where you can clearly see the node filter
in the job ref tag. (see attached job definition)

More, you can see that Rundeck detects the presence of the node filter
in the job ref, as although the node filter appears as empty, the tab
"override node filters" is opened while it is normally closed when no
filter is set. (see attached screenshot)

This is PagerDuty Automation or Rundeck Community 5.11.1, running on
RHEL9, RPM installation

Thanks in advance

Regards,

Xavier

--
Xavier Humbert
CRT Supervision et Exploitation de Niveau 1
Direction des Services d'Information du Grand Est
Rectorat de l'Académie de Nancy-Metz
Ministère de l'Éducation Nationale et de la Jeunesse
03 83 86 27 39

[rac...@rundeck.com]

Hi Xavier,

I reproduced your issue. Looking back to (for example) Rudeck 4.0.0, that filter is kept in the Parent Job filter definition.  Can you open a new ticket here?

Thanks for your feedback!