Hi Team - we are seeing the following error in our gms logs when we are trying to deploy. This wasn’t the case when we deployed gms for the first time. Any pointers on fixing this
one or more objects failed to apply, reason: The order in patch list: [map[name:DATAHUB_UPGRADE_HISTORY_KAFKA_CONSUMER_GROUP_ID value:datahub-duhe-consumer-job-client-gms] map[name:DATAHUB_UPGRADE_HISTORY_KAFKA_CONSUMER_GROUP_ID value:datahub_staging-datahub-duhe-consumer-job-client-gms] map[name:SPRING_KAFKA_PROPERTIES_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM value:<nil>]] doesn't match $setElementOrder list: [map[name:SHOW_SEARCH_FILTERS_V2] map[name:SHOW_BROWSE_V2] map[name:BACKFILL_BROWSE_PATHS_V2] map[name:DATAHUB_UPGRADE_HISTORY_KAFKA_CONSUMER_GROUP_ID] map[name:DATAHUB_REVISION] map[name:ENABLE_PROMETHEUS] map[name:MCE_CONSUMER_ENABLED] map[name:MAE_CONSUMER_ENABLED] map[name:PE_CONSUMER_ENABLED] map[name:ENTITY_REGISTRY_CONFIG_PATH] map[name:DATAHUB_ANALYTICS_ENABLED] map[name:EBEAN_DATASOURCE_USERNAME] map[name:EBEAN_DATASOURCE_PASSWORD] map[name:EBEAN_DATASOURCE_HOST] map[name:EBEAN_DATASOURCE_URL] map[name:EBEAN_DATASOURCE_DRIVER] map[name:KAFKA_BOOTSTRAP_SERVER] map[name:KAFKA_SCHEMAREGISTRY_URL] map[name:SCHEMA_REGISTRY_TYPE] map[name:ELASTICSEARCH_HOST] map[name:ELASTICSEARCH_PORT] map[name:SKIP_ELASTICSEARCH_CHECK] map[name:ELASTICSEARCH_USE_SSL] map[name:GRAPH_SERVICE_IMPL] map[name:SPRING_KAFKA_PROPERTIES_KAFKASTORE_SECURITY_PROTOCOL] map[name:SPRING_KAFKA_PROPERTIES_KAFKASTORE_SSL_TRUSTSTORE_LOCATION] map[name:SPRING_KAFKA_PROPERTIES_KAFKASTORE_SSL_TRUSTSTORE_PASSWORD] map[name:SPRING_KAFKA_PROPERTIES_SASL_JAAS_CONFIG] map[name:SPRING_KAFKA_PROPERTIES_SASL_MECHANISM] map[name:SPRING_KAFKA_PROPERTIES_SECURITY_PROTOCOL] map[name:SPRING_KAFKA_PROPERTIES_SSL_ENABLED_PROTOCOLS] map[name:SPRING_KAFKA_PROPERTIES_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM] map[name:SPRING_KAFKA_PROPERTIES_SSL_PROTOCOL] map[name:SPRING_KAFKA_PROPERTIES_SSL_TRUSTSTORE_LOCATION] map[name:SPRING_KAFKA_PROPERTIES_SSL_TRUSTSTORE_PASSWORD] map[name:SPRING_KAFKA_PROPERTIES_SSL_TRUSTSTORE_TYPE] map[name:METADATA_CHANGE_EVENT_NAME] map[name:FAILED_METADATA_CHANGE_EVENT_NAME] map[name:METADATA_AUDIT_EVENT_NAME] map[name:DATAHUB_USAGE_EVENT_NAME] map[name:METADATA_CHANGE_PROPOSAL_TOPIC_NAME] map[name:FAILED_METADATA_CHANGE_PROPOSAL_TOPIC_NAME] map[name:METADATA_CHANGE_LOG_VERSIONED_TOPIC_NAME] map[name:METADATA_CHANGE_LOG_TIMESERIES_TOPIC_NAME] map[name:PLATFORM_EVENT_TOPIC_NAME] map[name:DATAHUB_UPGRADE_HISTORY_TOPIC_NAME] map[name:UI_INGESTION_ENABLED] map[name:UI_INGESTION_DEFAULT_CLI_VERSION] map[name:ELASTICSEARCH_QUERY_MAX_TERM_BUCKET_SIZE] map[name:ELASTICSEARCH_QUERY_EXACT_MATCH_EXCLUSIVE] map[name:ELASTICSEARCH_QUERY_EXACT_MATCH_WITH_PREFIX] map[name:ELASTICSEARCH_QUERY_EXACT_MATCH_FACTOR] map[name:ELASTICSEARCH_QUERY_EXACT_MATCH_PREFIX_FACTOR] map[name:ELASTICSEARCH_QUERY_EXACT_MATCH_CASE_FACTOR] map[name:ELASTICSEARCH_QUERY_EXACT_MATCH_ENABLE_STRUCTURED] map[name:ELASTICSEARCH_SEARCH_GRAPH_TIMEOUT_SECONDS] map[name:ELASTICSEARCH_SEARCH_GRAPH_BATCH_SIZE] map[name:ELASTICSEARCH_SEARCH_GRAPH_MAX_RESULT] map[name:SEARCH_SERVICE_ENABLE_CACHE] map[name:LINEAGE_SEARCH_CACHE_ENABLED] map[name:ELASTICSEARCH_INDEX_BUILDER_MAPPINGS_REINDEX] map[name:ELASTICSEARCH_INDEX_BUILDER_SETTINGS_REINDEX] map[name:ALWAYS_EMIT_CHANGE_LOG] map[name:GRAPH_SERVICE_DIFF_MODE_ENABLED] map[name:JAVA_OPTS] map[name:DATAHUB_USAGE_EVENT_KAFKA_CONSUMER_GROUP_ID] map[name:PLATFORM_EVENT_KAFKA_CONSUMER_GROUP_ID] map[name:DATAHUB_UPGRADE_HISTORY_KAFKA_CONSUMER_GROUP_ID] map[name:METADATA_CHANGE_EVENT_KAFKA_CONSUMER_GROUP_ID] map[name:METADATA_CHANGE_LOG_KAFKA_CONSUMER_GROUP_ID] map[name:METADATA_CHANGE_PROPOSAL_KAFKA_CONSUMER_GROUP_ID]]
Hey Dheeraj! Apologies for the delay here… <@U03MF8MU5P0> might have some pointers!
Hey Maggie - we fixed the issue. Apparently it was something to do with the way we added the extraEnvs. I removed it and it worked.
In our scenario, the release.name mentioned https://github.com/acryldata/datahub-helm/blob/master/charts/datahub/subcharts/datahub-gms/templates/deployment.yaml#L120C50-L120C50|here should match the username of our kafka ssl scram configuration otherwise it wouldn’t work.
ideally if that could be retrieved from values.yaml, it would be have been much simpler.