cluster template image update does not update cluster_distro

Bug #1685224 reported by Ricardo Rocha
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
New
Undecided
Unassigned

Bug Description

Here's an example sequence:

$ magnum cluster-template-create --name rocha-test00 --image-id c60d724b-8bf8-416d-9b3f-68e17b733347 --external-network-id CERN_NETWORK --flavor-id m2.medium --master-flavor-id m2.medium --coe swarm
...
| cluster_distro | fedora-atomic |
| image_id | c60d724b-8bf8-416d-9b3f-68e17b733347 |
...

Which is correct:
$ glance image-show c60d724b-8bf8-416d-9b3f-68e17b733347 | grep os_distro
| os_distro | fedora-atomic |

If i then update the cluster template image with the following (different os_distro):
$ glance image-show c4537d3b-9c90-4620-b802-c1064df9f40e | grep os_distro
| os_distro | fedora-atomic-staging

$ magnum cluster-template-update rocha-test00 replace image_id=c4537d3b-9c90-4620-b802-c1064df9f40e
...
| cluster_distro | fedora-atomic |
| image_id | c4537d3b-9c90-4620-b802-c1064df9f40e |
...

The cluster_distro is not properly updated with the value of the new image.

This causes issues as currently the driver is selected based on a combination of cluster_distro and coe.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.