'copy-image' import job should not try to run additional plugins
Bug #1885725 reported by
Erno Kuvaja
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Glance |
Fix Released
|
High
|
Erno Kuvaja | ||
| Ussuri |
Fix Committed
|
High
|
Erno Kuvaja | ||
| Victoria |
Fix Released
|
High
|
Erno Kuvaja | ||
Bug Description
The import plugins were designed to be additional tasks to be performed against the image data or metadata before image being set to active. Things like uncompression or conversion etc. just does not make sense while target is just to copy the data between stores.
| Changed in glance: | |
| assignee: | nobody → Erno Kuvaja (jokke) |
| Changed in glance: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to glance (master) | #1 |
| Changed in glance: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to glance (stable/ussuri) | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit b8332d9b6b5e1e6
Author: Erno Kuvaja <email address hidden>
Date: Tue Jun 30 14:28:09 2020 +0100
Don't include plugins on 'copy-image' import
The import plugins were designed to interact with the image data
or metadata before the image becomes active. It does not make sense
to try to run them on 'copy-image' taskflow which is just copying
the data between stores on active image.
Co-Authored-By: Erno Kuvaja <email address hidden>
Co-Authored-By: Abhishek Kekane <email address hidden>
Closes-Bug: #1885725
Change-Id: I2df30aa26f96a0