Launch instance: volume device name should be optional

Bug #1339760 reported by Julie Pichon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Medium
Miguel Grinberg

Bug Description

From comment 9 on Nova bug 1337821, the device name should be optional and can cause issues if we force the user to select one and they enter an incorrect value. We should make the field optional (and make sure we still create the instance correctly in these cases.)

Changed in horizon:
assignee: nobody → Miguel Grinberg (miguelgrinberg)
Revision history for this message
Miguel Grinberg (miguelgrinberg) wrote :

My plan is to hide the device name field when can_set_mount_point is False. If there are any problems with this approach please let me know.

Revision history for this message
Miguel Grinberg (miguelgrinberg) wrote :

Turns out bug 1273298 implements this fix in the same way I was planning to.

Revision history for this message
Gary W. Smith (gary-w-smith) wrote :

In addition to hiding the field, the validation logic must be changed to permit the device name to be unspecified.

Changed in horizon:
status: New → Confirmed
tags: added: low-hanging-fruit
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/114711

Changed in horizon:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/114711
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=7915b5bf833713da7bac99c6d9dedf8a9cac6c5b
Submitter: Jenkins
Branch: master

commit 7915b5bf833713da7bac99c6d9dedf8a9cac6c5b
Author: Miguel Grinberg <email address hidden>
Date: Sat Aug 16 00:38:58 2014 +0000

    allow empty device name when launching an instance

    From comment 9 on Nova bug 1337821, the device name should be optional
    and can cause issues if we force the user to select one and they enter
    an incorrect value. We should make the field optional (and make sure
    we still create the instance correctly in these cases.)

    Change-Id: I7745b67bc52bbfbb98aa223b6e14ae2f96d81339
    Closes-Bug: 1339760

Changed in horizon:
status: In Progress → Fix Committed
Akihiro Motoki (amotoki)
Changed in horizon:
milestone: none → kilo-1
Thierry Carrez (ttx)
Changed in horizon:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in horizon:
milestone: kilo-1 → 2015.1.0
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.