Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I have put together a draft updated table, using the Conga display and the annotated cluster scheme, and I have sent this for review with a request for quick turnaround. We should be able to get this fixed for 6.1.
I can't see that url... it seems the server documentation-stage.bne.redhat.com doesn't exist (outside of Red Hat?).
Since I can't see it, I need to ask, is the option use_virsh per /usr/share/cluster/vm.sh covered in the GUI now?
Joshua: I'm not sure I understand the question. The vm.sh resource agent is treated as a service by luci -- so if you select resources -> add you won't see it on the list of resource types to select, but from the "Add service" menu, when you add a resource, you will see "Virtual machine" as a resource you can add. Those are the parameters that are documented in table B.21.
I'm asking if there is any documentation that you've added about use_virsh ?
Comment 11Steven J. Levine
2011-05-17 15:34:10 UTC
Joshua: No -- it is not something you select in the luci interface (which is what I though you meant by the GUI). The tables of resource parameters in the Cluster Administration document summarize the meanings of the resource parameters, using the luci interface as the guideline (the screensnap you provided), but they do not currently include the literal elements and attributes you set in the cluster.conf file (the cluster.conf equivalents of the luci/GUI selections). Those attributes are documented in the cluster schema at /usr/share/cluster/cluster.rng, and the annotated schema at /usr/share/doc/cman-X.Y.ZZ/cluster_conf.html, where use_virsh is documented as part of the vm tag.
Comment 14Steven J. Levine
2011-05-18 13:46:50 UTC
*** Bug 675246 has been marked as a duplicate of this bug. ***
Comment 15Steven J. Levine
2011-05-24 16:49:01 UTC
With the release of RHEL 6.1 I'm moving this to CLOSED.