-
Notifications
You must be signed in to change notification settings - Fork 271
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
Fixes #28067 - dynflow sidekiq services config #761
Conversation
d3f5ab6
to
db566e4
Compare
db566e4
to
060d6ea
Compare
63c29e1
to
ab7fcff
Compare
ab7fcff
to
a08ce06
Compare
a08ce06
to
3aab044
Compare
|
Tests are failing? |
As we have it default on, it needs the package, that is not in yet |
To summarize our discussion from https://community.theforeman.org/t/release-meeting-notes-2019-10-23/15883 - this will be merged only post branching and will be supported in 1.25. |
67c867f
to
7e087ba
Compare
f21a8fe
to
aef973d
Compare
I tested this out on a Katello nightly. Installation was successful but bats test are failing for most anything task related. My forklift box:
After running
|
I think you need this: theforeman/foreman-installer#400 The failure seems to be in the ping command though. It fails on status |
aef973d
to
ad55480
Compare
ad55480
to
861e5e5
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.
@ehelms could you have a look?
The Debian acceptance tests will fail until we actually build a new package with the packaging change (https://ci.theforeman.org/job/foreman-develop-package-release/336/) and promote it.
Will run through a few tests and report back |
I've kicked off https://ci.theforeman.org/job/foreman-nightly-deb-pipeline/263/ and will restart the Debian tests after that. |
I'm getting less bats failures now, woot! But I am still seeing an issue with one related to package installation failing:
This makes me think one of the previous tasks is failing in some way or incomplete but is not registering as such. Needs further investigation before we merge. As this will surely result in a broken nightly. My steps were the same as before. I spin up a machine with this puppet module patch, and latest nightly and ran bats tests against it. |
Perhaps it was an issue that the old dynflowd was still running? After theforeman/foreman-packaging#4442 is merged, that should be fixed in a |
It appeared dead when I checked:
|
Debian seems to fail on the dynflow-orchestrator service now 💔 |
It looks like the systemd unit is somehow wrong |
Looks like it's not included in Debian
I was looking at systemd conditionals to check if Speaking of guarantees: using type=notify per https://github.com/mperham/sidekiq/blob/3510de7df3c2eaacec9061184666aa853a0abb13/examples/systemd/sidekiq.service#L28-L35 looks like a good idea but does require some code in core. |
theforeman/foreman-packaging#4620 intends to fix the Debian packaging side. |
Looks like I am seeing two failures, but latest nightly has the same bats failures. So I am good from that perspective. We will need this to land close to the foreman-maintain change + a build of foreman-maintain or else nightly will fail with the status check. |
I updated the f-m PR to have the correct redis service names |
https://ci.theforeman.org/job/foreman-develop-package-release/343/ should include the Debian fix. Once complete I'll kick off https://ci.theforeman.org/job/foreman-nightly-deb-pipeline/ as well to get green tests.
This is theforeman/foreman_maintain#292 |
https://ci.theforeman.org/job/foreman-nightly-deb-pipeline/268/ should make that available. |
I think the same statsd failure is seen in master now, haven't looked into it yet. |
Exactly 💚 |
merged, díky @ezr-ondrej! |
Install necessary sidekiq configs and dependencies.