ZohoCRM fails to discover catalog on production accounts

Connector Questions & Issues
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu
  • Memory / Disk: -
  • Deployment: Kubernetes
  • Airbyte Version: 0.40.29
  • Source name/version: Zoho CRM
  • Destination name/version: 0.1.0
  • Step: During discover catalog

Hi,

ZohoCRM fails to discover catalog on zoho production accounts. Error seems to be “Key Error: modules not found”

any ideas?

Here are the complete logs:

2023-02-16 09:48:29 e[32mINFOe[m i.a.w.p.KubeProcessFactory(create):96 - Attempting to start pod = zoho-crm-discover-2ead65bc-47e5-441b-8aa8-658f87a01688-0-nzvch for airbyte/source-zoho-crm:0.1.0 with resources io.airbyte.config.ResourceRequirements@2a537bd7[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=]
2023-02-16 09:48:29 e[32mINFOe[m i.a.w.p.KubeProcessFactory(create):99 - zoho-crm-discover-2ead65bc-47e5-441b-8aa8-658f87a01688-0-nzvch stdoutLocalPort = 9020
2023-02-16 09:48:29 e[32mINFOe[m i.a.w.p.KubeProcessFactory(create):102 - zoho-crm-discover-2ead65bc-47e5-441b-8aa8-658f87a01688-0-nzvch stderrLocalPort = 9021
2023-02-16 09:48:29 e[32mINFOe[m i.a.w.p.KubePodProcess(lambda$setupStdOutAndStdErrListeners$10):602 - Creating stdout socket server…
2023-02-16 09:48:29 e[32mINFOe[m i.a.w.p.KubePodProcess():533 - Creating pod zoho-crm-discover-2ead65bc-47e5-441b-8aa8-658f87a01688-0-nzvch…
2023-02-16 09:48:29 e[32mINFOe[m i.a.w.p.KubePodProcess(lambda$setupStdOutAndStdErrListeners$11):620 - Creating stderr socket server…
2023-02-16 09:48:29 e[32mINFOe[m i.a.w.p.KubePodProcess(waitForInitPodToRun):313 - Waiting for init container to be ready before copying files…
2023-02-16 09:48:29 e[32mINFOe[m i.a.w.p.KubePodProcess(waitForInitPodToRun):317 - Init container present…
2023-02-16 09:48:31 e[32mINFOe[m i.a.w.p.KubePodProcess(waitForInitPodToRun):320 - Init container ready…
2023-02-16 09:48:31 e[32mINFOe[m i.a.w.p.KubePodProcess():564 - Copying files…
2023-02-16 09:48:31 e[32mINFOe[m i.a.w.p.KubePodProcess(copyFilesToKubeConfigVolume):262 - Uploading file: source_config.json
2023-02-16 09:48:31 e[32mINFOe[m i.a.w.p.KubePodProcess(copyFilesToKubeConfigVolume):270 - kubectl cp /tmp/532a72f5-c916-4e6b-a180-ebf9ab0ddc51/source_config.json airbyte/zoho-crm-discover-2ead65bc-47e5-441b-8aa8-658f87a01688-0-nzvch:/config/source_config.json -c init
2023-02-16 09:48:31 e[32mINFOe[m i.a.w.p.KubePodProcess(copyFilesToKubeConfigVolume):273 - Waiting for kubectl cp to complete
2023-02-16 09:48:31 e[32mINFOe[m i.a.w.p.KubePodProcess(copyFilesToKubeConfigVolume):287 - kubectl cp complete, closing process
2023-02-16 09:48:31 e[32mINFOe[m i.a.w.p.KubePodProcess(copyFilesToKubeConfigVolume):262 - Uploading file: FINISHED_UPLOADING
2023-02-16 09:48:31 e[32mINFOe[m i.a.w.p.KubePodProcess(copyFilesToKubeConfigVolume):270 - kubectl cp /tmp/a9d42a80-8323-453a-a3e8-cfeac7bde2f3/FINISHED_UPLOADING airbyte/zoho-crm-discover-2ead65bc-47e5-441b-8aa8-658f87a01688-0-nzvch:/config/FINISHED_UPLOADING -c init
2023-02-16 09:48:31 e[32mINFOe[m i.a.w.p.KubePodProcess(copyFilesToKubeConfigVolume):273 - Waiting for kubectl cp to complete
2023-02-16 09:48:32 e[32mINFOe[m i.a.w.p.KubePodProcess(copyFilesToKubeConfigVolume):287 - kubectl cp complete, closing process
2023-02-16 09:48:32 e[32mINFOe[m i.a.w.p.KubePodProcess():567 - Waiting until pod is ready…
2023-02-16 09:48:32 e[32mINFOe[m i.a.w.p.KubePodProcess(lambda$setupStdOutAndStdErrListeners$10):611 - Setting stdout…
2023-02-16 09:48:33 e[32mINFOe[m i.a.w.p.KubePodProcess(lambda$setupStdOutAndStdErrListeners$11):623 - Setting stderr…
2023-02-16 09:48:33 e[32mINFOe[m i.a.w.p.KubePodProcess():583 - Reading pod IP…
2023-02-16 09:48:33 e[32mINFOe[m i.a.w.p.KubePodProcess():585 - Pod IP: 10.10.0.231
2023-02-16 09:48:33 e[32mINFOe[m i.a.w.p.KubePodProcess():592 - Using null stdin output stream…
2023-02-16 09:48:33 e[32mINFOe[m i.a.w.i.VersionedAirbyteStreamFactory(create):102 - Reading messages from protocol version 0.2.0
2023-02-16 09:48:34 e[1;31mER e
File “/usr/local/lib/python3.7/site-packages/airbyte_cdk/entrypoint.py”, line 127, in launch
for message in source_entrypoint.run(parsed_args):
File “/usr/local/lib/python3.7/site-packages/airbyte_cdk/entrypoint.py”, line 112, in run
catalog = self.source.discover(self.logger, config)
File “/usr/local/lib/python3.7/site-packages/airbyte_cdk/sources/abstract_source.py”, line 72, in discover
streams = [stream.as_airbyte_stream() for stream in self.streams(config=config)]
File “/airbyte/integration_code/source_zoho_crm/source.py”, line 35, in streams
return stream_factory.produce()
File “/airbyte/integration_code/source_zoho_crm/streams.py”, line 131, in produce
modules = self._init_modules_meta()
File “/airbyte/integration_code/source_zoho_crm/streams.py”, line 112, in _init_modules_meta
modules_meta_json = self.api.modules_settings()
File “/airbyte/integration_code/source_zoho_crm/api.py”, line 82, in modules_settings
return self._json_from_path(“/crm/v2/settings/modules”, key=“modules”)
File “/airbyte/integration_code/source_zoho_crm/api.py”, line 76, in _json_from_path
return response.json()[key]
KeyError: ‘modules’
2023-02-16 09:48:35 e[32mINFOe[m i.a.w.p.KubePodProcess(close):721 - (pod: airbyte / zoho-crm-discover-2ead65bc-47e5-441b-8aa8-658f87a01688-0-nzvch) - Closed all resources for pod
2023-02-16 09:48:35 e[33mWARNe[m i.a.w.g.DefaultDiscoverCatalogWorker(run):107 - Discover job subprocess finished with exit codee 1
2023-02-16 09:48:35 e[32mINFOe[m i.a.w.t.TemporalAttemptExecution(lambda$getWorkerThread$5):198 - Completing future exceptionally…
io.airbyte.workers.exception.WorkerException: Integration failed to output a catalog struct and did not output a failure reason
at io.airbyte.workers.WorkerUtils.throwWorkerException(WorkerUtils.java:198) ~[io.airbyte-airbyte-commons-worker-0.40.29.jar:?]
at io.airbyte.workers.general.DefaultDiscoverCatalogWorker.run(DefaultDiscoverCatalogWorker.java:120) ~[io.airbyte-airbyte-commons-worker-0.40.29.jar:?]
at io.airbyte.workers.general.DefaultDiscoverCatalogWorker.run(DefaultDiscoverCatalogWorker.java:43) ~[io.airbyte-airbyte-commons-worker-0.40.29.jar:?]
at io.airbyte.workers.temporal.TemporalAttemptExecution.lambda$getWorkerThread$5(TemporalAttemptExecution.java:195) ~[io.airbyte-airbyte-workers-0.40.29.jar:?]
at java.lang.Thread.run(Thread.java:1589) ~[?:?]
2023-02-16 09:48:35 e[32mINFOe[m i.a.w.t.TemporalAttemptExecution(get):163 - Stopping cancellation check scheduling…
2023-02-16 09:48:35 e[33mWARNe[m i.t.i.a.ActivityTaskExecutors$BaseActivityTaskExecutor(execute):114 - Activity failure. ActivityId=73feca51-78d2-334a-8acb-eb2a2979b4a9, activityType=Run, attempt=1
java.util.concurrent.ExecutionException: io.airbyte.workers.exception.WorkerException: Integration failed to output a catalog struct and did not output a failure reason
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396) ~[?:?]
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073) ~[?:?]
at io.airbyte.workers.temporal.TemporalAttemptExecution.get(TemporalAttemptExecution.java:161) ~[io.airbyte-airbyte-workers-0.40.29.jar:?]
at io.airbyte.workers.temporal.discover.catalog.DiscoverCatalogActivityImpl.run(DiscoverCatalogActivityImpl.java:125) ~[io.airbyte-airbyte-workers-0.40.29.jar:?]
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:578) ~[?:?]
at io.temporal.internal.activity.RootActivityInboundCallsInterceptor$POJOActivityInboundCallsInterceptor.executeActivity(RootActivityInboundCallsInterceptor.java:64) ~[temporal-sdk-1.17.0.jar:?]
at io.temporal.internal.activity.RootActivityInboundCallsInterceptor.execute(RootActivityInboundCallsInterceptor.java:43) ~[temporal-sdk-1.17.0.jar:?]
at io.temporal.internal.activity.ActivityTaskExecutors$BaseActivityTaskExecutor.execute(ActivityTaskExecutors.java:95) ~[temporal-sdk-1.17.0.jar:?]
at io.temporal.internal.activity.ActivityTaskHandlerImpl.handle(ActivityTaskHandlerImpl.java:92) ~[temporal-sdk-1.17.0.jar:?]
at io.temporal.internal.worker.ActivityWorker$TaskHandlerImpl.handleActivity(ActivityWorker.java:241) ~[temporal-sdk-1.17.0.jar:?]
at io.temporal.internal.worker.ActivityWorker$TaskHandlerImpl.handle(ActivityWorker.java:206) ~[temporal-sdk-1.17.0.jar:?]
at io.temporal.internal.worker.ActivityWorker$TaskHandlerImpl.handle(ActivityWorker.java:179) ~[temporal-sdk-1.17.0.jar:?]
at io.temporal.internal.worker.PollTaskExecutor.lambda$process$0(PollTaskExecutor.java:93) ~[temporal-sdk-1.17.0.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.lang.Thread.run(Thread.java:1589) ~[?:?]
Caused by: io.airbyte.workers.exception.WorkerException: Integration failed to output a catalog struct and did not output a failure reason
at io.airbyte.workers.WorkerUtils.throwWorkerException(WorkerUtils.java:198) ~[io.airbyte-airbyte-commons-worker-0.40.29.jar:?]
at io.airbyte.workers.general.DefaultDiscoverCatalogWorker.run(DefaultDiscoverCatalogWorker.java:120) ~[io.airbyte-airbyte-commons-worker-0.40.29.jar:?]
at io.airbyte.workers.general.DefaultDiscoverCatalogWorker.run(DefaultDiscoverCatalogWorker.java:43) ~[io.airbyte-airbyte-commons-worker-0.40.29.jar:?]
at io.airbyte.workers.temporal.TemporalAttemptExecution.lambda$getWorkerThread$5(TemporalAttemptExecution.java:195) ~[io.airbyte-airbyte-workers-0.40.29.jar:?]
… 1 more

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team