Bug 241216
Summary: | fence_apc 1.32.45 doesn't work | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Jonny <jschulz> |
Component: | fence | Assignee: | Jim Parsons <jparsons> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | cluster-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-02-27 13:57:32 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jonny
2007-05-24 13:33:31 UTC
double post... delete it please double post ... delete it please So, this agent has been worked on, as there were a couple of tickets against it, but I am uncertain if fix will cover your issue - is it possible to test the new agent on your cluster? Does this work for you in the current release? Jonny - are there still issues with this? What is the exact model of the apc device? I'm visiting apc soon and will check scripts against your exact model...Should this ticket be closed? Closing due to no response from ticket creator. In addition, a trip to the APC plant in February of this year revealed that certain versions of 3.x APC firmware was buggy, and APC users should be running the very latest. Our current APC script was tested with the latest firmware and worked without fault. |