LaunchConfiguration missing constraints about "IMAGE_ID" and "KEY_NAME"

Bug #1312564 reported by huangtianhua
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Undecided
huangtianhua

Bug Description

AWS::AutoScaling::LaunchConfiguration resource missing constraints about "IMAGE_ID" and "KEY_NAME", we should to check whether the image/keypair exists.

Changed in heat:
assignee: nobody → huangtianhua (huangtianhua)
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix proposed to heat (master)

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

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

Reviewed: https://review.openstack.org/90304
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=7262d3a2c79c38391a93617cfbe69341d2221324
Submitter: Jenkins
Branch: master

commit 7262d3a2c79c38391a93617cfbe69341d2221324
Author: huangtianhua <email address hidden>
Date: Fri Apr 25 15:36:15 2014 +0800

    Add constraints to check whether image/keypair exists

    Add constraints for "KeyName" and "ImageId" to check whether keypair/image
    exists on "AWS::AutoScaling::LaunchConfiguration" resource.

    Change-Id: I23dc126e621f3cfa7ca86b3a1c27dd949d3f5093
    Closes-Bug: #1312564

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
milestone: none → juno-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: juno-3 → 2014.2
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.