Bug 1283683 - Utilization button not working for containers
Utilization button not working for containers
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: GA
: 5.5.0
Assigned To: Daniel Korn
Avi Tal
: 1285548 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2015-11-19 10:03 EST by Daniel Korn
Modified: 2016-04-22 00:59 EDT (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-12-08 08:49:19 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
verified screenshot (740.50 KB, image/png)
2015-12-02 04:10 EST, Avi Tal
no flags Details

  None (edit)
Description Daniel Korn 2015-11-19 10:03:27 EST
Description of problem:
When clicking the "Utilization" button in a container the UI crashes with the exception: "Action not implemented [container/x_button]"

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

How reproducible:

Steps to Reproduce:
1. Navigate to the containers list page (Containers > Containers)
2. Choose a specific container from the list
3. press "Monitoring" drop-down > click "Utilization"

Actual results:
crash with the error: "Action not implemented [container/x_button]"

Expected results:
navigate to utilization page

Additional info:
Comment 2 Federico Simoncelli 2015-11-26 08:49:53 EST
Comment 4 Federico Simoncelli 2015-12-01 03:45:48 EST
*** Bug 1285548 has been marked as a duplicate of this bug. ***
Comment 5 Avi Tal 2015-12-02 04:10 EST
Created attachment 1101366 [details]
verified screenshot
Comment 6 Avi Tal 2015-12-02 04:10:56 EST
Comment 8 errata-xmlrpc 2015-12-08 08:49:19 EST
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.


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