Bug 1214904 - mysqld_safe generates errors on sed
Summary: mysqld_safe generates errors on sed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: mariadb-galera
Version: 5.0 (RHEL 6)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: z5
: 5.0 (RHEL 6)
Assignee: Michael Bayer
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On: 1134032
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-23 20:10 UTC by Michael Bayer
Modified: 2023-02-22 23:02 UTC (History)
8 users (show)

Fixed In Version: mariadb-galera-5.5.41-2.el6ost
Doc Type: Bug Fix
Doc Text:
Previously, a call to the "sed" command within mysqld_safe.sh which was used to certain command line arguments failed to accommodate arguments which included a slash, such as the paths to the SSL key and certificate files to pass through this function. As a consequence, the mysqld_safe.sh script produced warnings of the form "unknown option to `s'". The script continued to work correctly otherwise as these arguments are not actually needed in this specific context. With this update, the call to sed has been corrected such that the SSL arguments which include slashes are properly interpreted. As a result, the warnings regarding sed are now resolved.
Clone Of: 1134032
Environment:
Last Closed: 2015-09-10 11:45:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1763 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Bug Fix and Enhancement Advisory 2015-09-10 15:45:07 UTC

Comment 8 errata-xmlrpc 2015-09-10 11:45:16 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.

https://rhn.redhat.com/errata/RHBA-2015-1763.html


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