Bug 1179493
Summary: | rubygem-staypuft: pcs status shows "neutron-server_monitor_30000 on pcmk-maca25400702875 'OCF_PENDING' (196): call=228, status=complete, last-rc-change='Tue Jan 6 16:44:44 2015', queued=0ms, exec=0ms" under failed actions. | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Alexander Chuzhoy <sasha> | ||||||||||
Component: | rubygem-staypuft | Assignee: | Mike Burns <mburns> | ||||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Omri Hochman <ohochman> | ||||||||||
Severity: | urgent | Docs Contact: | |||||||||||
Priority: | urgent | ||||||||||||
Version: | unspecified | CC: | mburns, steve_hand, yeylon | ||||||||||
Target Milestone: | ga | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | x86_64 | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2015-01-07 14:32:54 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: | |||||||||||||
Attachments: |
|
Description
Alexander Chuzhoy
2015-01-06 22:19:37 UTC
Created attachment 976976 [details]
logs - controller1
Created attachment 976977 [details]
logs - controller2
Created attachment 976979 [details]
logs - controller3
Created attachment 976980 [details]
foreman logs
This is a duplicate of bug 1174389 It's not a blocker. The service failed *at some point* but is currently running. So pacemaker correctly handled the failure. Failed message: neutron-server_monitor_30000 on pcmk-maca25400702875 But current status: Clone Set: neutron-server-clone [neutron-server] Started: [ pcmk-maca25400702875 pcmk-maca25400702876 pcmk-maca25400702877 ] *** This bug has been marked as a duplicate of bug 1174389 *** |