Leaving the multipath option enabled on Debian was causing
the lock-unlock process to fail with an error message pointing
to the multipath.conf file that stated:
"error parsing config file"
The parsing error happens because "*" is not a valid regular
expression and the solution was simply changing "*" to ".*"
Test Plan (CentOS & Debian):
PASS: Build and Install
PASS: Unlock Controller-0
PASS: Multiple lock-unlock
PASS: multipathd service faced no errors
Reviewed: https:/ /review. opendev. org/c/starlingx /stx-puppet/ +/858440 /opendev. org/starlingx/ stx-puppet/ commit/ 396be6304c9fc70 e4d2852c8bb58ad e7a4069939
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 396be6304c9fc70 e4d2852c8bb58ad e7a4069939
Author: Matheus Guilhermino <email address hidden>
Date: Mon Sep 19 14:04:50 2022 -0300
Fix blacklist on multipath.conf
Leaving the multipath option enabled on Debian was causing
the lock-unlock process to fail with an error message pointing
to the multipath.conf file that stated:
"error parsing config file"
The parsing error happens because "*" is not a valid regular
expression and the solution was simply changing "*" to ".*"
Test Plan (CentOS & Debian):
PASS: Build and Install
PASS: Unlock Controller-0
PASS: Multiple lock-unlock
PASS: multipathd service faced no errors
Closes-bug: 1990183
Signed-off-by: Matheus Guilhermino <email address hidden> c9440233014d6c6 6dbe50ed07a
Change-Id: I750589d4268fff