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.
Bug 1101266 - luci to cope with virtual machine in both plain and service-like resource (incl. complex defs in cluster.conf)
Summary: luci to cope with virtual machine in both plain and service-like resource (in...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Cluster_Administration
Version: 6.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On: 1100817
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-26 13:37 UTC by Jan Pokorný [poki]
Modified: 2014-07-24 20:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1100817
Environment:
Last Closed: 2014-07-24 20:13:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jan Pokorný [poki] 2014-05-26 13:37:16 UTC 
Most important part below wrt. documentation highlighted by quotation:

+++ This bug was initially created as a clone of Bug #1100817 +++

--- Additional comment from RHEL Product and Program Management on 2014-05-23 16:13:20 CEST ---

Since this bug report was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Jan Pokorný on 2014-05-26 15:15:34 CEST ---

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.

--- Additional comment from Jan Pokorný on 2014-05-26 15:19:47 CEST ---

Shortly discussed with Fabio, there should be some kind of distinction
between 1/ and 2/, to the user is in no way mislead to some false
assumptions of what is being configured.


> Fabio mentioned that there could be a popup upon introducing "vm"
> in either context.  Regardless if this will be the case or we will
> stick just with verbose labels, documention will be affected for sure,
> hence cloning a documentation bug...

--- Additional comment from Jan Pokorný on 2014-05-26 15:32:40 CEST ---

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.)
Note You need to log in before you can comment on or make changes to this bug.