Bug 723188 - Luci does not allow to modify __max_restarts and __restart_expire_time for independent subtrees, only for non-critical resources.
Summary: Luci does not allow to modify __max_restarts and __restart_expire_time for in...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: conga
Version: 5.6
Hardware: Unspecified
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-19 10:46 UTC by Alfredo Moralejo
Modified: 2012-02-21 03:16 UTC (History)
2 users (show)

Fixed In Version: conga-0.12.2-34.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-21 03:16:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0151 0 normal SHIPPED_LIVE Moderate: conga security, bug fix, and enhancement update 2012-02-21 07:24:48 UTC

Description Alfredo Moralejo 2011-07-19 10:46:46 UTC
Description of problem:

Luci does not allow to modify __max_restarts and __restart_expire_time for independent subtrees, only for non-critical resources.

Version-Release number of selected component (if applicable):

luci-0.12.2.24.el5_6.1

How reproducible:

Always

Steps to Reproduce:
1. From luci, for any resource, enable option "This resource is an independent subtree" and apply change.

2. Try to set values for "Maximum number of restart failures before giving up (applies only for non-critical resources)" and "Restart expire time (applies only for non-critical resources)"
  
Actual results:

Values are not added for resource in cluster.conf


Expected results:

AFAIK, values provided should be added as __max_restarts and __restart_expire_time, as it's used for resources with __independent_subtree="1", not only for non-critical resources. User should be able to modify this values from luci.

Comment 6 errata-xmlrpc 2012-02-21 03:16:32 UTC
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-2012-0151.html


Note You need to log in before you can comment on or make changes to this bug.