Bug 989041 - Unable to detach VMs from a pool if pool contains more than 100 VMs
Unable to detach VMs from a pool if pool contains more than 100 VMs
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal (Show other bugs)
3.1.5
Unspecified Unspecified
medium Severity medium
: ---
: 3.3.0
Assigned To: Frantisek Kobzik
Pavel Stehlik
virt
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-26 22:53 EDT by Bryan Yount
Modified: 2015-09-22 09 EDT (History)
10 users (show)

See Also:
Fixed In Version: is8
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-01-21 12:35:00 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 435913 None None None Never
oVirt gerrit 17450 None None None Never

  None (edit)
Description Bryan Yount 2013-07-26 22:53:55 EDT
Description of problem:
If a pool contains more than 100 VMs, there is no way to detach any VM >100 from the pool. The tab does not contain a "Next page" button or a search field.

Version-Release number of selected component (if applicable):
3.1.0-55
3.1.2 (I couldn't test a pool this large but no "Next Page" button exists here)

How reproducible:
Very

Steps to Reproduce:
1. Create a pool with 101 VMs
2. Click on the pool tab
3. Select the VM sub-tab
4. Try to locate VM 101 in the pool to detach it

Actual results:
Unable to detach VM 101

Expected results:
Ability to go to next page and detach VM 101 from the pool
Comment 2 Frantisek Kobzik 2013-07-30 05:44:08 EDT
merged u/s: caef3ae2886a0135757c989266aaef3f5869faf6
Comment 3 David Botzer 2013-08-27 06:25:59 EDT
Fixed, 3.3/is11
Allow to detach vm-101
* Known issue where the names of the VMs in pool->Virtual machine are all disappeared
Fixed, 3.3/is11
Comment 4 Charlie 2013-11-27 19:08:39 EST
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.
Comment 6 errata-xmlrpc 2014-01-21 12:35:00 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2014-0038.html

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