← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1531334] Re: [Launch Instance] New items are visible under both allocated and available in transfer tables

 

Reviewed:  https://review.openstack.org/252205
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=52fc193d0cbf8d9208b1151b6a302001a44cb582
Submitter: Jenkins
Branch:    master

commit 52fc193d0cbf8d9208b1151b6a302001a44cb582
Author: Rajat Vig <rajatv@xxxxxxxxxxxxxxxx>
Date:   Tue Dec 1 22:18:56 2015 -0800

    Transfer table should update allocatedIds on allocated change
    
    Transfer table does a one time allocation
    for allocatedIds and does not watch changes to
    allocated. As a result, when the allocated
    list is fetched at a later point, the allocatedIds
    are not updated resulting in a broken view.
    
    Partially-Implements: blueprint ng-flavors
    Closes-Bug: #1531334
    
    Change-Id: I807c682b69081f90fc3d74675e8ca149bb855521


** Changed in: horizon
       Status: In Progress => Fix Released

-- 
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/1531334

Title:
  [Launch Instance] New items are visible under both allocated and
  available in transfer tables

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Description:
  The transfer table is a component that is preloaded with data to identify what's available and what's allocated. This results in two disjoint sets. The bug appears when we programatically try to create and allocate an item to an already preloaded transfer table. Although the table adds the new item to the allocated set, it adds it to the available set as well.

  Steps to reproduce:
  * Navigate to Project-->Compute-->Instances
  * Click on the angular Launch Instance button to open up the Launch Instance Modal
  * Go to key pair section
  * Make sure there are no key pairs allocated in the transfer table.
  * Create a key pair by clicking on the create key pair button and completing the create key pair flow.

  When you return back to the transfer table that lists the key pairs,
  you can see that the newly created key pair is visible under both the
  available section as well as the allocated.

  Attached Screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1531334/+subscriptions


References