Use specific env files (eg. Ceph/HCI) based on target CI job
Bug #1661257 reported by
Giulio Fidente
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
Would be nice to have a mechanism which would allow adding a specific env file to the deployment commandline based on the target CI job.
This could be used, for example, to match the change at https:/
| tags: | added: transition-port |
| affects: | tripleo-quickstart → tripleo |
| tags: | added: quickstart |
| Changed in tripleo: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in tripleo: | |
| milestone: | none → pike-1 |
| Changed in tripleo: | |
| milestone: | pike-1 → pike-2 |
| Changed in tripleo: | |
| milestone: | pike-2 → pike-3 |
| Changed in tripleo: | |
| status: | Triaged → In Progress |
| 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: | |
| status: | In Progress → Triaged |
| 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 |
| Changed in tripleo: | |
| milestone: | rocky-3 → rocky-rc1 |
| Changed in tripleo: | |
| milestone: | rocky-rc1 → stein-1 |
| Changed in tripleo: | |
| milestone: | stein-1 → stein-2 |
Revision history for this message
| Emilien Macchi (emilienm) wrote Cleanup EOL bug report | #1 |
| Changed in tripleo: | |
| importance: | High → Undecided |
| status: | Triaged → Expired |
To post a comment you must log in.
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
Valid example: CONFIRMED FOR: FUTURE