Bug 1312018
Summary: | [systemd] Make changes to start opal-prd daemon automatically (fedora-release) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Vasant Hegde <hegdevasant> |
Component: | fedora-release | Assignee: | Stephen Gallagher <sgallagh> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 24 | CC: | bugproxy, dennis, dhorak, errata-xmlrpc, hannsj_uhl, hegdevasant, jdisnard, jmcdonal, jsynacek, kevin, pbrobinson, sgallagh, zbyszek |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | ppc64le | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-06-16 17:41:28 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1284527 | ||
Bug Blocks: | 1071880, 1051573, 1312446 |
Description
Vasant Hegde
2016-02-25 14:26:45 UTC
------- Comment From hannsj_uhl.com 2016-02-25 10:46 EDT------- . This bug has been incorrectly added to the "Edit Fedora Components" group, which should not be used for bugs. As it is not clear whether this bug is intended to be public or private, I'm going to add the bug to the Fedora Contrib Private group so that the other group can be removed from this bug and disabled. If it's ok for the bug to be public, the Fedora Contrib Private group can be cleared. (In reply to Jason McDonald from comment #2) > This bug has been incorrectly added to the "Edit Fedora Components" group, > which should not be used for bugs. Sorry. That was my mistake. > As it is not clear whether this bug is > intended to be public or private, I'm going to add the bug to the Fedora > Contrib Private group so that the other group can be removed from this bug > and disabled. I'm fine to keep it under Private group. -Vasant If you want your service to be enabled by default, see https://fedoraproject.org/wiki/Packaging:DefaultServices, section "Approved Exceptions". Feel free to reopen this bugzilla when you have the necessary exception approved. I've raised https://fedorahosted.org/fesco/ticket/1558 to get exception approval from FESCO. -Vasant As disu(In reply to Vasant Hegde from comment #5) > I've raised https://fedorahosted.org/fesco/ticket/1558 to get exception > approval from FESCO. As suggested by sgallagh in above ticket I'm REOPENING this bug and changing component to fedora-release. -Vasant (In reply to Vasant Hegde from comment #6) > As disu(In reply to Vasant Hegde from comment #5) > > I've raised https://fedorahosted.org/fesco/ticket/1558 to get exception > > approval from FESCO. > > As suggested by sgallagh in above ticket I'm REOPENING this bug and changing > component to fedora-release. > > -Vasant Thanks. Can you please specify the exact systemd units that you want enabled by default? e.g. foo.service, bar.socket or baz.timer (In reply to Stephen Gallagher from comment #7) > (In reply to Vasant Hegde from comment #6) > > As disu(In reply to Vasant Hegde from comment #5) > > > I've raised https://fedorahosted.org/fesco/ticket/1558 to get exception > > > approval from FESCO. > > > > As suggested by sgallagh in above ticket I'm REOPENING this bug and changing > > component to fedora-release. > > > > -Vasant Stephen, > > Thanks. Can you please specify the exact systemd units that you want enabled > by default? e.g. foo.service, bar.socket or baz.timer Exact service name is : opal-prd.service -Vasant What about the socket unit? (In reply to Zbigniew Jędrzejewski-Szmek from comment #9) > What about the socket unit? opal-prd.socket -Vasant Sure, I know what the socket is called. My question (implicit, but I thought it would be obvious) is whether you want it enabled by default, and if yes why, and if no, why not. And if yes, why do you want the service started by default instead of being socket activated. (In reply to Zbigniew Jędrzejewski-Szmek from comment #11) > Sure, I know what the socket is called. My question (implicit, but I thought > it would be obvious) is whether you want it enabled by default, and if yes > why, and if no, why not. Yes. We want to enable this by default. opal-prd daemon handles hardware-specific recovery processes, and should be run as a background system process after boot. It interacts with OPAL firmware to capture hardware error causes, log events to the management processor, and handles recoverable errors where suitable. Without this daemon we will not be able to handle hardware errors (like processor checkstop). Hence we would like to enable this daemon by default on ppc64le architecture. > > And if yes, why do you want the service started by default instead of being > socket activated. No particular reason. Either way works for me as long as daemon starts by default. -Vasant OK, after looking at the two unit files, .service Requires the .socket unit, so it is enough to only put the .service in presets. (In reply to Zbigniew Jędrzejewski-Szmek from comment #13) > OK, after looking at the two unit files, .service Requires the .socket unit, > so it is enough to only put the .service in presets. Thanks! -Vasant https://pagure.io/fedora-release/pull-request/38 (F24) https://pagure.io/fedora-release/pull-request/37 (Rawhide/F25) Looks like its fixed in rawhide branch.. But not yet included in Fedora24 branch. changelog from rawhide branch. fedora-release-25-0.7.noarch.rpm * Fri Mar 18 2016 Dennis Gilmor <dennis> - 25-0.7 - drop Requires(post): sed - Fork to execute systemctl calls * Tue Mar 15 2016 Dennis Gilmore <dennis> - 25-0.6 - Properly handle systemd presets in Lua scripts - enable opal-prd.service - Remove call to grub2-mkconfig -Vasant It was not pulled into f24 yet as we were in alpha freeze and it did not fix anything that was proposed as a blocker or freeze exception. As such it was inappropriate to pull in. This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions This will be in fedora-release-24-0.18 (or the next one) Verified on fedora-release-24-1.noarch.rpm and its fixed. We can close this bug. -Vasant |