Magnum

Baymodel create can't support to use image name any more

Bug #1448952 reported by Lan Qi song
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
Lan Qi song

Bug Description

After this patch get merged: https://review.openstack.org/#/c/172348/ we can't use image name as one parameter when create a baymodel, otherwise, it will raise an image not found exception.

But in most of our guides, we used image name as example, I think we should keep this capability.

See original description
Lan Qi song (lqslan)
description: updated
Revision history for this message
Lan Qi song (lqslan) wrote :

The fix patch: https://review.openstack.org/#/c/177707/

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

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

commit 1c3027fc526181f8eb3e3831d278c79b0cf194d3
Author: Lan Qi song <email address hidden>
Date: Mon Apr 27 16:03:02 2015 +0800

    Add image name support when create a baymodel

    Currently, if we create a baymodel and pass an image name as parameter,
    an image not found exception would be raised.

    This patch add image name support when create a baymodel

    Closes-Bug: #1448952

    Change-Id: If8b41eacccf0880908dafebb3e86e374399c0bef

Changed in magnum:
status: In Progress → Fix Committed
Adrian Otto (aotto)
Changed in magnum:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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