Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1696994 - Wrong exit code on init script failure
Summary: Wrong exit code on init script failure
Status: NEW
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: mariadb
Version: rh-mariadb102
Hardware: Unspecified
OS: Unspecified
Target Milestone: alpha
: 3.3
Assignee: Michal Schorm
QA Contact: qe-baseos-daemons
Depends On:
TreeView+ depends on / blocked
Reported: 2019-04-06 23:47 UTC by Michal Schorm
Modified: 2019-04-08 14:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Michal Schorm 2019-04-06 23:47:22 UTC
Applicable only on RHEL6.


Service file:

Contains line:
  /opt/rh/rh-mariadb101/root/usr/libexec/mysql-prepare-db-dir $MYUSER $MYGROUP >/dev/null || return 4


However the exit code "4" is not correct as per:

The correct exit code on failure should be "1".


This behaviour also lead to Test case failure:


Originally filed against 10.1 collection as #1558044


Not applicable on later (10.3+) MariaDB collections, as they are not released for RHEL6.

Comment 2 Michal Schorm 2019-04-06 23:58:24 UTC
Looks like this exit code was brought from Fedora when updating RHEL 5.5.40 SPECfile to 10.0.15

Comment 3 Michal Schorm 2019-04-08 14:40:26 UTC
DEV notes:
  * we won't fix it in the already released collection to prevent issues on the customer's side who might rely on the return code.
QA note:
  * the test should be enhanced to accept this error code as an expected behaviour for MariaDB collections.

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