Description of problem:
unable to use state variables accorss multiple deployment of a service
Version-Release number of selected component (if applicable):
all the time (customer environment)
Steps to Reproduce:
The customer needs to use Ansible Embedded to set a state var. they have created a domain to test it, and a service catalog that has configured its entry point to the state machine of this domain. The schema is the following:
- State 1: Set a state var and print it
- State 2: Launch the playbook using Ansible Embedded. This playbook makes the connection, initialize the workspace and set the state var with another value.
- State 3: Print eh value of the state var.
the first service deployment works fine, the second fails until the name of the state variable is changed, and so on for the next deployments.
sometimes changing the name doesn't fix the deployment.
consistant behaviour without having to change the name of the state var
the customer is using a playbook based on the example explained here: https://github.com/syncrou/manageiq-automate/blob/master/README.md.
The role we are using in the playbook (manageiq-automate), is exactly the same as the one in this page
Please collect the logs from an appliance showing this error. We are attempting to recreate locally.
I was able to make the playbook work by removing/commenting out the 'Become' values in lines 3,18,32 and setting the Escalate Privilege to NO. I was testing on a later release so now I am going to test on 22.214.171.124.
Will update when I am finished testing on 126.96.36.199.
Tested on 188.8.131.52
You also need to update your role to look like this:
I will upload the playbook that I used.
Created attachment 1430260 [details]
Updated playbook that works