Bug 1709957 - wrong number of cells for None row in Catalog Item->Request Info->Catalog->Selected VM
Summary: wrong number of cells for None row in Catalog Item->Request Info->Catalog->Se...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.10.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: GA
: 5.11.0
Assignee: Milan Zázrivec
QA Contact: Tasos Papaioannou
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-14 16:10 UTC by Ievgen Zapolskyi
Modified: 2019-12-12 13:36 UTC (History)
8 users (show)

Fixed In Version: 5.11.0.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-12 13:36:27 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screen shot (285.23 KB, image/png)
2019-05-14 16:10 UTC, Ievgen Zapolskyi 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:4199 0 None None None 2019-12-12 13:36:39 UTC

Description Ievgen Zapolskyi 2019-05-14 16:10:22 UTC 
Created attachment 1568544 [details]
screen shot

Description of problem:
None row has one extra cell in Selected VM table. look at screenshot

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

How reproducible:
100%

Steps to Reproduce:
1. Open Service->Catalogs->Catalog Items
2. Choose Configuration->Add a New Catalog Item
3. Choose Catalog Item type f.e. RedHat Virtualization
4. Open Request Info tab

Actual results:
None row has one extra cell

Expected results:
correctly rendered table

Additional info:
Comment 3 Milan Zázrivec 2019-05-15 08:18:47 UTC 
https://github.com/ManageIQ/manageiq-ui-classic/pull/5487
Comment 4 Tasos Papaioannou 2019-05-20 16:56:27 UTC 
Verified on 5.11.0.4.
Comment 6 errata-xmlrpc 2019-12-12 13:36:27 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/RHBA-2019:4199
Note You need to log in before you can comment on or make changes to this bug.