Cloudera Docs

Fixed Issues

This section lists the issues in Livy that are fixed in Cloudera Runtime 7.3.1 release, its service packs and cumulative hotfixes.

Cloudera Runtime 7.3.1.700 SP3 CHF 2

OPSAPS-76032: Livy fails to start due to misconfiguration of the filesystem scheme
Cloudera Manager prepended the default filesystem URL, resulting in an invalid URL with double slashes, preventing Livy from creating the recovery directory. This issue is now fixed, and Cloudera Manager truncates double slashes in the fs.defaultFS value.

Cloudera Runtime 7.3.1.600 SP3 CHF 1

There are no fixed issues in this release.

Cloudera Runtime 7.3.1.500 SP3

There are no fixed issues in this release.

Cloudera Runtime 7.3.1.400 SP2

There are no fixed issues in this release.

Cloudera Runtime 7.3.1.300 SP1 CHF 1

There are no fixed issues in this release.

Cloudera Runtime 7.3.1.200 SP1

There are no fixed issues in this release.

Cloudera Runtime 7.3.1.100 CHF 1

There are no new fixed issues in this release.

Cloudera Runtime 7.3.1

OPSAPS-71873 - UCL | CKP4| livyfoo0 kms proxy user is not allowed to access HDFS in 7.3.1.0
Cloudera Manager 7.13.1.0
In the kms-core.xml file, the Livy proxy user is taken from Livy for Spark 3's configuration in Cloudera on premises version 7.3.1 and above.
CDPD-73324 - LIVY_FOR_SPARK3 goes into down with Invalid Keystore format error in FIPS cluster
7.3.1
Fixed an issue that caused LIVY_FOR_SPARK3 to go into a bad state with Invalid Keystore format error in a 7.3.1 FIPS cluster.