Completed: Upgrade to The Things Network v3.16.2
This is a cross-post of an incident on our The Things Network status page.
It will be updated automatically.
Scheduled: Mon, 20 Dec 2021 09:30:00 +0100 until 11:30:00 +0100
Resolved: Mon, 20 Dec 2021 11:30:37 +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, 17 Dec 2021 14:42:18 +0100
During this maintenance window we will upgrade The Things Network v3.16.2
We do not expect noticeable downtime during this deployment.
Here is the changelog since the current version v3.16.1:
Added
- User defined antenna gain for LBS gateways.
- Support for the Authorization Code flow for the OIDC authentication providers.
- Previously only the Hybrid flow was supported.
- Better support for user claims provided by OIDC authentication providers.
- Non-TLS interop listener. Default port is 1886.
- Webhooks now have a health status associated with them. Webhooks that fail successively are now disabled for a period of time.
- Failure in this context means that the HTTP endpoint returned a non-2xx status code.
- A successful HTTP request will reset the failure counter.
- The number of allowed successive failures and cooldown period can be configured using the
--as.webhooks.unhealthy-attempts-threshold
and--as.webhooks.unhealthy-retry-interval
configuration options.
- Webhook enabled path validation in the Console.
Changed
- Increased the maximum gRPC message size to 16MB.
- Gateways which have been deleted are now automatically disconnected by the Gateway Server.
Fixed
- Access to application payload formatters for users with
RIGHT_APPLICATION_SETTINGS_BASIC
right. - End device mac settings handling in the Console.
- Uplink and downlink counters display on end device activity in the Console.
- External users unique constraint taking into account the wrong columns.
- This requires a database schema migration (
ttn-lw-stack is-db migrate
).
- This requires a database schema migration (
- Invitations unique constraint taking into account the wrong columns.
- This requires a database schema migration (
ttn-lw-stack is-db migrate
).
- This requires a database schema migration (
- Join settings handling in JS-only deployments in the Console.
- Configuring Packet Broker listed option when Packet Broker Agent is configured with a Packet Broker tenant API key.
- Contact info validation through the Account app.
In Progress
Posted: Mon, 20 Dec 2021 09:30:21 +0100
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Completed
Posted: Mon, 20 Dec 2021 11:30:37 +0100
The scheduled maintenance has been completed.