oneagent version 1.311.72.20250423-112851 causing production troubles

[jaoued_zahraoui]

our production application has issues with some functionalities.

after investigation, figured out it was related to oneagent.

relevant logs:
[29.04.2025 08:06.59.288] [ERROR] /opt/dynatrace/oneagent/agent/bin/1.311.72.20250423-112851/any/nodejs/nodejsagent.js:12700
[29.04.2025 08:06.59.292] [ERROR] e.runFunctionInContext(J, k.origFn, this, ...I).then(x, z);
[29.04.2025 08:06.59.292] [ERROR] ^
[29.04.2025 08:06.59.294] [ERROR] TypeError: Cannot read properties of undefined (reading 'then')
[29.04.2025 08:06.59.294] [ERROR] at <anonymous>
[29.04.2025 08:06.59.294] [ERROR] at AsyncLocalStorage.run (node:async_hooks:330:14)
[29.04.2025 08:06.59.294] [ERROR] at processTicksAndRejections (node:internal/process/task_queues:96:5)

Had to downgrade to previous stable version, to restore the service.

want to be sure this bug is known and handled and this version is not being automatically installed when the new release comes out.

thank you.

[Theodore_x86]

Hello. Can you please describe the symptom of the issue? What was the impact? Was the application able to start up properly?

BR

[jaoued_zahraoui]

yes the application start, but some feature that allowing to uploads files was creating this issue.

the error indicates that the Dynatrace Node.js agent is trying to call .then() on something that's undefined.

[Theodore_x86]

Understood.

Suppose you have already opened a support ticket. If this is a bug, then Support must be engaged.

BR

[jaoued_zahraoui]

ticket is this one: https://one.dynatrace.com/hc/en-us/requests/476502 

can you please  indicate if the RFE is accepted, planned, already implemented, not planned, etc.

[HannahM · Accepted solution]

This looks like an issue fixed in OneAgent 313, OA-46324. It's due to be released soon, we're just waiting for Production Go. 

EDIT: OneAgent 313 is being released to SaaS tenants on 12th May.

[jaoued_zahraoui]

thank you very much.

[sathi]

we are also seeing the same issue .. is there a workaround until the fix is released

[HannahM]

The only workaround currently is to roll back the OneAgent Image to 1.309.73.20250423-112845
 
1. Uninstall the Operator, see steps here: https://docs.dynatrace.com/docs/shortlink/guides-k8s-update-uninstall-operator
 
2. Retrieve the OneAgent Version or set the OneAgent Version in your tenant to image: "dynatrace/dynatrace-oneagent:1.309.73.20250423-112845"

There are a few ways to find or set the available OneAgent versions:

• Method 1: Dynatrace UI (Recommended )
  1. Log in to your Dynatrace environment (SaaS or Managed).
  2. Navigate to Settings> Updates > OneAgent.
     You can define the current version latest OneAgent Versions to be used, which is 1.309.
     
     

• Method 2: Dynatrace API (Good for Automation)
  You can use the Dynatrace API to query available OneAgent versions. The specific endpoint may vary slightly depending on your Dynatrace version and API generation used, but a common one (using API v1) is:

  • Endpoint:/api/v1/deployment/installer/agent/versions/{os-type}/{installer-type}
  • Example (Linux PaaS installer):GET {your-environment-id}.live.dynatrace.com/api/v1/deployment/installer/agent/versions/unix/paas (Replace {your-environment-id} with your actual environment ID).
  • You'll need an API token with the "Read settings" (settings.read) permission.
  • The response will list available versions, often including the full version string you need.
    Documentation: https://docs.dynatrace.com/docs/discover-dynatrace/references/dynatrace-api/environment-api/deployme...

  Alternatively, check the newer Settings API (/api/v2/settings/objects) for schemas related to OneAgent updates if the above endpoint is deprecated in your version.

3. Redeploy the Operator to pull in the latest OneAgent versions defined in Global Settings.

Go to Updates > OneAgent, you can hardcode the specific version see below:

3.1 Hardcode the Specific OneAgent Version in dynakube.yaml
The dynakube.yaml file defines the Custom Resource for the Dynatrace Operator. You specify the OneAgent version within the spec.oneAgent section, under the specific deployment mode you are using (e.g., classicFullStack, cloudNativeFullStack).
Here are examples for common deployment modes:

• Example for classicFullStack:

  apiVersion: dynatrace.com/v1beta1
  kind: DynaKube
  metadata:
    name: dynakube # Your DynaKube instance name
    namespace: dynatrace # Your Dynatrace namespace
  spec:
    apiUrl: https://your-environment-id.live.dynatrace.com/api # Replace with your API URL
    oneAgent:
      classicFullStack:
        # >>> HARDCODE VERSION HERE <<<
        version: "1.278.123.20240420-100000"
        # Tolerations, node selectors, arguments etc. might also be here
        # ...
    # Other configurations like ActiveGate, routing, etc.
    # ...

• Example for cloudNativeFullStack:

  apiVersion: dynatrace.com/v1beta1
  kind: DynaKube
  metadata:
    name: dynakube # Your DynaKube instance name
    namespace: dynatrace # Your Dynatrace namespace
  spec:
    apiUrl: https://your-environment-id.live.dynatrace.com/api # Replace with your API URL
    oneAgent:
      cloudNativeFullStack:
        # >>> HARDCODE VERSION HERE <<<
        version: "1.278.123.20240420-100000"
        # Tolerations, node selectors, arguments etc. might also be here
        # ...
    # Other configurations like ActiveGate, routing, etc.
    # ...

  
  If you have any questions, please start a chat or create a Support ticket and mention ticket OA-46324

[HannahM]

OneAgent 313 has now been released. 🎉

[sathi]

Can you share the release notes for oneAgent 313 . Thanks

[HannahM]

I'm sorry, but they're not quite ready yet. Also, it looks like OneAgent 313 has only been released to internal tenants, but I'm hoping it will be ready soon.