Bug 1430013 - Failure adding scope in Compliance Policy/Control Policy
Summary: Failure adding scope in Compliance Policy/Control Policy
Keywords:
Status: CLOSED DUPLICATE of bug 1434896
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Harpreet Kataria
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-07 16:22 UTC by Pavel Zagalsky
Modified: 2017-12-26 14:59 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-26 08:11:58 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pavel Zagalsky 2017-03-07 16:22:29 UTC
Description of problem:
Infninte spinner will appear when pressing on "???" in new Container Image Compliance Policy/Control Policy menus


How reproducible:
Always

Steps to Reproduce:
1. Control --> Explorer --> Policies --> Compliance Policies 
2. Press on Configuration --> Add new Container Image Compliance Policy
3. Press on the "???" button (href="/miq_policy/exp_token_pressed?token=1")

Actual results:
Infinite spinner appears

Expected results:
The user should be able to add Scope of the Compliance Policy


Additional info:
This is the error that appears in evm.log:
[----] E, [2017-03-07T11:16:43.633589 #17863:10dd134] ERROR -- : MIQ(ManageIQ::Providers::OpenshiftEnterprise::ContainerManager::Refresher#fetch_hawk_inv) <html>

Comment 2 Federico Simoncelli 2017-03-15 08:29:35 UTC
Pavel can you check if this happen for the other entities as well (for example VMs, etc.). Thanks.

Comment 3 Pavel Zagalsky 2017-04-23 07:24:16 UTC
I observe the same behaviour when attempting to add a new VM and Instance Compliance Policy.
At the latest version (5.8.0.11) I see the spinner very briefly without any following action

Comment 4 Federico Simoncelli 2017-04-24 07:51:28 UTC
Based on comment 3 this seems to be generic (not container specific).

Comment 5 Dave Johnson 2017-07-14 02:50:11 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.

Comment 7 Pavel Zagalsky 2017-12-26 08:11:58 UTC

*** This bug has been marked as a duplicate of bug 1434896 ***


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