Bug 1376747 - RHV: when choosing hosts, sorting mechanism misbehaves
Summary: RHV: when choosing hosts, sorting mechanism misbehaves
Keywords:
Status: NEW
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: WebUI
Version: 1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.2
Assignee: John Matthews
QA Contact: Sudhir Mallamprabhakara
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-16 09:48 UTC by Antonin Pagac
Modified: 2020-01-08 16:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Antonin Pagac 2016-09-16 09:48:13 UTC
Description of problem:
Deploying RHV engine + n hypervisors
In step 2B. Engine, sorting available hosts by clicking on the table headers (one of [Host Name, MAC Address, Host Type, CPU, Memory, Disks, Disk Space, Network]) seems to be working fine and user is able to choose an engine.
In step 2C. Hypervisor, when trying to sort remaining available host in the table, clicking on any of the table headers causes the already chosen engine machine to re-appear, and whole setup takes step back to 2B. All this is done only by clicking on the table header in steb 2C.

Version-Release number of selected component (if applicable):
QCI-1.0-RHEL-7-20160908.1

How reproducible:
Always

Steps to Reproduce:
1. Start RHV engine + hypervisor deployment, go to step 2B, select engine machine, click next
2. In step 2C, try to sort the rows in the table with hosts by clicking on any of the table headers (one of [Host Name, MAC Address, Host Type, CPU, Memory, Disks, Disk Space, Network])
3. The engine machine appears in the table
4. You are suddenly back at step 2B

Actual results:
Sorting seems to be working but it's returning user to previous step of the deployment

Expected results:
Sort the rows in the table in the current step of the deployment

Additional info:


Note You need to log in before you can comment on or make changes to this bug.