Fix PostgreSQL startup failure in non-systemd environments #6595
+3
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PostgreSQL fails to start in non-systemd environments (e.g. Docker, GitLab Runner) because it cannot create the socket lock file at /run/postgresql/.s.PGSQL.5432.lock if the directory does not exist. This will also block openQA bootstrap process.
The specific error is:
pg_ctl: could not start server
Examine the log output.
Reproduce:
docker run -it --rm --name openqa-test opensuse/tumbleweed bash
zypper --non-interactive install openQA-bootstrap
/usr/share/openqa/script/openqa-bootstrap