Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-54366

Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing

XMLWordPrintable

      Previously we have using tower 3.1.5 with plugins 0.81. We trigger the ansible tower workflow templates with jenkins and pass extra variable inside. it is ok.

      But after we upgrading to tower 3.3.0 with plugins 0.9. It don't work anymore. It show ("Extra variables defined but prompt for variables on launch is not set in tower job") but actually the workflow templates don't have this checkbox whenever in tower 3.1.5 and 3.3.0 (but it work in 3.1.5). I have confirmed that all the job templates have checked the "prompt on launch" before and after the upgrade

          [JENKINS-54366] Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing

          cap ho created issue -

          Casey Motherway added a comment -

          I am seeing the same issue.  Additionally there is a new warning message in the Jenkins Console Output that was not there before:

           [WARNING]: Extra variables defined but prompt for variables on launch is not set in tower job

          We recently upgraded to AT 3.3.1 and Jenkins AT plugin 0.9.0.

          My Jenkins job kicks off an AT Workflow.  The workflow has never had a "Prompt on Launch" option.  The jobs within the workflow do have the prompt option enabled.  In the past, the extra vars passed over by the Jenkins AT plugin have always magically passed through to the Jobs.  Now the vars do not make it through.

          I would consider this to be a blocking issue, not a minor issue.

          Casey Motherway added a comment - I am seeing the same issue.  Additionally there is a new warning message in the Jenkins Console Output that was not there before: [WARNING]: Extra variables defined but prompt for variables on launch is not set in tower job We recently upgraded to AT 3.3.1 and Jenkins AT plugin 0.9.0. My Jenkins job kicks off an AT Workflow.  The workflow has never had a "Prompt on Launch" option.  The jobs within the workflow do have the prompt option enabled.  In the past, the extra vars passed over by the Jenkins AT plugin have always magically passed through to the Jobs.  Now the vars do not make it through. I would consider this to be a blocking issue, not a minor issue.

          Casey Motherway added a comment - - edited

          It seems like this is probably an issue on the Ansible Tower end.  There is a variable on the workspace in the AT API: 

          ask_variables_on_launch

          It is defaulted to false.  After setting this to true via the API my extra vars are now making it from Jenkins to AT and passing through to the jobs.  This should probably be a bug in AT for changing the default behavior, while there is no option in the UI to set it.

          The warning in the Jenkins Console Output went away also.

          Kudos to our amazing IT guy (SD) for figuring this out, and saving the day.

          Casey Motherway added a comment - - edited It seems like this is probably an issue on the Ansible Tower end.  There is a variable on the workspace in the AT API:  ask_variables_on_launch It is defaulted to false.  After setting this to true via the API my extra vars are now making it from Jenkins to AT and passing through to the jobs.  This should probably be a bug in AT for changing the default behavior, while there is no option in the UI to set it. The warning in the Jenkins Console Output went away also. Kudos to our amazing IT guy (SD) for figuring this out, and saving the day.
          John Westcott made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Fixed but Unreleased [ 10203 ]

          John Westcott added a comment -

          Thanks for all of the comments and research on this issue. Since it appears to be an issue in Tower I am going to close this issue out. If you think we need to do more work on the plugin, please let me know and we can reopen the ticket.

          John Westcott added a comment - Thanks for all of the comments and research on this issue. Since it appears to be an issue in Tower I am going to close this issue out. If you think we need to do more work on the plugin, please let me know and we can reopen the ticket.
          John Westcott made changes -
          Resolution Original: Fixed [ 1 ] New: Not A Defect [ 7 ]
          Status Original: Fixed but Unreleased [ 10203 ] New: Closed [ 6 ]

          cap ho added a comment -

          Hi ,

          i understand that it may resolved that using ansible tower api to modify the ask_variables_on_launch to true may resolved the issue. But it is very strange that my ansible tower everytime will update ask_variables_on_launch to false when i make any change in workflow. So everytime i need to manual update it again. is there any way that i have the workaround on that? (e.g passing ask_variables_on_launch: true when calling the ansible tower jenkins plugins or other suggestion?)

          ansible tower 3.3 

          thx

           

          capho

           

          cap ho added a comment - Hi , i understand that it may resolved that using ansible tower api to modify the ask_variables_on_launch to true may resolved the issue. But it is very strange that my ansible tower everytime will update ask_variables_on_launch to false when i make any change in workflow. So everytime i need to manual update it again. is there any way that i have the workaround on that? (e.g passing ask_variables_on_launch: true when calling the ansible tower jenkins plugins or other suggestion?) ansible tower 3.3  thx   capho  
          cap ho made changes -
          Resolution Original: Not A Defect [ 7 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]

            johnwestcottiv John Westcott
            capmatch cap ho
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: