openstak cli doesn't set os_distro correctly required by magnum clusters

Bug #1676450 reported by yatin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
yatin

Bug Description

After start using openstack cli instead of glance for creating image, cluster-template cannot be created: I2785ed54da7d2e2a162d163a8a9fa4c1cfe083be.

Reason:- magnum requires 'os_distro" property to be set on image, Earlier when using glance cli as below 'os-distro' converted into 'os_distro'
glance image-create --name CoreOS \
                        --visibility public \
                        --disk-format=qcow2 \
                        --container-format=bare \
                        --os-distro=coreos \
                        --file=coreos_production_openstack_image.img

after the patch when using openstack cli,'os-distro' remains 'os-distro' so magnum doesn't find 'os_distro'. This can be fixed either we update the openstack cli in magnum docs to use 'os_distro' or we start accepting both as valid 'os_distro' and 'os-distro'

yatin (yatinkarel)
Changed in magnum:
assignee: nobody → yatin (yatinkarel)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/450250

Changed in magnum:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/450250
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=bb16a62732ce19d2ee3ac36d2d6ecd42863ace50
Submitter: Jenkins
Branch: master

commit bb16a62732ce19d2ee3ac36d2d6ecd42863ace50
Author: yatinkarel <email address hidden>
Date: Mon Mar 27 19:37:16 2017 +0530

    Use 'os_distro' instead of 'os-distro'

    Change-Id: I4fd8c4db9f2297019ead053b97aa0c8c577864bb
    Closes-Bug: #1676450

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 5.0.0

This issue was fixed in the openstack/magnum 5.0.0 release.

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.