| 2016-01-05 23:16:49 |
Errol Pais |
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. |
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 |
|
