Bug 1300037 - New Service Catalog item form is broken if type is Orchestration
Summary: New Service Catalog item form is broken if type is Orchestration
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
medium
unspecified
Target Milestone: GA
: 5.5.3
Assignee: Eric Winchell
QA Contact: Taras Lehinevych
URL:
Whiteboard:
Depends On: 1299848
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-19 19:31 UTC by John Prause
Modified: 2016-04-13 18:41 UTC (History)
8 users (show)

Fixed In Version: 5.5.3.2
Doc Type: Bug Fix
Doc Text:
Clone Of: 1299848
Environment:
Last Closed: 2016-04-13 18:41:30 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 RHBA-2016:0616 0 normal SHIPPED_LIVE CFME 5.5.3 bug fixes and enhancement update 2016-04-13 22:38:44 UTC

Description John Prause 2016-01-19 19:31:05 UTC 
+++ This bug was initially created as a clone of Bug #1299848 +++

Description of problem:
New Service Catalog item form has insufficient space for Orchestration Template field

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

How reproducible:
Always, both in Firefox and Chrome

Steps to Reproduce:
1. Go to Services -> Catalogs -> Catalog Items
2. Add a new Catalog Item, select Catalog Item Type = Orchestration

Actual results:
Catalog Item form is broken, see screenshot

Expected results:
Catalog Item form is displayed correctly

Additional info:
Comment 2 Eric Winchell 2016-02-15 14:41:44 UTC 
http://gitlab.cloudforms.lab.eng.rdu2.redhat.com/cloudforms/cfme/merge_requests/751
Comment 4 Taras Lehinevych 2016-03-28 09:16:53 UTC 
Verified in 5.5.3.2
Comment 6 errata-xmlrpc 2016-04-13 18:41:30 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-2016:0616
Note You need to log in before you can comment on or make changes to this bug.