*** This bug is a duplicate of bug 1563529 *** https://bugs.launchpad.net/bugs/1563529
It is already fixed in https://review.opendev.org/#/c/680603/. ** This bug has been marked a duplicate of bug 1563529 "Boot from volume" fails on image size restriction -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1744999 Title: Horizon incorrectly checks for flavor disk if volume-based instance is being created Status in OpenStack Dashboard (Horizon): New Bug description: Description =========== When creating a new VM through Horizon, it validates that its disk size is less than the flavor disk one. Such check doesn't make sense when creating a volume-based instance - either via image2volume process or by using previously existing image. There are no such restrictions in Nova for quite a while. - check in Horizon: https://github.com/openstack/horizon/blob/67eba6443900654b5c70501553e65ddb48f33bad/openstack_dashboard/dashboards/project/static/dashboard/project/workflow /launch-instance/flavor/flavor.controller.js#L382 - fixed bug with incorrect behaviour in Nova (in Kilo version): https://bugs.launchpad.net/nova/+bug/1457517 Steps to reproduce ================== 1. Create an image A with min_size of 50GB 2. Create a flavor B with disk size of 20GB 3. Try to create an instance C using boot source "image A" and requesting to create a new volume. 4. Select flavor B as a flavor. Expected result =============== Instance creation succeeds. Actual result ============= Warning is shown, instance creation button is disabled. Environment =========== OpenStack Pike. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1744999/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp