Hi Team. I have a problem when switching from helm...
# troubleshoot
r
Hi Team. I have a problem when switching from helm chart version 0.2.128 to version 0.2.129, with the same problem on version 0.2.130 (datahub 0.9.5 for this versions). Logs of
datahub-datahub-upgrade-job
:
Copy code
APPLICATION FAILED TO START Description:
Field kafkaHealthChecker in com.linkedin.gms.factory.kafka.DataHubKafkaEventProducerFactory required a bean of type 'com.linkedin.metadata.dao.producer.KafkaHealthChecker' that could not be found.
The injection point has the following annotations:
@javax.inject.Inject() @javax.inject.Named(value="noCodeUpgrade") Action: Consider defining a bean of type 'com.linkedin.metadata.dao.producer.KafkaHealthChecker' in your configuration.
✅ 2
👀 1
i
Hello Laurent, Can you share your values.yaml file?
r
Hello Pedro, yes of course, here it is
i
Could you update datahub version to v0.9.6.1 ?
And helm chart version to 0.2.141
r
So I have deployed version 0.2.133 of helm datahub. Actually I'm testing an incremental upgrade, but sometimes I have problems with some versions. Skipping some of them doesn't seem to be a problem.
i
We built the helm charts such that they should be bumped without effort on your side and usually the latest ones have flags/configs or otherwise for new datahub features being released. Once in a while these features are not helm-backwards compatible so it is best pratice to upgrade helm to the latest version with any upgrade of Datahub