Upgrade to The Things Network v3.22.2 (completed)

Completed: Upgrade to The Things Network v3.22.2

This is a cross-post of an incident on our The Things Network status page.
It will be updated automatically.

Scheduled: Mon, 07 Nov 2022 12:00:00 +0100 until 14:30:00 +0100

Resolved: Mon, 07 Nov 2022 14:30:38 +0100

Affected Components

  • Europe 1 (eu1.cloud.thethings.network): Operational
  • North America 1 (nam1.cloud.thethings.network): Operational
  • Australia 1 (au1.cloud.thethings.network): Operational

Scheduled

Posted: Fri, 04 Nov 2022 17:14:26 +0100

During this maintenance window we will upgrade The Things Network v3.22.2

We do not expect noticeable downtime during this deployment.

Here is the changelog since the current version v3.22.1:

Changed

  • Class B and C downlinks will no longer be automatically retried indefinitely if none of the gateways are available at the scheduling moment, and the downlink paths come from the last uplink.
    • This was already the behavior for downlinks which had their downlink path provided explicitly using the class_b_c.gateways field.
    • The downlinks will be evicted from the downlink queue and a downlink failure event will be generated. The failure event can be observed by the application using the downlink_failed message, which is available in all integrations.
  • Event history and payload storage TTL has now 1% jitter.

Fixed

  • User creation via OpenID Connect now correctly takes into account name clashes with existing organizations.
  • Do not require AppKey when skipping Join Server registration in end device onboarding in the Console.
  • Fix auto generation of device ID when using DevEUI generator in the Console.
  • Fix several device onboarding issues with ABP in the Console.
    • Do not ask for a JoinEUI.
    • Reinitialize form properly when switching between ABP and OTAA.
  • Issue with pasting values into byte input at the wrong position in the Console

In Progress

Posted: Mon, 07 Nov 2022 12:00:41 +0100

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Completed

Posted: Mon, 07 Nov 2022 14:30:38 +0100

The scheduled maintenance has been completed.

The incident on our status page was just updated with new information. The first post in this topic has been updated accordingly.

The incident on our status page was just updated with new information. The first post in this topic has been updated accordingly.