great-branch-515
09/12/2022, 11:50 AMfull-chef-85630
09/12/2022, 1:39 PM../gradlew :metadata-ingestion:installDev
Failed to build python-ldap orderedset sasl3
ERROR: Could not build wheels for python-ldap, which is required to install pyproject.toml-based projects
> Task :metadata-ingestion:installDev FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':metadata-ingestion:installDev'.
> Process 'command 'bash'' finished with non-zero exit value 1
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at <https://help.gradle.org>
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See <https://docs.gradle.org/6.9.2/userguide/command_line_interface.html#sec:command_line_warnings>
BUILD FAILED in 4m 19s
26 actionable tasks: 9 executed, 17 up-to-date
cuddly-arm-8412
09/13/2022, 11:48 AMbland-orange-13353
09/14/2022, 8:59 AMshy-dog-84302
09/14/2022, 7:04 PMconfigure-sysctl
initcontainer pod.
I see running sysctl command requires root access but the container constraints does not allow that. Attached is my StatefulSet that results in this error.
How can I fix this?
Event : elasticsearch-master StatefulSet elasticsearch-master datahub create Pod elasticsearch-master-0 in StatefulSet elasticsearch-master failed error: admission webhook "<http://pod-security-webhook.kubernetes.io|pod-security-webhook.kubernetes.io>" denied the request: pods "elasticsearch-master-0" is forbidden: violates PodSecurity "restricted:latest": privileged (container "configure-sysctl" must not set securityContext.privileged=true), allowPrivilegeEscalation != false (container "configure-sysctl" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "configure-sysctl" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "configure-sysctl" must set securityContext.runAsNonRoot=true), runAsUser=0 (container "configure-sysctl" must not set runAsUser=0), seccompProfile (pod or container "configure-sysctl" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost") FailedCreate
bright-egg-51769
09/14/2022, 10:48 PMthousands-solstice-2498
09/15/2022, 3:11 AMtall-butcher-30509
09/15/2022, 6:03 AMWe will support a standardized way to do this in Kubernetes setup in the near future.https://datahubproject.io/docs/advanced/db-retention/ Is there any update on this?
cuddly-arm-8412
09/15/2022, 9:12 AMbright-egg-51769
09/15/2022, 3:41 PMproud-table-38689
09/15/2022, 9:02 PMbumpy-journalist-41369
09/16/2022, 7:39 AMcuddly-arm-8412
09/16/2022, 11:08 AMcolossal-needle-73093
09/17/2022, 4:20 AMcuddly-arm-8412
09/19/2022, 11:44 AMmicroscopic-mechanic-13766
09/19/2022, 11:45 AMcuddly-arm-8412
09/19/2022, 11:58 AMthousands-solstice-2498
09/19/2022, 1:10 PMorg.apache.kafka.common.errors.UnknownTopicOrPartitionException:
at org.apache.kafka.common.internals.KafkaFutureImpl.wrapAndThrow(KafkaFutureImpl.java:45)
at org.apache.kafka.common.internals.KafkaFutureImpl.access$000(KafkaFutureImpl.java:32)
at org.apache.kafka.common.internals.KafkaFutureImpl$SingleWaiter.await(KafkaFutureImpl.java:104)
at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:272)
at kafka.admin.ConfigCommand$.getResourceConfig(ConfigCommand.scala:552)
at kafka.admin.ConfigCommand$.alterConfig(ConfigCommand.scala:322)
at kafka.admin.ConfigCommand$.processCommand(ConfigCommand.scala:302)
at kafka.admin.ConfigCommand$.main(ConfigCommand.scala:97)
at kafka.admin.ConfigCommand.main(ConfigCommand.scala)
Caused by: org.apache.kafka.common.errors.UnknownTopicOrPartitionException:
microscopic-mechanic-13766
09/19/2022, 1:50 PMvictorious-xylophone-76105
09/19/2022, 4:44 PMquickstart
deployment started giving me issues: recently while trying to invoke datahub docker quickstart
, I am getting:
Fetching docker-compose file <https://raw.githubusercontent.com/datahub-project/datahub/master/docker/quickstart/docker-compose-without-neo4j.quickstart.yml> from GitHub
Pulling docker images...
unknown shorthand flag: 'f' in -f
...
I suspect that this line of code has to do something with it, because docker compose
is called instead if `docker-compose`:
https://github.com/datahub-project/datahub/blob/master/metadata-ingestion/src/datahub/cli/docker_cli.py#L636-L637
Please, help how to get around it?
Thanks!cuddly-arm-8412
09/20/2022, 1:56 AMrich-policeman-92383
09/20/2022, 6:45 AMfamous-florist-7218
09/20/2022, 7:53 AMoeja.AnnotationParser
spamming with message scanned from multiple locations
after upgrading and re-deploying helm chart. This thing happens on datahub-gms. Any thoughts?
=============
Chart version: 0.2.100.
DataHub version: 0.8.44colossal-fish-54995
09/20/2022, 8:32 AMdatahub docker quickstart
command. It looks like someone mentioned this bug earlier. But it still works fine when I ran it yesterday.microscopic-mechanic-13766
09/20/2022, 10:36 AMmicroscopic-mechanic-13766
09/20/2022, 11:37 AMbumpy-journalist-41369
09/20/2022, 2:46 PM~~~~ Execution Summary ~~~~
RUN_INGEST - {'errors': [],
'exec_id': '318cbd70-0a68-426a-aec1-c9c50c344b85',
'infos': ['2022-09-20 13:17:11.219637 [exec_id=318cbd70-0a68-426a-aec1-c9c50c344b85] INFO: Starting execution for task with name=RUN_INGEST',
'2022-09-20 13:17:11.220184 [exec_id=318cbd70-0a68-426a-aec1-c9c50c344b85] INFO: Caught exception EXECUTING '
'task_id=318cbd70-0a68-426a-aec1-c9c50c344b85, name=RUN_INGEST, stacktrace=Traceback (most recent call last):\n'
' File "/usr/local/lib/python3.9/site-packages/acryl/executor/execution/default_executor.py", line 121, in execute_task\n'
' self.event_loop.run_until_complete(task_future)\n'
' File "/usr/local/lib/python3.9/site-packages/nest_asyncio.py", line 89, in run_until_complete\n'
' return f.result()\n'
' File "/usr/local/lib/python3.9/asyncio/futures.py", line 201, in result\n'
' raise self._exception\n'
' File "/usr/local/lib/python3.9/asyncio/tasks.py", line 256, in __step\n'
' result = coro.send(None)\n'
' File "/usr/local/lib/python3.9/site-packages/acryl/executor/execution/sub_process_ingestion_task.py", line 71, in execute\n'
' validated_args = SubProcessIngestionTaskArgs.parse_obj(args)\n'
' File "pydantic/main.py", line 521, in pydantic.main.BaseModel.parse_obj\n'
' File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__\n'
'pydantic.error_wrappers.ValidationError: 1 validation error for SubProcessIngestionTaskArgs\n'
'debug_mode\n'
' extra fields not permitted (type=value_error.extra)\n']}
Execution finished with errors.
If however I log into the kubernetes pod - datahub-acryl-datahub-action, and execute the same recipe.yaml it executes sucessfully. Can someone help with my problem?thousands-solstice-2498
09/20/2022, 4:17 PMhttps://raw.githubusercontent.com/datahub-project/datahub/master/datahub-web-react/src/images/default_avatar.png▾
careful-engine-38533
09/21/2022, 10:07 AMshy-lion-56425
09/21/2022, 4:52 PM