-
Notifications
You must be signed in to change notification settings - Fork 129
Properly manage libvirt services #1313
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
Conversation
|
Hi @cjeanner. Thanks for your PR. I'm waiting for a metal3-io member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
c96c9ca to
285b787
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.
Thanks for the patch!
Some nits that shellcheck will also probably point out.
/ok-to-test
With newer CS9 and RHEL-9, libvirtd has moved to a modular, socket activated layout. This new layout conflicts with the single, monolithic "libvirtd.service" that was restarted until now, creating issues with other projects that may wrap this metal3-dev-env. Fixes: metal3-io#1312
285b787 to
a6a7968
Compare
|
/test-centos-integration-release-1-5 |
lentzi90
left a comment
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.
Looks good!
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lentzi90 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
With newer CS9 and RHEL-9, libvirtd has moved to a modular, socket activated layout. This new layout conflicts with the single, monolithic "libvirtd.service" that was restarted until now, creating issues with other projects that may wrap this metal3-dev-env. There is a related PR against metal3-env-dev[1]. [1] metal3-io/metal3-dev-env#1313
With newer CS9 and RHEL-9, libvirtd has moved to a modular, socket activated layout. This new layout conflicts with the single, monolithic "libvirtd.service" that was restarted until now, creating issues with other projects that may wrap this metal3-dev-env. There is a related PR against metal3-env-dev[1]. [1] metal3-io/metal3-dev-env#1313
|
\o/ all green - that was almost too easy :). |
|
/lgtm Thanks for the contribution! |
With newer CS9 and RHEL-9, libvirtd has moved to a modular, socket activated layout. This new layout conflicts with the single, monolithic "libvirtd.service" that was restarted until now, creating issues with other projects that may wrap this metal3-dev-env. There is a related PR against metal3-env-dev[1]. [1] metal3-io/metal3-dev-env#1313
With newer CS9 and RHEL-9, libvirtd has moved to a modular, socket activated layout. This new layout conflicts with the single, monolithic "libvirtd.service" that was restarted until now, creating issues with other projects that may wrap this metal3-dev-env. There is a related PR against metal3-env-dev[1]. [1] metal3-io/metal3-dev-env#1313
|
this actually breaks execution of metal3-dev-env, see https://zuul.opendev.org/t/openstack/build/742fa43741ba4efca5d85c8c7c6a3d3b |
|
fix proposed #1314 |
With newer CS9 and RHEL-9, libvirtd has moved to a modular, socket activated layout.
This new layout conflicts with the single, monolithic "libvirtd.service" that was restarted until now, creating issues with other projects that may wrap this metal3-dev-env.
Fixes: #1312