Cloudera Docs

Known issues

Learn about the known issues in Cloudera Data Catalog, the impact or changes to the functionality, and the workaround.

Known Issues in Cloudera Data Catalog 1.5.5

The following issues were identified in Cloudera Data Catalog 1.5.5.

CDPDSS-4019: Profiler pods are stuck in init state
The CDP_ACCESS_KEY_ID and CDP_PRIVATE_KEY keys do not receive values when installing from Cloudera Data Catalog 1.5.5.
  1. Use the following command to restart the DSS App: kubectl rollout restart deployment/cdp-release-dssapp -n <namespace>
  2. Delete and relaunch the profilers after the upgrade.

Known issues carried from Cloudera Data Catalog 1.5.4

The following issues were identified in Cloudera Data Catalog 1.5.4.

CDPDSS-3472: Profiler jobs are showing up twice when two data lakes are present
Cloudera Data Catalog does not support more than one data lakes (or base clusters). Connecting two data lakes will result in all profiler jobs showing as duplicated in the Profilers page.

Known issues carried from Cloudera Data Catalog 1.5.3

The following issues were identified in Cloudera Data Catalog 1.5.3.

There are no unresolved issues in this release applicable to Cloudera Data Catalog 1.5.5.

Known issues carried from Cloudera Data Catalog 1.5.2

The following issues were identified in Cloudera Data Catalog 1.5.2.

CDPDSS-2706: Data Steward user role is not reflecting
Data Steward role is not reflecting in Control Plane.
None
CDPDSS-3346: Profiler pods are stuck in init state
The CDP_ACCESS_KEY_ID and CDP_PRIVATE_KEY keys do not receive values when upgrading from Cloudera Data Catalog 1.5.2 to 1.5.4.
  1. Use the following command to restart the DSS App: kubectl rollout restart deployment/cdp-release-dssapp -n <namespace>
  2. Delete and relaunch the profilers after the upgrade.
CDPDSS-3057: Failed profiler job because of missing columns in log entries.
When the logs to be profiled by the Ranger Audit Profiler have missing columns, the profiling job fails. The ranger audit profiler pod log contains the following message:Ranger Audit Profiler failed: Failed to run Ranger Audit Profiler. Error: "['column1', 'column2', ...] not in index".

column1, column2 show the missing column entries in the logs.

Each Ranger audit profiler job has 3 sub-jobs (identified by the same job ID prefix), any of which could fail because of the above reason. It is possible that one or even two sub-jobs pass till the above scenario is encountered.

None