Bug 1336888 - Not able to create catalog item for azure
Summary: Not able to create catalog item for azure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.0
Assignee: Milan Zázrivec
QA Contact: Shveta
URL:
Whiteboard: azure:catalog
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-17 17:16 UTC by ldomb
Modified: 2017-08-30 20:18 UTC (History)
8 users (show)

Fixed In Version: 5.6.0.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 16:03:15 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:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description ldomb 2016-05-17 17:16:07 UTC
Description of problem:
Not able to create catalog item for azure

Version-Release number of selected component (if applicable):
5.6.0.6-beta2.5.20160511140943_ff75fb2


How reproducible:


Steps to Reproduce:
1. Press compute -> Services -> Catalogs
2. Create a catalog named clouds
3. Create a catalog item in the clouds catalog with the following characteristics: 

Catalog item type -> Azure

Actual results:
Adding new catalog item is grayed out and the "sun icon is spinning and spinning"

Expected results:
Can fill out the catalog item. I don't have that problem with Ec2 and GCE

Additional info:

Comment 4 Shveta 2016-05-18 17:24:02 UTC
Well , the actual problem here is the spinner .
Even though the screen is greyed out , you can type in the catalog item name and then the spinner stops spinning.

So the bug here is that the spinner shows spinning even after loading the screen.
Catalog item can be added.

Comment 5 ldomb 2016-05-18 17:35:37 UTC
Yes I can confirm that. Not sure if this is a browser related issue as well. Tried it again today and the spinner went away as well. So it seems to be working?

Comment 7 Shveta 2016-05-18 21:52:52 UTC
This issue points to https://github.com/ManageIQ/manageiq/issues/8751 in github

Comment 8 Milan Zázrivec 2016-05-19 06:21:37 UTC
This is a valid bug report and it definitely needs to be fixed for the 5.6 release.

This issue is not specific to an azure type of service catalog, the problem
shows when adding a new service template for a provider type, which doesn't
have any vm templates synced (i.e. in your case, you don't have any azure vm templates
refreshed from your providers).

So in the end, this problem would show for all blank 5.6 installations.

Comment 9 Milan Zázrivec 2016-05-19 13:09:26 UTC
https://github.com/ManageIQ/manageiq/pull/8810

Comment 10 CFME Bot 2016-05-19 18:06:06 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/613cb4bcf57fbd97b2eb52e947f49686e81a6929

commit 613cb4bcf57fbd97b2eb52e947f49686e81a6929
Author:     Milan Zazrivec <mzazrivec>
AuthorDate: Thu May 19 15:04:33 2016 +0200
Commit:     Milan Zazrivec <mzazrivec>
CommitDate: Thu May 19 15:04:33 2016 +0200

    Fix for never ending spinner when creating service catalog item
    
    In case we're creating a service catalog item for a provider type,
    which doesn't have any vm templates available, we'd be getting
    an infinite spinner in UI.
    
    This was caused by us relying on presence of @edit[:new][:src_vm_id]
    variable, which in this particular case would be missing. This in
    the end would cause a javascript error -> infinite spinner.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1336888

 app/assets/javascripts/miq_application.js                     | 4 +++-
 app/controllers/application_controller/miq_request_methods.rb | 1 +
 2 files changed, 4 insertions(+), 1 deletion(-)

Comment 11 Shveta 2016-05-26 16:20:51 UTC
Fixed.
verified in 5.6.0.8-rc1.20160524155303_f2a5a50

Comment 13 errata-xmlrpc 2016-06-29 16:03:15 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:1348


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