Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rundeck Plugin Options type prevents saving of node step #4109

Closed
cjmcken opened this issue Oct 11, 2018 · 4 comments · Fixed by #5302

Comments

@cjmcken
Copy link

commented Oct 11, 2018

Issue type: Bug report

My Rundeck detail

  • Rundeck version: 3.0.7-20181008
  • install type: rpm
  • OS Name/version: centos 7
  • DB Type/version: mysql

I've created a rundeck plugin (in java) with a Property of type "Options", when I then go to save the step inside of the rundeck UI I get an error 500 Server Error with the following stack trace in it:

Class
groovy.lang.MissingMethodException
Message
No signature of method: [Ljava.lang.String;.replaceAll() is applicable for argument types: (java.lang.String, java.lang.String) values: [\r?\n, ]

Line | Method
666 | doCall in rundeck.controllers.WorkflowController$_cleanLineEndings_closure20

How to Reproduce
This can be reproduce by creating a rundeck plugin in java and having a property with the type "Property.Type.Options".Then you need to install the plugin and create a job with this as one of the steps. Upon trying to save if you open up the developer console you will notice that the request cannot be made to the backend correctly and throws a server error (code: 500)

@sjrd218

This comment has been minimized.

Copy link
Contributor

commented Oct 17, 2018

@cjmcken Looks like a bug with the Options property type. Can you use FreeSelect instead?

@sjrd218 sjrd218 added the bug label Oct 17, 2018
@cjmcken

This comment has been minimized.

Copy link
Author

commented Oct 17, 2018

@sjrd218 For the minute I've been using a String field and using it as a comma separated value using validators

@mergeable

This comment has been minimized.

Copy link

commented Jan 20, 2019

There haven't been much activity here. This is stale. Is it still relevant? This is a friendly reminder to please resolve it. :-)

@skywalke34

This comment has been minimized.

Copy link

commented Jul 5, 2019

Confirmed this is still an issue in 3.1.0-SNAPSHOT 06-24-2019. Using a single value for the Options type will allow the workflow step to save. However, using >1 values throws an exception error and will not allow you to save the workflow step.
image

@sjrd218 sjrd218 self-assigned this Sep 24, 2019
@sjrd218 sjrd218 added this to the 3.1.2 milestone Sep 24, 2019
@jessemarple jessemarple added the v3.1.2 label Sep 26, 2019
@jessemarple jessemarple removed this from the 3.1.2 milestone Sep 26, 2019
@gschueler gschueler closed this in 77d73c9 Sep 27, 2019
@gschueler gschueler added this to the 3.1.2 milestone Sep 27, 2019
mergify bot pushed a commit that referenced this issue Oct 10, 2019
…om the ui and saved.

(cherry picked from commit 77d73c9)
sjrd218 added a commit that referenced this issue Oct 16, 2019
…om the ui and saved.

(cherry picked from commit 77d73c9)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.