octavia-diskimage-retrofit fails to set image architecture
Bug #2016344 reported by
Alan Baghumian
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-octavia-diskimage-retrofit |
Fix Committed
|
Wishlist
|
Alan Baghumian |
Bug Description
Executing the following command produces amphorae images on OpenStack:
$ juju run-action --wait octavia-
However it does not set the "architecture" property properly.
This causes Openstack to schedule workloads on mismatching compute nodes in multi-arch deployments. For instance we see x86_64 image being launched on aarch64 nodes.
This should be fairly easy to fix.
Thank you,
Alan
To post a comment you must log in.
So doing a bit of digging, the glance client 'create' method takes an architecture property: https:/ /github. com/openstack/ python- glanceclient/ blob/7c2ab837aa 0c5749ac84eb610 ed13ac4fb6dfc12 /glanceclient/ v2/image_ schema. py#L221
This just needs to be added in the charm code here: https:/ /github. com/openstack/ charm-octavia- diskimage- retrofit/ blob/939a008141 bb9e5d5390b491c b1713fd7e1c524c /src/lib/ charm/openstack /octavia_ diskimage_ retrofit. py#L300 essentially reusing/using "source_ image.architect ure).