Bug 1466232 - extra_vars missing in retirement_job_options
extra_vars missing in retirement_job_options
Status: NEW
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate (Show other bugs)
Unspecified Unspecified
medium Severity medium
: GA
: cfme-future
Assigned To: Greg McCullough
Dave Johnson
Depends On:
  Show dependency treegraph
Reported: 2017-06-29 06:01 EDT by Kim Borup
Modified: 2017-08-09 11:19 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Ansible

Attachments (Terms of Use)

  None (edit)
Description Kim Borup 2017-06-29 06:01:44 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.