[Bug 934534] Re: metadata ami-launch-index always returning "1"

[OpenStack Hudson]

Reviewed:  https://review.openstack.org/4715
Committed: http://github.com/openstack/nova/commit/09e664c0f00326d3dea8c04ac661ca0a05bbf0f5
Submitter: Jenkins
Branch:    milestone-proposed

commit 09e664c0f00326d3dea8c04ac661ca0a05bbf0f5
Author: Mike Milner <mike.milner at canonical.com>
Date:   Thu Feb 23 15:13:51 2012 -0400

    Include launch_index when creating instances.
    
    Fixes bug 934534.
    
    The launch_index column in the database is used as the ami-launch-index value
    provided by the metadata service.
    
    If launch_index is not specified it defaults to 1. This is incorrect for the
    single instance case (should be 0) and doesn't correctly handle multi-instance
    starts.
    
    This branch changes the default launch_index to 0 (to handle the single
    instance case) and adds the launch_index in the schedulers for multi-instance
    starts.
    
    Change-Id: Ifc45abf4cd9f50f732ba4a4b68c0a6242a6c9710


** Changed in: nova
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/934534

Title:
  metadata ami-launch-index always returning "1"

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/934534/+subscriptions