Description of problem: Variables used when provisioning using ansble, does not get used when doing a retirement. How reproducible: All the time Steps to Reproduce: 1. Create ansible playbook for provision and retirement that uses a variable. 2. create service dialog that ask for variable name 3. Create Catalog item that uses service dialog. 4. Order Catalog item providing name for variable. 5. Retire Service item which will then fail. Actual results: Variable does not get passed during retirement. Expected results: Variable from provisioning get added when doing retirement in order to link to the correct projects in ie OCP. Additional info: From API. "dialog": { "dialog_credential": "10", "dialog_hosts": "host.example.com", "dialog_param_projectname": "thedebug" }, "provision_job_options": { "hosts": "host.example.com", "extra_vars": { "projectname": "thedebug" }, "credential": "3", "inventory": 16 }, "retirement_job_options": { "hosts": "host.example.com", "extra_vars": {}, "inventory": 17 } }, "retirement_job_options": { "hosts": "host.example.com", "extra_vars": {}, <- This is where i would expect the extra vars from provisioning to be as you can see from the provision_job_options.
Hi Kim, Retirement was designed to run without user input. If 'copy from provision' is clicked at service creation / edit, the extra_vars from provision would be copied over. However, if the dialog is modified to expect user input, that input will not be pushed into the retirement task. In my opinion this is working as expected.