Bug 1440796 - SyntaxError when clicking on Refresh button for OpenStack Infra at Dashboard view
Summary: SyntaxError when clicking on Refresh button for OpenStack Infra at Dashboard ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.9.0
Assignee: Martin Povolny
QA Contact: Ola Pavlenko
URL:
Whiteboard: rhos:infra
Depends On:
Blocks: 1443082
TreeView+ depends on / blocked
 
Reported: 2017-04-10 13:35 UTC by Petr Blaho
Modified: 2018-03-06 14:48 UTC (History)
7 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1443082 (view as bug list)
Environment:
Last Closed: 2018-03-06 14:48:52 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Petr Blaho 2017-04-10 13:35:06 UTC
Description of problem:

Having OpenStack Infra provider and being on Dashboard view (http://localhost:3000/ems_infra/35?display=dashboard).

When I click on "Configuration" -> "Refresh Relationships and Power State" I got "exception caught evaling RJS" and "SyntaxError: expected expression, got '>'" as MIQ notifications and no refresh is triggered.

Server returns HTML when browser expects js.


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

Master of upstream repos for manageiq, manageiq-ui-classic and manageiq-providers-openstack.

How reproducible:

Easy.

Steps to Reproduce:
1. Go to Dashboard view of OpenStack Infra provider.
2. Click on "Configuration" -> "Refresh Relationships and Power State"
3. See notifications with errors - "exception caught evaling RJS" and "SyntaxError: expected expression, got '>'"

Actual results:

Notification with errors, html returned from server to browser instead of js and no refresh event scheduled/triggered for the provider.

Expected results:

No notification with error, probably notification with information that refresh is scheduled and actual refresh scheduled.

Additional info:


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