Description of problem:
during provisionning or via the rails console, it is not possible to change the values of the options of the embedded ansible service (the get/set_option is not implemented).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a service base on an embedded ansible catalog item
2. via the console: svc=$evm.vmdb(:service).find_by_name("test")
5. svc2[.options[:config_info][:retirement][:hosts] is not the defined value but the default one
8. svc2[.options[:config_info][:retirement][:hosts] is the defined value
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.
If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
the work around given form point 6 to 8 are not working via the automation.
Cyril - Does step 6 work during the provisioning of the service? Are you really reporting here that they do not work during retirement?
Greg, Yes I confirm that, during the provisionning I can set the host list and the params vars as expected.
The problem is, when we start the retirement of the service, the values of the hosts and params are set to the default from the catalog item and not from the values used during the provisionning, without the ability to change them.
Created attachment 1447964 [details]
The purpose of the RFE is to be able to change some of the options for retirement. The correct way to do this is through the preprocess step. You can point the pre4 step in automate to a user script following the default example as shown in attachment.
The options hash can accept the following keywords
:credential_id => <VMDB machine credential id>
:hosts => <a comma delimited string of hosts>
:extra_vars => <a hash of variables>
Please close this BZ if above instruction solves your problem.