-
Notifications
You must be signed in to change notification settings - Fork 25
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
Run bundle with systemd group #62
Conversation
Also changed to use "config set" to set with/without options as passing flags to bundle install is deprecated.
Oh wait... would this become a problem in podified build? |
@simaishi we have a gate on the Even if that didn't work for some reason we catch the load error here so if it wasn't in the bundle it'll fallback to the normal mode of starting workers |
I'm not sure. Does the rpm actually require systemd or any of it's libs be installed? If we don't require/use the gem in pods I would guess it would be okay. |
@@ -61,7 +61,9 @@ def populate_gem_home | |||
|
|||
shell_cmd("gem env") | |||
shell_cmd("gem install mime-types -v 2.6.1") | |||
shell_cmd("bundle _#{bundler_version}_ install --with qpid_proton --without test:development:metric_fu --jobs #{cpus} --retry 3") | |||
shell_cmd("bundle config set --local with qpid_proton systemd") | |||
shell_cmd("bundle config set --local without 'test:development:metric_fu'") |
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.
Note, metric_fu has been gone a long time and I think we can drop this now (followup PR)
So this broke pods:
We can probably come up with something to solve this in the source if it isn't easy to back this out just for pods. |
This could be my fault because I changed the way appliances are detected here: ManageIQ/manageiq@40620c9#diff-bd3bf5ebb076d419f16ea1eefa515cc9 Is the env var APPLIANCE set in containers? |
Yes, because we source |
I'll add an explicit |
@agrare I think I'd rather just fix is_container and is_appliance methods since they are wrong at the moment. EDIT: Actually it can't hurt to do both since we are sure we can't do systemd in containers. |
Yeah, was about to do that @agrare, just trying to figure out how to rebuild pods images using rpms with my manageiq branch to test. |
When we say "appliance" (for env var and is_appliance), that should only include VM appliances? If so, having APPLIANCE env var set in pods is wrong... |
@simaishi IMO, yes. We had discussed coming up with a different term for a "build" vs a literal "appliance": ManageIQ/manageiq#20107 (comment) |
However, for now, I'm 👍 with @agrare's idea to just short circuit supports_systemd? directly. |
Building this patch into container images now ... 16:03:42:~/Source/manageiq (no_systemd_in_containers)$ git diff upstream/master
diff --git a/lib/miq_environment.rb b/lib/miq_environment.rb
index 97813acb6a..c397a97ece 100644
--- a/lib/miq_environment.rb
+++ b/lib/miq_environment.rb
@@ -16,7 +16,7 @@ module MiqEnvironment
def self.supports_systemd?
return @supports_systemd unless @supports_systemd.nil?
- @supports_systemd = is_appliance? && supports_command?('systemctl')
+ @supports_systemd = !is_container && is_appliance? && supports_command?('systemctl')
end
def self.supports_nohup_and_backgrounding? |
Well that didn't work. HALP I'm running this in pods root dir: With this file:
Should that have pulled my manageiq ref here?
|
Tried running
And it pulled the right branch. Not sure what the difference is...
|
Ugh, well I'm using But it probably has something to do with this:
😫 |
Run bundle with systemd group (cherry picked from commit 9ebebe3)
Jansa backport details:
|
This was added to appliance build in ManageIQ/manageiq-appliance-build#396, but got missed when switched to rpm based. Sorry @agrare
Also changed to use "bundle config set" to set with/without options as passing those flags
to bundle install is deprecated.