Bug 1300729
Summary: | Pacemaker failed to start a systemd resource: 'not running' | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Matti Linnanvuori <mattilinnanvuori> |
Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
Status: | CLOSED NOTABUG | QA Contact: | cluster-qe <cluster-qe> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.2 | CC: | abeekhof, cluster-maint, jruemker |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-01-21 15:47:32 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: |
Description
Matti Linnanvuori
2016-01-21 14:56:38 UTC
(In reply to Matti Linnanvuori from comment #0) > Description of problem: > > Pacemaker failed to start a systemd resource: 'not running' > Hello, The problem you described would require further investigation in order to identify the true cause and any available means to resolve it, which is best done in a support case rather than here in bugzilla, which is intended more for reporting bugs and undesired behaviors in the product itself. I would like to request that you please engage Red Hat Global Support Services through one of the methods described at: https://access.redhat.com/start/how-to-engage-red-hat-support From there, we'll collect some additional information from you and take a closer look at the specifics of this incident to help you resolve the underlying problem. In an attempt to give you some guidance in the meantime: the problem you described doesn't look to be anything unexpected from pacemaker itself. It attempted to start the pmc-routing systemd service and encountered a failure; by default, the cluster property start-failure-is-fatal is set, which causes a start failure to automatically be treated as a reason to ban the local node from further attempts to start that resource and to try on another node. Since both of the other nodes are in standby, there is nowhere else to start, so it gives up. The real problem here is that a systemd start of pmc-routing failed. We'll need to look more closely at why that is and address it. This is what we can help you with in a support case. Since there doesn't appear to be anything in this data suggesting that there is a problem in need of a fix in pacemaker, I'm going to close this out. If we discover in the course of our investigation through a support case that there is some unexpected behavior in one of our products, then Red Hat Global Support Services will coordinate with the developers of that component to look into it and pursue any necessary fixes. Regards, John Ruemker, RHCA Principal Software Maintenance Engineer Red Hat Global Support Services |