Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
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.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
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.
Source: https://github.com/flipt-io/flipt/issues/993
Shows how to fix flipt 1.9.0 Postgres dial tcp lookup postgres device or resource busy. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes NLTK LookupError for the stopwords resource by downloading it or pointing NLTK at the right data path.
Fixes a helpdesk agent retrieving the FileVault key with the wrong device serial: verifying device identity before key lookup.