Flipt 1.9.0 Postgres dial tcp lookup postgres device or resource busy

TL;DR

What fixed it This was a Flipt regression fixed in v1.9.1 and v1.10.1, upgrade to either of those patch releases and the Postgres connection works again. The reporter confirmed v1.9.1 fixed it in both local Rancher Desktop and GCP clusters.

Steps

1. What was going on

Upgrading Flipt from 1.8.3 to 1.9.0 or 1.10.0 breaks Postgres connectivity in Kubernetes with: getting db driver for: postgres: dial tcp: lookup postgres.database.svc.cluster.local: device or resource busy. Versions 1.8.2 and 1.8.3 worked fine, and the error appears even against a fresh database, so it is a regression in the 1.9.x connection handling.

2. What fixed it

This was a Flipt regression fixed in v1.9.1 and v1.10.1, upgrade to either of those patch releases and the Postgres connection works again. The reporter confirmed v1.9.1 fixed it in both local Rancher Desktop and GCP clusters. If you must stay on 1.9.0/1.10.0 temporarily, rolling back to 1.8.3 avoids the error.

When to use

You are seeing this: What was going on Upgrading Flipt from 1.8.3 to 1.9.0 or 1.10.0 breaks Postgres connectivity in Kubernetes with: getting db driver for: postgres: dial tcp: lookup postgres.database.svc.cluster.local: device or resource busy. Use this skill when you run into "Flipt 1.9.0 Postgres dial tcp lookup postgres device or resource busy".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 1.8.3, 1.9.0, 1.10.0, Versions 1.8.2, v1.9.1, v1.10.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In the thread, the question was: Upgrading Flipt from 1.8.3 to 1.9.0 or 1.10.0 breaks Postgres connectivity in Kubernetes with: getting db driver for: postgres: dial tcp: lookup postgres.database.svc.cluster.local: device or resource busy. Versions 1.8.2 and 1.8.3 worked fine, and the error appears even against a fresh database, so it is a regression in the 1.9.x connection handling. The verified resolution: This was a Flipt regression fixed in v1.9.1 and v1.10.1, upgrade to either of those patch releases and the Postgres connection works again. The reporter confirmed v1.9.1 fixed it in both local Rancher Desktop and GCP clusters. If you must stay on 1.9.0/1.10.0 temporarily, rolling back to 1.8.3 avoids the error. Thread: https://vectle.com/threads/thriwJnrdM4ja8v3gctAuN7g