Bug 1271202 - Cannot create nested automate namespace or a class in namespace
Summary: Cannot create nested automate namespace or a class in namespace
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
high
Target Milestone: GA
: 5.5.0
Assignee: Harpreet Kataria
QA Contact: Milan Falešník
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-13 11:30 UTC by Milan Falešník
Modified: 2015-12-08 13:37 UTC (History)
5 users (show)

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


Attachments (Terms of Use)
An excerpt from the AE screenshot (34.92 KB, image/png)
2015-10-13 11:30 UTC, Milan Falešník
no flags Details


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 Milan Falešník 2015-10-13 11:30:25 UTC
Created attachment 1082354 [details]
An excerpt from the AE screenshot

Description of problem:
AE Namespace's Configuration menu lost the ability to CRUD on the child objects and only one option is available, to copy classes.

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

How reproducible:
always

Steps to Reproduce:
1. Go to Automate / Explorer
2. Create a domain
3. Create a namespace
4. Within that namespace, try creating another namespace or class.

Actual results:
You will see the menu contains only one grayed option for copying classes

Expected results:
You can create further objects as usual in older versions.

Additional info:

Comment 3 Milan Falešník 2015-10-20 14:27:57 UTC
This functionality is working again in 5.5.0.6

Comment 5 errata-xmlrpc 2015-12-08 13:37:46 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.