Bug 613868
Summary: | Remove fence_virsh from luci UI since this fence is not supported with RHEL HA/Cluster | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Ryan Mitchell <rmitchel> | ||||||
Component: | luci | Assignee: | Chris Feist <cfeist> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Cluster QE <mspqa-list> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 6.0 | CC: | bbrock, cfeist, cluster-maint, everett.bennett, rmccabe, tdunnon | ||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | luci-0.22.2-9.el6 | Doc Type: | Bug Fix | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2010-11-10 22:11:46 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: | |||||||||
Attachments: |
|
Created attachment 431332 [details]
screenshot of errior after creating virsh_fence_device.
fence_virsh is not supported with either RHEL5 or RHEL6 cluster. The fence agent is provided as a development tool only for individuals who want a fencing like device for virtual machines, but only for standalone (i.e. non-cluster usage). Please see the support matrix at: https://access.redhat.com/kb/docs/DOC-30003 "fence_virsh is included in RHEL5 as a test fence agent. It is shipped and can be used by developers but it is not formally supported in conjunction with Red Hat Enterprise Linux Clustering" Therefore this bug will be changed to remove fence_virsh from the Luci UI since it should not have been there in the first place. The acceptable/supported virtualization fencing agents that can be used with RHEL HA/Cluster Suite are fence_xvm and fence_virt. Fixed in a958cd4bc22cbac3be9bfb661fa335d265232b6c. Any recommendations on what fence device to use in RHEL 5.5 KVM situtation. I have a RHEL 6.0 Beta 2 Host on IBM Blade for test purposes. I currently have 4 RHEL 5.5 KVM Guests running in cluster mode. (In reply to comment #6) > Any recommendations on what fence device to use in RHEL 5.5 KVM situtation. I > have a RHEL 6.0 Beta 2 Host on IBM Blade for test purposes. I currently have 4 > RHEL 5.5 KVM Guests running in cluster mode. If running RHEL5 clustered guests on top of a RHEL6 host, the correct fence agent to use is fence_xvm on RHEL5. fence_xvm will work properly with fence_virtd running on the host OS. Lon designed fence_virt/fence_virtd to be backwards compatible with fence_xvm/fence_xvmd for exactly this use case. Note though: the configuration you are running in is a TechPreview, so it is not yet fully tested or fully supported at this time. Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |
Created attachment 431331 [details] screenshot when creating virsh_fence_device screen (no login field) Description of problem: When attempting to create a shared "virsh fence agent" fencing device, the fields presented to configure this device do not include a "login" field. Once filling out all the available fields and clicking submit, I get the error: No value for required attribute "login" was given for fence "fencedevicename" Version-Release number of selected component (if applicable): $ rpm -q luci luci-0.22.2-3.el6.x86_64 $ rpm -q cman cman-3.0.12-9.el6.x86_64 $ uname -r 2.6.32-42.el6.x86_64 How reproducible: Very reproducible Steps to Reproduce: 1. Install luci on RHEL6 2. Create a cluster with at least 2 nodes (preferably virtual machines but its not important) 3. Click through to manage your cluster. On cluster management page, choose "Fence Devices" tab. 4. Choose "Add" option. Select "virsh fence agent" from the list. 5. Fill out the fields and click "Submit". Actual results: - No fence device is created. - Error messages: No value for required attribute "login" was given for fence "fencedevicename" Expected results: - Fence device is created. - No error message is displayed Additional info: - I think we need to add a "login" field to the interface so you can specify one.