Bug 1461534 - Setting VM ownership on more than 100 VMs at a time causing server error status 400 bad request
Summary: Setting VM ownership on more than 100 VMs at a time causing server error stat...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.7.0
Hardware: All
OS: All
high
high
Target Milestone: GA
: 5.9.0
Assignee: Libor Pichler
QA Contact: Nandini Chandra
URL:
Whiteboard:
Depends On:
Blocks: 1484385 1484387
TreeView+ depends on / blocked
 
Reported: 2017-06-14 17:36 UTC by Ryan Spagnola
Modified: 2020-12-14 08:52 UTC (History)
12 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1484385 1484387 (view as bug list)
Environment:
Last Closed: 2018-03-06 14:34:04 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
evm log (9.01 MB, application/x-xz)
2017-06-14 19:40 UTC, Ryan Spagnola 		no flags Details
View All

Description Ryan Spagnola 2017-06-14 17:36:15 UTC 
Description of problem:
Setting VM ownership on more than 100 VMs at a time causing  the following error:
Status 400 Bad Request
Content-Type
Data

Version-Release number of selected component (if applicable):
5.6.4

How reproducible:
Repeatedly

Steps to Reproduce:
1. Go To Compute > Infrastructure > Virtual Machines
2. list 100 items per page and check all
3. Go To Configuration > Set Ownership
4. Change Ownership and Group

Actual results:
400 Bad Request

Expected results:
Changed VM ownership

Additional info:
Tested in lab on vcenter provider with 10,000 vms. 
Changed ownership of 1,000 vms simultaneously without error.
Not able to reproduce on 5.6.4 or 5.7.2
Comment 2 Ryan Spagnola 2017-06-14 19:40:29 UTC 
Created attachment 1287770 [details]
evm log
Comment 12 Libor Pichler 2017-08-21 12:06:17 UTC 
EUWE PR: https://github.com/ManageIQ/manageiq/pull/15860
Comment 16 Nandini Chandra 2017-11-04 04:13:11 UTC 
Verified in 5.9.0.4
Note You need to log in before you can comment on or make changes to this bug.