Known Issues in Cloudera Runtime 7.2.18.800

You can review the list of reported known issues in Cloudera Runtime 7.2.18.800.

CDPD-81958: Improve Cookie Security in Knox-Proxied Web UIs with Secure and HttpOnly Attributes: The pac4jCsrfToken cookie has neither HttpOnly nor Secure flags in Knox proxied applications. This can lead to the cookie being sent over an unencrypted HTTP connection resulting in a security risk.; The cookie flags are provided from Cloudera Runtime 7.2.18.1000.
CDPD-27801: Knox is missing HSTS header for HTTP 404 responses: HTTP Strict-Transport-Security response header (HSTS) is missing for HTTP 404 responses in Knox.; None.
CDPD-79144: Incorrect schema version in Hive schema initialization script for MySQL: Cluster creation with Cloudera Public Cloud Base 7.2.18.600 fails due to an incorrect database schema version in the CDH_VERSION table. The schema version is set to 3.1.3000.7.2.18.0-Update1, but it should be 3.1.3000.7.2.18.0-Update2. This mismatch causes schema validation failure in Hive Metastore.; Manually update the schema version in the CDH_VERSION table:

Go to Cloudera Manager > Hive Configuration and retrieve database details (host, name, username).

Log in to the Metastore host and switch to the root user: sudo su -

Activate the Salt environment: source activate_salt_env

Retrieve the Hive database credentials:salt-call pillar.get postgres

Connect to the database: psql -h <hostname> -U hive -p

Update the schema version: UPDATE "CDH_VERSION" SET "SCHEMA_VERSION" = '3.1.3000.7.2.18.0-Update2' WHERE "VER_ID" = 1;

important
Take a database backup before applying these steps
CDPD-81554: Without permission for one glossary, /glossary call throws exception: When you don't have the permission for a glossary, the /glossary call results in a exception, blocking authorization for all glossaries. The error message is the following:
{ "errorCode": "ATLAS-403-00-001", "errorMessage": "hrt_qa is not authorized to perform read entity: guid=*********-****-****-****-*******"}
CDPD-67942: Atlas can't search Chinese/Japanese comment properly: Entities whose comments contain Chinese or Japanese characters cannot be searched by using the comment (string), containing filters.
CDPD-69910, CDPD-79161: NPE while deleting BusinessMetadata: If business metadata is created without adding any applicable types, a NullPointerException is produced when trying to delete that business metadata.; None; Apache Jira: ATLAS-4863
CDPD-82057: UI: when server response date fields as '0', UI shows as current time: If an API response contains an invalid date value (such as 0) intended for display on the user interface, the current system date is shown. This issue specifically affects the Entity Detail page, where the create time and modified time are displayed.; Apache JIRA: ATLAS-5015
CDPD-76789: Creating tag with name description throws java.lang.ClassCastException: Creating classification with reserved names such as "name", "description", "owner", "version", "serviceType" and "options" can lead to HTTP 500 error in Apache Atlas.; Avoid creating classification with reserved names such as "name", "description", "owner", "version", "serviceType" and "options".
CDPD-77435: RAZ: Import-hive on Cloudera Data Engineering cluster fails: Running import-hive command on RAZ enabled Cloudera Data Engineering cluster fails with error "NoClassDefFoundError: com/sun/jersey/core/spi/factory/ResponseBuilderImpl".
CDPD-75994: Post DL regular upgrade (non ZDU) to 7.3.1, "Exception in getKafkaConsumer ,WakeupException: null" is seen: After the data lake is upgraded to 7.3.1, sometimes Atlas Hook does not function when Apache Atlas and Apache Kafka are started at the same time, thus Atlas is unable to connect to Kafka while Kafka is still being set up. Atlas performs only three attempts.
Restart the cluster, after the upgrade to trigger to reconnect to Apache Kafka. The Kafka consumer creation should be retried if the Kafka service is unavailable during Atlas startup.
CDPD-76035: Resource lookup for Atlas service is failing: Once the Atlas configuration snippet atlas.authentication.method.file is enabled and a classification is created, these do not synchronize correctly to the Type Category resource field setting of Apache Ranger. The newly created classification won't be able to be selected as the Type Name.
DOCS-26821: Iceberg entities created in 7.2.17 Atlas-Hook (Hive,Impala,Spark) is not ingested by 7.2.18/7.3.1 Atlas Server: When using an Atlas hook from 7.2.18 or later version (7.3.1) with an earlier version of Atlas server (7.2.17 or earlier) to create an Iceberg table, the older data model of Iceberg cannot process the features of the new data models. For example, when encountering relationships or attributes in queries which do not have a definition in the earlier model, Iceberg fails to create new tables with an error message. The data model of the Iceberg in Cloudera Runtime 7.2.18 or later is not backward compatible with earlier data models.; It is recommended to upgrade your Atlas server version to at least 7.2.18 or later.
CDPD-87670: [Atlas UI] Apache Atlas Glossary becomes unresponsive when the page size is set to 50: When the page limit is set to 50 in Glossary, the user interface becomes unresponsive due to an incorrect API call with the error message, when trying to show more than 25 associated entities for a glossary item: "expected type AtlasGlossaryCategory; found AtlasGlossaryTerm".; Apache Jira: ATLAS-5067
CDPD-28741: Atlas node start failure : PermanentLockingException: Expected value mismatch for KeyColumn: In an Atlas High Availability (HA) enabled environment, starting both Atlas hosts at the same time can result in both trying to access or modify the same graph database resulting in a race condition. One instance successfully modifies the patch vertex, while the other instance triggers a Locking Exception (Concurrent modification exception).; Start Atlas instances in sequence and not in parallel to avoid the potential race condition. If the exception is already present, restart the second Atlas instance after triggering the PermanentLockingException.