Troubleshooting Cloudera Manager (Cloudera Manager server) Migration in an Cloudera Embedded Container Service Cluster

Users migrating their Cloudera Manager server to a new host within an Cloudera Embedded Container Service (Data Services) cluster might encounter issues where the Cloudera Embedded Container Service environment remains linked to the old Cloudera Manager host.

This scenario could lead to unauthorized access or connection refused errors, preventing the Cloudera Data Catalog, Virtual Warehouse, and Cloudera AI Workspaces from functioning as expected.

What to do next

To address this issue you must maintain a proper migration workflow that involves three main steps:

Ensure that the new Cloudera Manager host is fully operational
Manually update the cmHost value in the Cloudera Embedded Container Service database
Validate and troubleshoot

Confirm that Cloudera Manager and all services are up and running on the new host.
Validate the general Cloudera Manager migration process using Moving the Cloudera Manager Server to a New Host.
Since Cloudera Embedded Container Service does not automatically update the Cloudera Manager host, the cmHost entry must be manually modified in the Cloudera Embedded Container Service embedded database using the following commands:
```
kubectl -n cdp exec -it cdp-embedded-db-0 – - bash
psql
\c db-env
\dt
\d configs
SELECT * FROM configs WHERE attr= 'cmHost';
UPDATE configs SET value = 'https://<NEW_CM_HOST>:7183' WHERE attr = 'cmHost';
```
- Replace <NEW_CM_HOST> with the hostname or IP of the new Cloudera Manager server. For example: hostname.domain.com
- Restart Cloudera Embedded Container Service services to ensure the changes take effect.
Confirm that Cloudera Embedded Container Service components (Cloudera Data Catalog, Virtual Warehouse, and Cloudera AI Workspaces) are properly connected to the new Cloudera Manager host and are functioning correctly.