PowerNV: Restart opal-prd daemon on any kind of failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
High
|
Unassigned | ||
skiboot (Ubuntu) |
Fix Released
|
High
|
Ubuntu on IBM Power Systems Bug Triage | ||
Xenial |
Fix Released
|
Undecided
|
Steve Langasek | ||
Yakkety |
Fix Released
|
Undecided
|
Steve Langasek | ||
Zesty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[SRU Justification]
As a hardware diagnostic service, it's important that opal-prd be kept running even in the face of hardware unreliability. The most effective way to do this is with a systemd unit policy of Restart=always, to ensure the service is not allowed to accidentally die.
[Test case]
1. Install the opal-prd package on a system that has /dev/mtd0.
2. Verify that the service is running with 'systemctl status opal-prd'.
3. Get the pid of the opal-prd process from systemctl and kill it with 'sudo kill -9 $pid'.
4. Verify via 'systemctl status opal-prd' that the service is no longer running.
5. Install opal-prd from -proposed.
6. Verify via 'systemctl status opal-prd' that the service is running again.
7. Kill the new process with 'sudo kill -9 $pid'.
8. Verify via 'systemctl status opal-prd' that the service has been restarted.
9. Install the opal-prd package from -proposed on a system that does not have /dev/mtd0.
10. Verify that 'systemctl status opal-prd' shows the service is inactive, and has not been allowed to restart indefinitely after failure, driving up the system load.
[Regression potential]
Since the package may be installed on systems where opal-prd is useless and will not run, it's important to verify for each release that Restart=always doesn't cause systemd to go into a busy loop trying to restart the service under these conditions. The uploaded change should guard against this by checking for the correct path before starting the job, and the test case should further confirm this.
== Comment: #0 - VASANT HEGDE <email address hidden> - 2017-03-08 03:12:33 ==
---Problem Description---
opal-prd package contains prd daemon (Processor Runtime Diagnostics).
One of the requirements from a field service perspective is to be able
to restart opal-prd when it fails for whatever reason.
Direct systemd to restart the opal-prd service on any kind of failure.
Ubuntu contains opal-prd package. This bug is to restart daemon after failure
Contact Information = <email address hidden>
Machine Type = All Open Power Systems
Userspace tool common name: opal-prd
Userspace rpm: opal-prd
The userspace tool has the following bit modes: 64bit
== Comment: #3 - Ananth Narayan M G <email address hidden> - 2017-03-08 03:37:46 ==
Posted patch upstream for this -- https:/
summary: |
- Restart opal-prd daemon on any kind of failure + PowerNV: Restart opal-prd daemon on any kind of failure |
Changed in skiboot (Ubuntu): | |
status: | Fix Released → In Progress |
tags: | added: ubuntu-16.04 |
Changed in ubuntu-power-systems: | |
status: | New → In Progress |
Changed in skiboot (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in skiboot (Ubuntu Xenial): | |
assignee: | nobody → Steve Langasek (vorlon) |
milestone: | none → ubuntu-16.04.3 |
Changed in skiboot (Ubuntu Zesty): | |
status: | New → Fix Released |
description: | updated |
Changed in skiboot (Ubuntu Yakkety): | |
status: | New → In Progress |
Changed in skiboot (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in skiboot (Ubuntu Yakkety): | |
assignee: | nobody → Steve Langasek (vorlon) |
milestone: | none → yakkety-updates |
Changed in ubuntu-power-systems: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-power-systems: | |
status: | Fix Committed → Fix Released |
Default Comment by Bridge