Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1214904 - mysqld_safe generates errors on sed
mysqld_safe generates errors on sed
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: mariadb-galera (Show other bugs)
5.0 (RHEL 6)
Unspecified Unspecified
low Severity low
: z5
: 5.0 (RHEL 6)
Assigned To: Michael Bayer
Leonid Natapov
: Rebase, ZStream
Depends On: 1134032
Blocks:
  Show dependency treegraph
 
Reported: 2015-04-23 16:10 EDT by Michael Bayer
Modified: 2015-09-10 07:45 EDT (History)
9 users (show)

See Also:
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.
Story Points: ---
Clone Of: 1134032
Environment:
Last Closed: 2015-09-10 07:45:16 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1763 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Bug Fix and Enhancement Advisory 2015-09-10 11:45:07 EDT

  None (edit)
Comment 8 errata-xmlrpc 2015-09-10 07:45:16 EDT
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.