Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

[CM 5.4]: The feature Operational Reports is not available. (error 500)

Solved Go to solution

[CM 5.4]: The feature Operational Reports is not available. (error 500)

Rising Star

Why trying to create CMS service via CM API, getting the error below.

However, CMS service is created

#######################################################################################

scm=> select * from services;
 service_id | optimistic_lock_version | name | service_type | cluster_id | maintenance_count |        display_name
| generation
------------+-------------------------+------+--------------+------------+-------------------+-----------------------------
+------------
          1 |                       1 | mgmt | MGMT         |            |                 0 | Cloudera Management Service
|          1
(1 row)

#######################################################################################

but I can NOT start CMS service!!!

 

It is not clear to me what roles are allowed under what type of licensing (enterprise vs community).

Here are the roles that have been created:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

scm=> select * from roles;
 role_id |       name        | host_id |    role_type    | configured_status | service_id | merged_keytab | maintenance_cou
nt | decommission_count | optimistic_lock_version | role_config_group_id | has_ever_started
---------+-------------------+---------+-----------------+-------------------+------------+---------------+----------------
---+--------------------+-------------------------+----------------------+------------------
       1 | ACTIVITYMONITOR-1 |       1 | ACTIVITYMONITOR | STOPPED           |          1 |               |
 0 |                  0 |                       0 |                    4 | f
       2 | ALERTPUBLISHER-1  |       1 | ALERTPUBLISHER  | STOPPED           |          1 |               |
 0 |                  0 |                       0 |                    2 | f
       3 | EVENTSERVER-1     |       1 | EVENTSERVER     | STOPPED           |          1 |               |
 0 |                  0 |                       0 |                    3 | f
       4 | HOSTMONITOR-1     |       1 | HOSTMONITOR     | STOPPED           |          1 |               |
 0 |                  0 |                       0 |                    7 | f
       5 | SERVICEMONITOR-1  |       1 | SERVICEMONITOR  | STOPPED           |          1 |               |
 0 |                  0 |                       0 |                    6 | f
(5 rows)

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

but again I cannot start them!!!!

 

I have run the same exact CM API script in CM 5.3 and it works without any issues!!!!!

 

Here is the error getting by executing a CM API python script:

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>

Traceback (most recent call last):
  File "./deploy_cms_service.py", line 238, in <module>
    main()
  File "./deploy_cms_service.py", line 222, in main
    RMAN_ROLE_CONFIG)
  File "./deploy_cms_service.py", line 151, in deploy_management
    mgmt.create_role(rman_role_name + "-1", "REPORTSMANAGER", CM_HOST)
  File "/usr/lib/python2.6/site-packages/cm_api-6.0.2-py2.6.egg/cm_api/endpoints/services.py", line 403, in create_role
    role_name, host_id, self._get_cluster_name())
  File "/usr/lib/python2.6/site-packages/cm_api-6.0.2-py2.6.egg/cm_api/endpoints/roles.py", line 53, in create_role
    ApiRole, True, data=[apirole])[0]
  File "/usr/lib/python2.6/site-packages/cm_api-6.0.2-py2.6.egg/cm_api/endpoints/types.py", line 137, in call
    ret = method(path, data=data, params=params)
  File "/usr/lib/python2.6/site-packages/cm_api-6.0.2-py2.6.egg/cm_api/resource.py", line 138, in post
    self._make_headers(contenttype))
  File "/usr/lib/python2.6/site-packages/cm_api-6.0.2-py2.6.egg/cm_api/resource.py", line 63, in invoke
    headers=headers)
  File "/usr/lib/python2.6/site-packages/cm_api-6.0.2-py2.6.egg/cm_api/http_client.py", line 161, in execute
    raise self._exc_class(ex)
cm_api.api_client.ApiException: The feature Operational Reports is not available. (error 500)

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: [CM 5.4]: The feature Operational Reports is not available. (error 500)

Rising Star

After I commented out the portion of my script that creates the RMAN role and rerun the script it worked!

 

3 REPLIES 3

Re: [CM 5.4]: The feature Operational Reports is not available. (error 500)

Rising Star

I have read this similar thread but it is not clear how it got resolved!

 

https://community.cloudera.com/t5/Cloudera-Manager-Installation/Server-Error-The-feature-Operational...

 

Highlighted

Re: [CM 5.4]: The feature Operational Reports is not available. (error 500)

Rising Star

After I commented out the portion of my script that creates the RMAN role and rerun the script it worked!

 

Re: [CM 5.4]: The feature Operational Reports is not available. (error 500)

Community Manager
Awesome! Glad to see that you found the solution.



Cy Jervis, Community Manager

Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

Learn more about the Cloudera Community:
Community Guidelines
How to use the forum
Don't have an account?
Coming from Hortonworks? Activate your account here