Skip to content
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

Explicitly disable systemd support in podified env #20277

Merged

Conversation

agrare
Copy link
Member

@agrare agrare commented Jun 15, 2020

If we are on a podified environment we should explicitly disable systemd support.

ManageIQ/manageiq-rpm_build#62 (comment)

If we are on a podified environment we should explicitly disable systemd
support.
@agrare agrare force-pushed the explicitly_disable_on_containerized branch from 7df6192 to 4e39e5c Compare June 15, 2020 20:27
@miq-bot
Copy link
Member

miq-bot commented Jun 15, 2020

Checked commit agrare@4e39e5c with ruby 2.5.7, rubocop 0.69.0, haml-lint 0.28.0, and yamllint
2 files checked, 0 offenses detected
Everything looks fine. 👍

@carbonin carbonin self-assigned this Jun 15, 2020
@carbonin carbonin merged commit 4701b11 into ManageIQ:master Jun 15, 2020
@carbonin
Copy link
Member

Will need to go back to jansa if ManageIQ/manageiq-rpm_build#62 does.

simaishi pushed a commit that referenced this pull request Jun 18, 2020
…ized

Explicitly disable systemd support in podified env

(cherry picked from commit 4701b11)
@simaishi
Copy link
Contributor

Jansa backport details:

$ git log -1
commit 9f2f4f740f226fb38ebe9e6914e10a872f7ca859
Author: Nick Carboni <ncarboni@redhat.com>
Date:   Mon Jun 15 16:59:58 2020 -0400

    Merge pull request #20277 from agrare/explicitly_disable_on_containerized

    Explicitly disable systemd support in podified env

    (cherry picked from commit 4701b115e424701719c12d2931c720819c80fda6)

@agrare agrare deleted the explicitly_disable_on_containerized branch October 19, 2020 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants