Details
-
Bug
-
Resolution: Fixed
-
Minor
-
COmanage Registry 4.2.0 (Pacific Pier)
-
RHEL 8.7, Registry 4.2.0, PHP 8.1.18
Description
We have a CO template configured with kafka servers for API Source-based organizational identity sources. When we duplicate the template CO, the basic server info is copied over, but we receive a No CO Specified error when we try to access the kafka configuration for those servers (see attached screenshots).
We've examined the cm_kafka_servers table, and the duplicate process is not creating a new record association between the kafka configuration and server records. Manually adding new cm_kafka_servers records with server_id equal to the newly created server record ids allows us to access and configure empty kafka configurations for the servers in the new CO.