Launching instance with volume created from snapshot doesn't honor original image min_disk

Bug #1752360 reported by Beth Elwell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Medium
Beth Elwell

Bug Description

When launching from Horizon an instance with volume creation from an image with a min-disk parameter :

* the volume size (GB) is automatically set to the minimum size
* if I choose a volume size inferior to this minimum size I get an error message: "The Volume size must be at least xxGB).

However, when trying to launch an instance with instance snapshot, the behaviour is much less user friendly:

* the Volume Size (GB) field is not automatically filled in with the minimum size
* the error message is not displayed before you click on the Launch Instance button

Beth Elwell (bethelwell)
Changed in horizon:
assignee: nobody → Beth Elwell (bethelwell)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

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

Changed in horizon:
status: New → In Progress
Akihiro Motoki (amotoki)
tags: added: queens-backport-potential
Changed in horizon:
importance: Undecided → Medium
milestone: none → rocky-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/548629
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=3233de8f0d13ad9e0223da9f1cf895aa30a6177e
Submitter: Zuul
Branch: master

commit 3233de8f0d13ad9e0223da9f1cf895aa30a6177e
Author: Beth Elwell <email address hidden>
Date: Wed Feb 28 15:52:06 2018 +0000

    Add same launch instance error handling as image to instance

    Previously, when launching an instance with an instance snapshot rather
    than with an image, the error handling was not as pleasant. I.e. the
    volume size was not automatically set to the minimum size and the error
    message would only appear after attempting to launch an instance. This
    is a small patch that addresses this and makes the user experience more
    friendly.

    Change-Id: Ib694f66c74e90ee2e15201673de953c08cf10122
    Closes-bug: #1752360

Changed in horizon:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (stable/queens)

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/551236

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (stable/queens)

Reviewed: https://review.openstack.org/551236
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=e2139bd71764c18fccbb47447b758cbc3fe47f7b
Submitter: Zuul
Branch: stable/queens

commit e2139bd71764c18fccbb47447b758cbc3fe47f7b
Author: Beth Elwell <email address hidden>
Date: Wed Feb 28 15:52:06 2018 +0000

    Add same launch instance error handling as image to instance

    Previously, when launching an instance with an instance snapshot rather
    than with an image, the error handling was not as pleasant. I.e. the
    volume size was not automatically set to the minimum size and the error
    message would only appear after attempting to launch an instance. This
    is a small patch that addresses this and makes the user experience more
    friendly.

    Change-Id: Ib694f66c74e90ee2e15201673de953c08cf10122
    Closes-bug: #1752360
    (cherry picked from commit 3233de8f0d13ad9e0223da9f1cf895aa30a6177e)

tags: added: in-stable-queens
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 14.0.0.0b1

This issue was fixed in the openstack/horizon 14.0.0.0b1 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 13.0.1

This issue was fixed in the openstack/horizon 13.0.1 release.

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.