Bug 1253463 - Sorting container entities list by provider column crashes the UI
Summary: Sorting container entities list by provider column crashes the UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.5.0
Assignee: Alissa
QA Contact: Ramesh A
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-13 18:15 UTC by Ramesh A
Modified: 2015-12-08 13:27 UTC (History)
6 users (show)

Fixed In Version: 5.5.0.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-08 13:27:10 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2551 0 normal SHIPPED_LIVE Moderate: CFME 5.5.0 bug fixes and enhancement update 2015-12-08 17:58:09 UTC

Description Ramesh A 2015-08-13 18:15:24 UTC 
Description of problem:
Sorting container entities list by provider column crashes the UI with the below mentioned exception

ERROR: column container_services.ext_management_system does not exist LINE 1: ...tainer_services"."container_project_id" ORDER BY container_... ^ [container_service/show_list]

@miq-bot add_label ui
@miq-bot add_label providers/containers
@miq-bot add_label bug
cc @simon3z

Version-Release number of selected component (if applicable):
master.20150813094605_98b8bee

How reproducible:
Very

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Ramesh A 2015-08-13 18:16:03 UTC 
github link - https://github.com/ManageIQ/manageiq/issues/3842
Comment 3 Alissa 2015-10-29 07:55:40 UTC 
fixed some time ago in https://github.com/ManageIQ/manageiq/pull/3887
Comment 4 Ramesh A 2015-11-16 11:52:00 UTC 
Good to go.  Verified and working fine in 5.5.0.10-beta2.1.20151110134042_d6f5459
Comment 6 errata-xmlrpc 2015-12-08 13:27:10 UTC 
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.

https://access.redhat.com/errata/RHSA-2015:2551
Note You need to log in before you can comment on or make changes to this bug.