undercloud configured to use wrong ssh configuration
Bug #1631125 reported by
Lars Kellogg-Stedman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Invalid
|
High
|
Unassigned |
Bug Description
When deploying an environment using a pre-existing inventory, such as:
myvirthost ansible_
There is no ansible_
In the above situation, the playbooks will select the wrong configuration, and connects to the undercloud will fail.
Changed in tripleo: | |
milestone: | pike-1 → pike-2 |
Changed in tripleo: | |
milestone: | pike-2 → pike-3 |
Changed in tripleo: | |
milestone: | pike-3 → pike-rc1 |
Changed in tripleo: | |
milestone: | pike-rc1 → pike-rc2 |
Changed in tripleo: | |
milestone: | pike-rc2 → queens-1 |
Changed in tripleo: | |
milestone: | queens-1 → queens-2 |
Changed in tripleo: | |
milestone: | queens-2 → queens-3 |
Changed in tripleo: | |
milestone: | queens-3 → queens-rc1 |
Changed in tripleo: | |
milestone: | queens-rc1 → rocky-1 |
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
To post a comment you must log in.
an alternative could be to set a virthost variable in the quickstart.sh ansible invocation that is set to the shell variable VIRTHOST. We could then make decisions based on that -e virthost var.