Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Default value not referenced when using a multi-valued option.

#585
  • Issue Type: Bug
  • Rundeck version: 1.4.3
  • JDK Version: Sun Java 1.6.0_31
  • Server OS: CentOS 5.3

* Install type: Yum-rpm

Issue:

When using a multi-valued option the default value appears to be ignored.

Ex.
Option name: opt1
Default value: val5
Values list: val1,val2,val3,val4

Command: echo ${option.opt1}

Run job without specifying a value for the option.
Output: /bin/sh: ${option.opt1}: bad substitution

Looks like this may be somewhat similar to the behavior seen in ticket #444 Default option filtering not honored from workflow?
#444 Default option filtering not honored from workflow

Reported by Michael Gibson · August 27th, 2012 @ 02:41 PM

State: new
Milestone: none
Assigned to: nobody

Activity

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.