Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1363830 - friendly-name change no non-friendly-name failed after set user_friendly_names from yes to no
friendly-name change no non-friendly-name failed after set user_friendly_name...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: device-mapper-multipath (Show other bugs)
7.3
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Ben Marzinski
Zhang Yi
Steven J. Levine
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-08-03 12:46 EDT by Zhang Yi
Modified: 2016-11-04 04:20 EDT (History)
5 users (show)

See Also:
Fixed In Version: device-mapper-multipath-0.4.9-96.el7
Doc Type: Bug Fix
Doc Text:
Multipath no longer occasionally fails while renaming devices Previously, multipath was using an uninitialized variable in the function to rename a device. This would cause multipath to fail occasionally while renaming a device because the variable was set to an invalid value. With this fix, multipath now initializes this variable when renaming a device.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-04 04:20:58 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-2016:2536 normal SHIPPED_LIVE device-mapper-multipath bug fix and enhancement update 2016-11-03 10:18:10 EDT

  None (edit)
Comment 3 Ben Marzinski 2016-08-05 17:42:02 EDT
This (and possibly Bug 1363937) are caused by an uninitialized variable being passed by dm_rename. I have a fix for it.
Comment 7 errata-xmlrpc 2016-11-04 04:20:58 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-2016-2536.html

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