23 Aug 2021 01:57 PM - last edited on 03 Oct 2022 03:14 PM by MaciejNeumann
Hi all,
we have managed to correctly monitor the kubernetes cluster from a previous environment and all works fine!
We repeat the steps that have worked in the previous environment (https://www.dynatrace.com/support/help/setup-and-configuration/setup-on-container-platforms/openshif...) and when we apply the cr.yaml the OneAgent is not verified after the download:
oc logs dynakube-alc1-pro-classic-f244x -n dynatrace
10:11:13 Started agent deployment as a container, PID 392707.
10:11:14 Downloading agent to /tmp/Dynatrace-OneAgent-Linux.sh via https://xxxxx.dynatrace-managed.com/e/cfccaeba-f2fc-45b7-932f-7e61fcd14c70/api/v1/deployment/installer/agent/unix/default/latest?Api-Token=***&arch=x86&flavor=default
10:11:14 Download complete
10:11:14 Downloaded version:
10:11:14 Verifying agent installer signature
10:11:14 Error: Agent installer signature verification failed, openssl cms returned: 2
10:11:14 Error: Error reading S/MIME message
139644288264000:error:0D0D40D2:asn1 encoding routines:SMIME_read_ASN1:no multipart body failure:crypto/asn1/asn_mime.c:416:
as I said, the configuration was same one that is working in previous environment with skipCertCheck: true
So, ¿any idea in what's wrong in production environment?
Regards, Josep Maria
27 Aug 2021 09:45 PM
make sure your AG has it set to ignore certs in the config file. I think that's what hung us up before.