Bug 1284082 - Create Service Dialog from Orchestration Template fails with no feed back.
Create Service Dialog from Orchestration Template fails with no feed back.
Status: CLOSED NOTABUG
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate (Show other bugs)
5.5.0
Unspecified Unspecified
unspecified Severity unspecified
: GA
: 5.5.0
Assigned To: Bill Wei
Dave Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-20 13:57 EST by Jeff Teehan
Modified: 2015-11-20 14:50 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-20 14:50:04 EST
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)

  None (edit)
Description Jeff Teehan 2015-11-20 13:57:08 EST
Description of problem:

I tried to create a Service Dialog which would have provisioned an Azure Item.  When I select my template and choose Create Service Dialog from Orchestration Template from configuration menu, nothing happens.  A check of the log shows no ERRORs.

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

How reproducible:
You can follow the steps in this bug https://bugzilla.redhat.com/show_bug.cgi?id=1276469, or:

Steps to Reproduce:
1. Create or select an Azure Template
2. Choose Create Service Dialog from Orchestration Template from configuration menu
3. Try to locate new menu.

Actual results:
I don't see any menu or error.

Expected results:
Should have the menu item.

Additional info:
I'll leave this appliance in a running state for the next two weeks.  https://10.16.6.164/catalog/explorer unless it horribly crashes.
Comment 2 Jeff Teehan 2015-11-20 14:50:04 EST
There was another issue that cause my system to go bad.  When I resolve it, this issue disappeared.  There is no new bug.

Please disregard this BZ

Note You need to log in before you can comment on or make changes to this bug.