Bug 169774
Summary: | fence_wti status check fails | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Lucas Tepper <lucas> |
Component: | fence | Assignee: | Ryan O'Hara <rohara> |
Status: | CLOSED WORKSFORME | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | cluster-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-01-05 21:02:50 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
Lucas Tepper
2005-10-03 14:37:00 UTC
looking for hardware to test on. Ryan - can you try and reproduce this, please? I have never been able to, with the wti switch here in Westford...I don't know if you guys have this exact model of WTI product in msp... I'm attempting to reproduce this with a WTI NPS-115 that I have setup in the lab here. It appears to be identical to the NPS-230 except that it is 115 VAC, wheras the NPS-230 is 230 VAC. I have not been able to reproduce this on an NPS-115, which should be identical to the NPS-230 except for VAC (mentioned above). Two things to mention: 1. The WTI NPS devices have a configurable "boot delay" which is used to set the time between the off/on of a reboot operation. It seems possible that boot delay could be set small enough that by the time we check the status (expecting "off") we see that it is "on". However, I tried this with the lowest possible setting (1 sec) and it did not occur. Even if this were the case, I would have expected the log messages to suggest that is fould the state to be "ON". In the log messages above, it appears the state is unknown. 2. There may be a very slight change in the console format due to different firmware revisions. It appears that the switch I was testing with has version 2.00. I am closing this since I am unable to reproduce this bug. If this continues to be a problem, please reopen this bug with addition information, including the firmware version, etc. |