host provision config tasks that follow initial connection setup

[jcnars]

Post the user creation in the previous PR, extending the previously merged code with additional functionality in this PR.

Command called as:

✔ ~/DriveFS/My Drive/bmaas/host_provisioning/bms-toolkit [host-provision|…1] 
21:34 $ runlocalssh ./host-provision.sh --instance-ip-addr 172.16.30.1  --instance-ssh-user ansible9 --proxy-setup false --u01-lun /dev/mapper/3600a098038314344372b4f75392d3850 
Command used:
/usr/local/google/home/jcnarasimhan/DriveFS/My Drive/bmaas/host_provisioning/bms-toolkit/host-provision.sh --instance-ip-addr 172.16.30.1 --instance-ssh-user ansible9 --proxy-setup false --u01-lun /dev/mapper/3600a098038314344372b4f75392d3850

Running with parameters from command line or environment variables:

INSTANCE_SSH_USER=ansible9
INVENTORY_FILE=172.16.30.1,
ORA_CS_HOSTS=172.16.30.1
ORA_PROXY_SETUP=false
ORA_U01_LUN=/dev/mapper/3600a098038314344372b4f75392d3850

Found Ansible at /usr/bin/ansible-playbook

Running Ansible playbook: /usr/bin/ansible-playbook -i 172.16.30.1,   host-provision.yml

PLAY [Create private public key pair locally] **********************************************************************************************************************************

TASK [Gathering Facts] *********************************************************************************************************************************************************
ok: [localhost]

TASK [host-provision : Creates .ssh directory in control node if it does not exist] ********************************************************************************************
ok: [localhost]

[mfielding]

Apologies for the delayed reply here.

[mfielding]

Can we please only ignore "This system is already registered" errors? I'd imagine that many other error cases would warrant issues.

[jcnars]

Modifying the logic for this completely. The new logic (when I push my branch) will reside in: bms-toolkit/roles/host-provision/tasks/rhel-config-tasks.yml.

In essence the logic will:

• Get current registration status of the host

• If host is not 'Subscribed':
  * ask Redhat Support username/password on the cmd line
  * 
Register host in RHSM


With this, we don't have to ignore any errors.

[jcnars]

https://paste.googleplex.com/6592815808118784 (internal) shows successful runs after code modification with different input options.

Here is the codeflow schematic for ref:
https://screenshot.googleplex.com/7uWan6c5N5Mrvyx (internal)

[jcnars]

Incorporated changes.
After final shape/approval, will test in a reimaged host and take the gaps to do further changes in this same PR.

[google-oss-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcnars

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jcnars]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcnars, mfielding

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jcnars,mfielding]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment