scenarios in Ocata reference services introduced in Pike
Bug #1708014 reported by
Emilien Macchi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Jiří Stránský |
Bug Description
Jobs which test upgrades from baremetal to containerized environments fail because they don't deploy TripleO from Ocata but from Pike (master).
See: https:/
Which is on master, but not on stable/ocata of course.
We need to change the tooling to deploy THT from stable/ocata and then upgrade it to Pike.
Right now, we have zero testing for upgrades from Ocata to Pike that actually work when deploying in containers.
Changed in tripleo: | |
milestone: | none → pike-rc1 |
tags: | added: ci |
tags: | added: quickstart upgrade |
Changed in tripleo: | |
assignee: | nobody → Jiří Stránský (jistr) |
tags: | removed: alert |
tags: | removed: quickstart |
Changed in tripleo: | |
status: | Triaged → In Progress |
Changed in tripleo: | |
milestone: | pike-rc1 → pike-rc2 |
Changed in tripleo: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
The job doesn't deploy pike, it deploys ocata:
http:// logs.openstack. org/10/ 489710/ 1/experimental/ gate-tripleo- ci-centos- 7-scenario001- multinode- oooq-container- upgrades/ b83b740/ console. html#_2017- 08-01_19_ 12_14_388824
Problem is that the ocata version of the scenario includes congress too.