[CI] New image prepare workflow is incompatible with updates and upgrades
Bug #1791332 reported by
Jiří Stránský
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Jiří Stránský |
Bug Description
To reuse the ContainerImageP
Main issue is probably that we do not (and cannot) run any external_*_tasks during normal `update run` and `upgrade run` commands, because those commands are sometimes run multiple times for granularity (e.g. even per-node). And external_*_tasks are used to run things like ceph-ansible, so we don't want to reexeute such things on each per-node update/upgrade call.
This is also why the current proposed fixes for update job don't make the job green yet.
tags: | added: alert |
description: | updated |
summary: |
- New image prepare workflow is incompatible with updates and upgrades + [ci] New image prepare workflow is incompatible with updates and + upgrades |
summary: |
- [ci] New image prepare workflow is incompatible with updates and + [CI] New image prepare workflow is incompatible with updates and upgrades |
Changed in tripleo: | |
assignee: | nobody → Jiří Stránský (jistr) |
Changed in tripleo: | |
milestone: | none → stein-1 |
Changed in tripleo: | |
status: | In Progress → Fix Committed |
Changed in tripleo: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
We should probably try:
1) Plug in whatever generates correct Heat image parameters to the updates+upgrades workflows
2) Use external update/upgrade commands to run the image uploading? Initially it seemed a bit weird but more i think about it, the more it feels ok, and at least we'd be using the same thing under the hood that we're using during deploy.
I'll look into this more next week and gather some feedback on this idea.