You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to use the agent-based installer for OKD 4.18, the PostgreSQL database service (assisted-service-db.service) fails to initialize properly, preventing the installation from proceeding. This should work out of the box but currently requires manual intervention.
Service Image: quay.io/okd/scos-content@sha256:7f597fb44334b5f5b6296321934df6476db527ba24d0b0e679f91f3ad771ac31
Current Behavior
The assisted-service-db.service fails to start with the following sequence:
Initial failure due to lock file directory issues
Service attempts to restart but fails repeatedly
PostgreSQL starts briefly but then immediately shuts down
Logs
Jan 13 10:31:33 master1.donker.vip podman[344792]: waiting for server to start.... done
Jan 13 10:31:33 master1.donker.vip podman[344792]: server started
Jan 13 10:31:34 master1.donker.vip postgres-container[344813]: waiting for server to shut down.... done
Jan 13 10:31:34 master1.donker.vip postgres-container[344813]: server stopped
Earlier attempts showed:
FATAL: could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock": No such file or directory
Expected Behavior
The PostgreSQL database service should:
Initialize correctly on first boot
Create necessary directories and files automatically
Start and remain running to support the installation process
Technical Analysis
The issues appear to be:
Lock file directory (/var/run/postgresql) is not properly created/mounted in the container
Service dependencies may not be properly ordered
Potential permission issues with the PostgreSQL data directory
Possible race condition in service startup sequence
This issue prevents new OKD cluster installations using the agent-based installer, requiring manual intervention and troubleshooting which should not be necessary for a standard installation process.
Suggested Fix
Consider implementing one or more of the following:
Ensure the container runtime properly creates and sets permissions for /var/run/postgresql
Add pre-start checks in the systemd service to verify directory existence and permissions
Include proper volume mounts in the default container configuration
Review service startup sequence to prevent race conditions
Additional Notes
Multiple attempts to resolve this through systemd service modifications and manual directory creation have shown that this is a fundamental issue with the service configuration rather than a local environment problem.
The text was updated successfully, but these errors were encountered:
Description
When attempting to use the agent-based installer for OKD 4.18, the PostgreSQL database service (
assisted-service-db.service
) fails to initialize properly, preventing the installation from proceeding. This should work out of the box but currently requires manual intervention.Environment
Current Behavior
The
assisted-service-db.service
fails to start with the following sequence:Logs
Earlier attempts showed:
Expected Behavior
The PostgreSQL database service should:
Technical Analysis
The issues appear to be:
/var/run/postgresql
) is not properly created/mounted in the containerWorking Configuration Attempted
Environment Variables Present
Impact
This issue prevents new OKD cluster installations using the agent-based installer, requiring manual intervention and troubleshooting which should not be necessary for a standard installation process.
Suggested Fix
Consider implementing one or more of the following:
/var/run/postgresql
Additional Notes
Multiple attempts to resolve this through systemd service modifications and manual directory creation have shown that this is a fundamental issue with the service configuration rather than a local environment problem.
The text was updated successfully, but these errors were encountered: