Red Hat Bugzilla – Bug 1100817
luci to cope with virtual machine in both plain and service-like resource (incl. complex defs in cluster.conf)
Last modified: 2015-04-08 09:48:45 EDT
Description of problem: Luci does not present virtual machine resource agent in its "Resources" menu. Having <vm ../> manually added to <cluster><rm><resources> will result in luci showing error 500 when "Resources" are clicked. Version-Release number of selected component (if applicable): luci-0.26.0-48.el6.x86_64 How reproducible: always Steps to Reproduce: 1. have running cman cluster 2. add <vm name="le-name" /> as a child tu <cluster><rm><resources> in /etc/cluster/cluster.conf and reread config 3. in Luci web ui go to Cluster->Resources Actual results: Error 500 Expected results: Usual resources page. Other info: cluster.conf containing <vm/> tag under resources validates with ccs_config_validate.
There are two distinct use cases of "vm" as seen from rgmanager's perspective: 1/ full-blown, but standalone virtual machine that can be migrated (represented with top-level "vm" tag) 2/ weaker, standard-resource-like notion of "vm" as a building block of service/resource group (i.e., tag under "service") 2a/ "vm" defined in-line under "service" 2b/ "vm" defined under "resources" and referenced from "service" IIUIC, situation looks like this: a. 2b/ is not properly supported on input, choking on such a construction in remote cluster.conf (hence this bug + reproducer) b. 2b/ is not properly supported by means to extend cluster.conf in such way (hence originally reported [bug 1100280]) Ultimate solution to this bug should hence address both a. and b., getting closer to the versatility of editing cluster.conf manually.
To recap due to summary change, the sympthoms are: - error 500 in case of cluster.conf contruction luci is not ready for, hence unability to cope with input (a.) - unability to configure luci as per user's possible intentions (b.)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-1390.html