Bug 1415074 - ccs_config_validate fails when called from cron (or a script invoked by cron)
Summary: ccs_config_validate fails when called from cron (or a script invoked by cron)
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cluster
Version: 6.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Christine Caulfield
QA Contact: cluster-qe@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-20 07:36 UTC by Madison Kelly
Modified: 2017-12-06 11:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-06 11:58:28 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Madison Kelly 2017-01-20 07:36:03 UTC
Description of problem:

If ccs_config_validate is called from cron (or by a script called by cron), PATH isn't set, and it calls ccs_update_schema without specifying the path. If cron doesn't set PATH, then the ccs_config_validate itself fails. 

==== line 190~192
if [ "$updaterelaxng" != 0 ]; then
        updateerr="$(ccs_update_schema 2>&1)"
        if [ $? != 0 ]; then

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


How reproducible:


Steps to Reproduce:
1. Call it from crontab

Actual results:

Expected results:

Additional info:

Comment 4 Jan Kurik 2017-12-06 11:58:28 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:


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:


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