Create volume from snapshot : Get mismatched form after a invalid submission

Bug #1642910 reported by lijunli
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
In Progress
Low
lijunli

Bug Description

Version: Mitaka

Steps to reproduce:

1. Go to Project -> Volumes Snapshots
2. Pick an existing snapshot, click "Create Volume" and get a modal form
3. Enter an invalid value(for example, a value which is smaller than the original size) for "Size(Gib)" field and click "Create Volume"
4. Get another modal form with a warning message "The volume size cannot be less than the
snapshot size(2GiB)."

Expected:
4. You should get the same modal form with step 2 except the warning message.

Actually:
The forms in step 2 and 4 are different.

Revision history for this message
lijunli (lijunli) wrote :
Changed in horizon:
assignee: nobody → lijunli (lijunli)
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/399812

Changed in horizon:
status: New → In Progress
Revision history for this message
Cindy Lu (clu-m) wrote :

Hi Lijun,

Can you verify this behavior in Newton? I tried it out, and it seemed to work normally.

Revision history for this message
lijunli (lijunli) wrote :

Hi Cindy,

I have verified this bug in Newton just now. It does exist!

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

This is still occurring on the current master. The form that is shown after the error is also titled 'Create Volume', but it has different fields, and does not retain the volume source of the original form, i.e. it has forgotten that the volume source is the snapshot.

Changed in horizon:
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on horizon (master)

Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/399812
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

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.