There is a case where `multipathd show status` should fail, yet it
doesn't exit with an error code. Instead it returns 0. Error is printed
to stdout as "error receiving packet".
This means that enforce will not work as expected.
But that patch is missing in some packages, so this patch adds a
workaround to detect the error base on the stdout of the multipathd show
status command.
Closes-Bug: #1789699
Change-Id: I1cb29782541e3fe53b0b1744ab36f56464cd2135
(cherry picked from commit 028af871de8a3f45f4cc8342e92d5586a7058e5a)
(cherry picked from commit f2fed213f6b1d36513504d0ec4ebbfeeddc52b94)
Reviewed: https:/ /review. openstack. org/647783 /git.openstack. org/cgit/ openstack/ os-brick/ commit/ ?id=ce72e77959a 6834620793dc9d4 006432781d09d7
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit ce72e77959a6834 620793dc9d40064 32781d09d7
Author: Gorka Eguileor <email address hidden>
Date: Wed Aug 29 19:16:58 2018 +0200
Improve detection of multipathd running
There is a case where `multipathd show status` should fail, yet it
doesn't exit with an error code. Instead it returns 0. Error is printed
to stdout as "error receiving packet".
This means that enforce will not work as expected.
The multipathd error got fixed here: /www.redhat. com/archives/ dm-devel/ 2015-March/ msg00136. html
https:/
But that patch is missing in some packages, so this patch adds a
workaround to detect the error base on the stdout of the multipathd show
status command.
Closes-Bug: #1789699 e53b0b1744ab36f 56464cd2135 5f4cc8342e92d55 86a7058e5a) 513504d0ec4ebbf eeddc52b94)
Change-Id: I1cb29782541e3f
(cherry picked from commit 028af871de8a3f4
(cherry picked from commit f2fed213f6b1d36