search

Dynatrace / dynatrace-oneagent-operator

Kubernetes/Openshift Operator for managing Dynatrace OneAgent deployments
Apache License 2.0
88 stars 48 forks source link

Error: Download failed on kubernetes #370

Closed niteenkole closed 3 years ago

niteenkole commented 3 years ago

Working on POC integrating Dynatrace with kubernetes.

kubectl logs -f oneagent-5mb48 -n dynatrace 16:23:53 Started agent deployment as a container, PID 74945. 16:23:53 Downloading agent to /tmp/Dynatrace-OneAgent-Linux.sh via https://axxxxxxxxup.ca/e/a61xxxx43-4f56-xxxx-48xxxxxdc/api/v1/deployment/installer/agent/unix/default/latest?Api-Token=***&arch=x86&flavor=default 16:24:03 Error: Download failed

using Wget is working fine on one of my alpine so token and all fine.

DTMad commented 3 years ago

Please reach out to support and create a ticket there so we can help you and do some analysis on that: https://www.dynatrace.com/support/contact-support/

niteenkole commented 3 years ago

https://support.dynatrace.com/supportportal/browse/SUP-64779

ewerton-silva00 commented 3 years ago

Hi, folks.

Same problem here. In my case, I'm trying to deployment on Kubernetes (AWS EKS).

00:00:31 Started agent deployment as a container, PID 6733.
00:00:31 Downloading agent to /tmp/Dynatrace-OneAgent-Linux.sh via https://**************.live.dynatrace.com/api/v1/deployment/installer/agent/unix/default/latest?Api-Token=***&arch=x86&flavor=default
00:01:02 Error: Download failed

It's OK with apiToken, because I can download the script file via wget.

DTMad commented 3 years ago

Please reach out to support and create a ticket there so we can help you and do some analysis on that: https://www.dynatrace.com/support/contact-support/

baichinger commented 3 years ago

@ewerton-silva00 Could be caused by DNS configuration. Give dnsPolicy: ClusterFirstWithHostNet (set in the custom resource) a try.

ewerton-silva00 commented 3 years ago

@ewerton-silva00 Could be caused by DNS configuration. Give dnsPolicy: ClusterFirstWithHostNet (set in the custom resource) a try.

Thanks, @baichinger for your reply.

This configuration, dnsPolicy: ClusterFirstWithHostNet is default in Custom Resource file (cr.yaml).

ewerton-silva00 commented 3 years ago

@ewerton-silva00 Could be caused by DNS configuration. Give dnsPolicy: ClusterFirstWithHostNet (set in the custom resource) a try.

Thanks, @baichinger for your reply.

This configuration, dnsPolicy: ClusterFirstWithHostNet is default in Custom Resource file (cr.yaml).

I changed the dnsPolicy to Default and it's works.