Submitting PR from IGBF-2318 to master branch after squashing all the commits into one.

To test:

• Follow instructions in control_node.yml to provision a control node "from scratch".
• If you notice any errors or problems, please create a new Jira ticket for same.

Chester Dias

Control Node provisioning threw an error initially but recovered the second time. I think this error could be due my slow internet
Verifications Summary:
1. python3 version = 3.7.6
2. installed pip3 modules are present
3. ansible version = 2.9.6
4. ansible python = 3.7.6
5. The correct playbook repo is cloning.
6. The required public key is copying to the local machine for adding in bitbucket.
7. The connection public key for provisioning target EC2 is also copying from local to control node.
8. Rerun does not recreate a new control-node.

Notes: This playbook has to be run twice to complete the provisioning.
Suggestion: Creation of a bot user for bitbucket access which will allow username and password for git clone to be passed via control_node_vars.yml

Attached complete output for future reference

Change request:

When closing a ticket, we always re-assign it to the original developer. This is to make it easier to keep track of what people have done.

Please re-assign this to me now that it is closed.
Chester Dias

I will ensure that going forward.