Bug 1395338 - Cannot configure "max_restarts" nor "restart_expire_time" for neither service nor vm at a root of a resource group
Summary: Cannot configure "max_restarts" nor "restart_expire_time" for neither service...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: luci
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-15 17:14 UTC by Jan Pokorný [poki]
Modified: 2017-11-15 00:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-15 00:43:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jan Pokorný [poki] 2016-11-15 17:14:40 UTC
Furthermore, as luci can only configure vm at the resource group root
([bug 1100817]), it doesn't make any sense to allow configuring
"Independent Subtree/Non-Critical Options" for it (the title pair
is a direct substitute for the respective underscored pair of parameters
in this context).

Comment 1 Chris Feist 2017-11-15 00:43:32 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production
3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent
Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and
will be marked as CLOSED/WONTFIX. If this remains a critical requirement,
please contact Red Hat Customer Support to request a re-evaluation of the
issue, citing a clear business justification. Note that a strong business
justification will be required for re-evaluation. Red Hat Customer Support can
be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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