-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix CI on CentOS #114
Fix CI on CentOS #114
Conversation
Cannot reproduce locally with:
|
58b1bf5
to
5b54b5f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An alternative is to only do this in CI. https://github.com/voxpupuli/voxpupuli-acceptance/#per-host-configuration describes that you can create spec/setup_acceptance_node.pp
. Perhaps that's a better place for a workaround?
Also, it only appears to show up on CentOS 7 (at least now). Perhaps scope it to that while you're at it?
I don't think this is at all correct; I just looked at a CentOS 7 system using chrony, and /var/run is a symlink to /run and its contents get lost on boot, so managing files in there is not correct. Something else seems to be the problem. |
chrony seems to create the directory by itself when it's started; it starts as root, so unless the test container is restricting writes to /run somehow I don't see why it would fail. |
indeed, it's |
💯 I added commits to test this and stumbled on voxpupuli/voxpupuli-acceptance#27. When fixed, I can remove the last commit and merge all other commits in a single one. |
I've just released https://rubygems.org/gems/voxpupuli-acceptance/versions/1.0.1 |
We are experiencing CI failures on CentOS because the service cannot start because it cannot create it's PID file. Running the very same test locally works as expected, so the root cause of the different behavior on the CI is unfortunately unknown. Yet, ensuring the directory for the PID file exist seems to fix the CI issue. So manage explicitely this directory when running on CentOS in CI.
Pull Request (PR) description
We are experiencing CI failures on CentOS because the service cannot start because it cannot create it's PID file.
Running the very same test locally works as expected, so the root cause of the different behavior on the CI is unfortunately unknown. Yet, ensuring the directory for the PID file exist seems to fix the CI issue.
This Pull Request (PR) fixes the following issues
n/a