[RFE] - Make clear differentiation between `ansible_user` and undercloud user that deploys the overcloud
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo-quickstart |
Fix Released
|
Critical
|
Harry Rybacki |
Bug Description
If we look way back to when OOOQ was initially developed by Trown up until rather recently, it was generally assumed that the 'stack' user would always be the user setup on the undercloud and used to deploy the overcloud. However, as we grown, refined, and expanded OOOQ and OOOQ-Extras this assumption is no longer valid. To make things slightly more complicated, we have decoupled hardcoded
In order for allow decouple the stack user we have opted to use 'ansible_user' e.g.[1] which is, by default, set to 'stack' in the common role[2].
To further help clear up cruft, we are also working towards a unified set of defaults such that roles within OOOQ-Extras depend on the extras-common role[3] and the extras-common role depends on the common role[4]. However, both [3] and [4] are bringing to light problems with using 'ansible_user' in such a broad manner[5]:
```
TASK [undercloud-deploy : Create undercloud install script] *******
task path: /home/centos/
Thursday 05 January 2017 21:59:44 +0000 (0:00:04.648) 0:10:40.734 ******
fatal: [undercloud]: FAILED! => {"changed": true, "failed": true, "msg": "Destination directory /home/stack/
```
Using 'ansible_user' rather than stack[1] has also created issues with the collect-logs role as upstream, ci.centos, and internal pipelines all have varying setup/environment requirements. Presently logging is broken in ci.centos as well as for internal (RH) jobs[6].
Let's start a discussion around creating a solution. Perhaps having a distinct 'undercloud_user' variable that would fall into where we have classically seen 'stack' would suffice.
[1] - https:/
[2] - https:/
[3] - https:/
[4] - https:/
[5] - https:/
[6] - https:/
Changed in tripleo-quickstart: | |
assignee: | nobody → Harry Rybacki (hrybacki-h) |
Changed in tripleo-quickstart: | |
status: | New → In Progress |
status: | In Progress → Fix Released |
Changed in tripleo-quickstart: | |
importance: | Undecided → Critical |
+1 for using introducing the `undercloud_user` variable which should default to `stack` and used in the places where we hardcoded it previously. This would the issues we have while making the undercloud deployments more flexible.