** Description changed: - While using Mitaka, we found that by default, using js backend, it is - not possible to choose 'any' availability zone. The issue is not fixed - in master branch. + [Impact] + While using Mitaka, we found that by default, using js backend, it is not possible to choose 'any' availability zone. The issue is not fixed in master branch. For python implementation the logic is: https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py#L390 The JS implementation miss the logic if number of AZs is >1 https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/launch-instance-model.service.js#L321 Also, JS implementation looks ugly if you have lot of subnets per network... + + [Test Case] + Ensure that in the Angular Launch Instance, if there is more than one availability zone, it defaults to the option of Nova scheduler picking the AZ. + + [Regression Potential] + Regression potential is fairly low. This bug has been fixed in all releases of OpenStack starting with Newton. The patch did have to be modified slightly to apply to mitaka.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613900 Title: Unable to use 'Any' availability zone when spawning instance To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1613900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
