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.
luci will allow users to set max_restarts, __max_restarts, and __max_failures without setting their corresponding timeouts, and vice versa.
A fix for these issues is already upstream:
commit 616e70d2a760175bd27262766efb85e63ea980fd
Author: Ryan McCabe <rmccabe>
Date: Thu Nov 15 11:08:48 2012 -0500
luci: Fix handling of subtree options
For subtrees, error out if __max_failures is set by __failure_expire_time
is not, and vice versa. Also error out if __max_restarts is set but
__restart_expire_time is not, and vice versa.
Signed-off-by: Ryan McCabe <rmccabe>
commit 0f0db639ab786c386fb8182fa82ce6bbe93dda8e
Author: Ryan McCabe <rmccabe>
Date: Thu Nov 15 10:56:52 2012 -0500
luci: Error out if max_restarts is set but not restart_expire_time
Error out if max_restarts is set but restart_expire_time is not set,
and vice versa, on the service group config form.
Signed-off-by: Ryan McCabe <rmccabe>
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/RHBA-2013-0309.html
luci will allow users to set max_restarts, __max_restarts, and __max_failures without setting their corresponding timeouts, and vice versa. A fix for these issues is already upstream: commit 616e70d2a760175bd27262766efb85e63ea980fd Author: Ryan McCabe <rmccabe> Date: Thu Nov 15 11:08:48 2012 -0500 luci: Fix handling of subtree options For subtrees, error out if __max_failures is set by __failure_expire_time is not, and vice versa. Also error out if __max_restarts is set but __restart_expire_time is not, and vice versa. Signed-off-by: Ryan McCabe <rmccabe> commit 0f0db639ab786c386fb8182fa82ce6bbe93dda8e Author: Ryan McCabe <rmccabe> Date: Thu Nov 15 10:56:52 2012 -0500 luci: Error out if max_restarts is set but not restart_expire_time Error out if max_restarts is set but restart_expire_time is not set, and vice versa, on the service group config form. Signed-off-by: Ryan McCabe <rmccabe>