Fixed Issues in Cloudera Manager 7.2.0
Issues that have been fixed in Cloudera Manager since the previous release.
- Cloudera Bug: OPSAPS-56457: Schema Registry yaml file generation broken on Azure.
- The YAML file is now generated correctly.
- Cloudera Bug: OPSAPS-55564: Increase the max length of configuration values in the Postgresql schema
- The maximum size of a configuration value that can be persisted when running on PostgresSQL has been increased from 1 MiB to 1GiB, which more closely matches the behavior of Oracle and MySQL databases.
- Cloudera Bug: OPSAPS-56269: Multiple Operational Database clusters should use different Ranger policies
- Issue has been fixed.
- Cloudera Bug: OPSAPS-55387: NPE during Cloudera Manager cluster template importing
- Fixed a bug that caused a null pointer exception when importing cluster templates.
- Cloudera Bug: OPSAPS-56286: Schema Registry Health Check broken with multiple instances
- Heath test fixed for Schema Registry when there are multiple instances of Schema Registry deployed.
- Cloudera Bug: OPSAPS-56345: Issues with Schema Registry's Ranger repo handling
- Ranger init script was rewritten to generate the repo name with a unique name. It will also not fail in case the repo already exists.
- Cloudera Bug: OPSAPS-56650: Generate Missing Credentials Fails due to issue with 'ldapdelete' command
- The components in DomainNames (DNs) viz. cn, dc, ou are valid even with whitespaces due to which the generate missing credentials script in Cloudera Manager failed. This is now fixed.
- Cloudera Bug: OPSAPS-56210: Upgrade failed with Oracle12 with "Failed to Create Hive Sys Database"
- Fix to the COLUMN name in the Oracle schema file.
- Cloudera Bug: OPSAPS-57000: Disable IDBroker token renewal
- Modified IDBroker configuration so that server-management of token state is disabled (token renewal/revocation is also disabled as a result).
- Cloudera Bug: OPSAPS-56442: Deploying CB template results in Error
- We opened two follow-up jiras based on further testing and debugging. Hence marking this as resolved. https://jira.cloudera.com/browse/OPSAPS-56576 https://jira.cloudera.com/browse/CDPD-12612
- Cloudera Bug: OPSAPS-53101: Hue cannot install sample_07 table, connection error
- This issue has been fixed.
- Cloudera Bug: OPSAPS-54424: yarn_kerberos_cluster installation failure: Failed to generate client configuration. (error 500)
- The Deploy client configuration command can fail easily if the HostStatus of the host heartbeat that includes component version is not received for hadoop-mapreduce. This command now waits for these heartbeats,
