Bug 1332866

Summary: Metrics roles are shown as enabled in the UI but not running in the backend
Product: Red Hat CloudForms Management Engine Reporter: Einat Pacifici <epacific>
Component: C&U Capacity and UtilizationAssignee: Greg Blomquist <gblomqui>
Status: CLOSED ERRATA QA Contact: Einat Pacifici <epacific>
Severity: high Docs Contact:
Priority: high    
Version: 5.6.0CC: cpelland, epacific, fsimonce, jhardy, llange, nachandr, obarenbo, simaishi, snaim, yzamir
Target Milestone: GAKeywords: Reopened
Target Release: 5.6.0Flags: snaim: automate_bug+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.6.0.8 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-29 15:57:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
SHowing configuration in CFME
none
Screenshot showing no C&U Roles none

Comment 1 Einat Pacifici 2016-05-04 12:03:17 UTC
Created attachment 1153819 [details]
SHowing configuration in CFME

Comment 3 Federico Simoncelli 2016-05-06 08:15:07 UTC
Greg, based on the screenshot and my email thread, it seems that Einat enabled C&U but the roles are not persisted/considered:

 roles=automate:database_operations:database_owner:ems_inventory:ems_operations:event:reporting:scheduler:smartstate:user_interface:web_services:websocket


I am moving this back to you (infra) but feel free to close the BZ with INSUFFICIENT_DATA given that she didn't attach any log.

Comment 6 Greg Blomquist 2016-05-20 15:44:01 UTC
Created attachment 1159986 [details]
Screenshot showing no C&U Roles

Closing this as notabug.

There are no C&U Roles enabled for the appliance.

Comment 7 Greg Blomquist 2016-05-20 15:47:33 UTC
I logged into the appliance and verified that in the DB there are no C&U server roles enabled.  And I logged into the UI and verified that there are no C&U server roles selected in the UI (see "Screenshot showing no C&U Roles" screen shot).

Query showing now C&U roles
------------------------------------------------------------------------------
vmdb_production=# select a.id, s.id, s.name, r.id, r.name, a.active, a.priority 
                  from assigned_server_roles a, server_roles r, miq_servers s 
                  where a.miq_server_id = s.id and a.server_role_id = r.id;
 id | id | name | id |        name         | active | priority 
----+----+------+----+---------------------+--------+----------
  1 |  1 | EVM  |  1 | automate            | t      |        2
  2 |  1 | EVM  |  2 | database_operations | t      |        2
  3 |  1 | EVM  |  5 | ems_inventory       | t      |        2
  4 |  1 | EVM  |  9 | ems_operations      | t      |        2
  5 |  1 | EVM  | 10 | event               | t      |        2
  6 |  1 | EVM  | 13 | reporting           | t      |        2
  7 |  1 | EVM  | 15 | scheduler           | t      |        2
  8 |  1 | EVM  | 17 | smartstate          | t      |        2
  9 |  1 | EVM  | 22 | user_interface      | t      |        2
 10 |  1 | EVM  | 24 | websocket           | t      |        2
 11 |  1 | EVM  | 25 | web_services        | t      |        2
 12 |  1 | EVM  |  3 | database_owner      | t      |        2
 13 |  1 | EVM  | 16 | smartproxy          | t      |        2
(13 rows)
------------------------------------------------------------------------------

Closing as notabug.

Comment 12 Federico Simoncelli 2016-05-30 22:13:29 UTC
*** Bug 1340172 has been marked as a duplicate of this bug. ***

Comment 15 Greg Blomquist 2016-05-31 14:34:25 UTC
Nick C. noticed that this bug is likely related to PR 8798.

https://github.com/ManageIQ/manageiq/pull/8798

Comment 16 Einat Pacifici 2016-06-08 12:29:20 UTC
Verified in version 5.6.0.10-rc2.1
When C&U roles are assigned, Metrics rollups are viewable in CFME.

Comment 18 errata-xmlrpc 2016-06-29 15:57:20 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