Resize Instance does not work on fresh login

Bug #1356546 reported by Amogh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Low
Gloria Gu

Bug Description

1. Launch DevStack and login as demo user
2. Create the Instance
3. Click on Resize Instance from more actions and select new flavor, click Resize
4. Observe that Resize waits for "confirm Resize/Migrate", click on the confirm button
5. Observe that the Instance state remains same.

This works fine if navigate to other tabs and navigate back to Instances to click on confirm Resize/Migrate again.

Revision history for this message
Amogh (amogh-r-mavinagidad) wrote :
Changed in horizon:
status: New → Confirmed
importance: Undecided → Low
Gloria Gu (gloria-gu)
Changed in horizon:
assignee: nobody → Gloria Gu (gloria-gu)
Changed in horizon:
status: Confirmed → In Progress
Revision history for this message
Gloria Gu (gloria-gu) wrote :

not sure why the it didn't show the review link...manually added here.

https://review.openstack.org/#/c/115818/

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

Reviewed: https://review.openstack.org/115818
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=03291f4269de89ff15633acfacde035f87ec9c6a
Submitter: Jenkins
Branch: master

commit 03291f4269de89ff15633acfacde035f87ec9c6a
Author: Gloria Gu <email address hidden>
Date: Wed Aug 20 16:11:02 2014 -0700

    Fixed issue of 'terminate instance' with fresh login

    When fresh login horizon, go to Instances page in project or
    admin panel, if try to terminate instance, it does
    not do anything. The symptom also applies to all the
    tables.BatchAction in instance page, for example,
    Hard Reboot, Soft Reboot, Suspend and etc.

    Similiar issue for resizing instance, once issue resize
    request, click on the confirm button, it doesn't do anything for
    fresh login as well.

    When trigger one of the actions on the instance page
    the very first time after login, the filter_string_session
    is None during the process of checking the filter info.
    The original condition checking causes filter change is True so it
    thinks it is the filterAction, so it gets redirected to the instance
    page instead of handling the action request.

    Fixed in get_server_filter_info to check
    filter_string_session is not None

    Closes-Bug: #1356517
    Closes-Bug: #1356546

    Change-Id: I2c093b70c781a63631bd6513b83feb2a698392a6

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