I peeked in your logs, and it seems to be a DNS resolution issue currently affecting the bos datacenter where your service’s primary region is designated.
Can you please try the workaround I suggested earlier? (It didn’t work for a few other users reporting this but I’d love to know if it works for you):
PRIMARY_REGION=atl fly deploy
This will force your ephemeral release_command machine to be created in a different region.
File “/usr/local/lib/python3.11/site-packages/psycopg/connection.py”, line 728, in connect
raise ex.with_traceback(None)
django.db.utils.OperationalError: connection is bad: No address associated with hostname
INFO Main child exited normally with code: 1
INFO Starting clean up.
WARN hallpass exited, pid: 315, status: signal: 15 (SIGTERM)
2023/10/23 21:00:48 listening on [fdaa:3:57e4:a7b:1ed:9e01:47e:2]:22 (DNS: [fdaa::3]:53)
[ 4.316027] reboot: Restarting system
machine restart policy set to ‘no’, not restarting