QE notes about reproducer:

* try to enable and disable profiling via Tendrl UI
* while having web dev. console running

And check that errors don't appear during processing related api requests.

Tested and Verified on:
  tendrl-ansible-1.6.3-3.el7rhgs.noarch
  tendrl-api-1.6.3-3.el7rhgs.noarch
  tendrl-api-httpd-1.6.3-3.el7rhgs.noarch
  tendrl-commons-1.6.3-4.el7rhgs.noarch
  tendrl-grafana-plugins-1.6.3-2.el7rhgs.noarch
  tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
  tendrl-monitoring-integration-1.6.3-2.el7rhgs.noarch
  tendrl-node-agent-1.6.3-4.el7rhgs.noarch
  tendrl-notifier-1.6.3-2.el7rhgs.noarch
  tendrl-selinux-1.5.4-2.el7rhgs.noarch
  tendrl-ui-1.6.3-1.el7rhgs.noarch

Enabling or Disabling Volume level profiling doesn't send any data in the POST request 
  /api/1.0/clusters/<cluster-id>/volumes/<volume-id>/{start_profiling,stop_profiling}


NOTE:
  Enabling or Disabling Cluster vide volume profiling sends following data:
    {"Cluster.volume_profiling_flag":"disable"}
  or
    {"Cluster.volume_profiling_flag":"enable"}
  in the POST request /api/1.0/clusters/<cluster-id>/profiling, which is expected.

>> VERIFIED

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/RHSA-2018:2616