Public bug reported:
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
** Affects: horizon
Importance: Undecided
Status: New
** Tags: allocated available key pair table transfer
** Attachment added: "NewItemDuplication.jpg"
https://bugs.launchpad.net/bugs/1531334/+attachment/4544659/+files/NewItemDuplication.jpg
** Description changed:
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
--
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):
New
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
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
