Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1300037 - New Service Catalog item form is broken if type is Orchestration
New Service Catalog item form is broken if type is Orchestration
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS (Show other bugs)
5.5.0
Unspecified Unspecified
medium Severity unspecified
: GA
: 5.5.3
Assigned To: Eric Winchell
Taras Lehinevych
: ZStream
Depends On: 1299848
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-19 14:31 EST by John Prause
Modified: 2016-04-13 14:41 EDT (History)
8 users (show)

See Also:
Fixed In Version: 5.5.3.2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1299848
Environment:
Last Closed: 2016-04-13 14:41:30 EDT
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 Product Errata RHBA-2016:0616 normal SHIPPED_LIVE CFME 5.5.3 bug fixes and enhancement update 2016-04-13 18:38:44 EDT

  None (edit)
Description John Prause 2016-01-19 14:31:05 EST
+++ 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 4 Taras Lehinevych 2016-03-28 05:16:53 EDT
Verified in 5.5.3.2
Comment 6 errata-xmlrpc 2016-04-13 14:41:30 EDT
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.