I've confirmed this also affects launching multiple instances in one call. Every instance will have an ami-launch index of 1.
Looking through the code I believe this comes from the following function in nova/compute/api.py : def create_db_entry_for_new_instance(self, context, instance_type, image, base_options, security_group, block_device_mapping, num=1): The num=1 default parameter gets saved as the launch_index parameter of the new instance. The num parameter is not passed for a single instance or multiple instances so the ami-launch-index will always be one. ** Summary changed: - metadata ami-launch-index coming back off-by-one + metadata ami-launch-index always returning "1" -- 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/ubuntu/+source/nova/+bug/934534/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs