7a52314695
This commit:
- fixes some "multipathd error handling improvement"
release notes
- fixes a related comment in the code
Related launchpad issue https://bugs.launchpad.net/ironic-python-agent/+bug/2031092
Change-Id: Ie3ba0601fa117b053cb8db6284e47249ca9c9134
Signed-off-by: Adam Rozman <adam.rozman@est.tech>
20 lines
1.2 KiB
YAML
20 lines
1.2 KiB
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes the error handling of multipathd service startup/discovery process.
|
|
IPA handles both scenario when the multipathd service is already started
|
|
and the scenario when the service has not been started and in the second
|
|
scenario IPA will try to start the service. IPA is not checking whether
|
|
multipathd is running already and not, it will start the multipathd service
|
|
even it is already running and expects 0 error code even if the service
|
|
is already running. It has been noticed that with certain combinations of
|
|
distros and multipathd versions the error code is not 0 when IPA tries
|
|
to start multipathd when an instance of multipathd is already running.
|
|
When the expected return code is not 0 that causes an exception and that
|
|
will cause the multipath device discovery to terminate prematurely and
|
|
if the selected root device is a multipath device then IPA won't be
|
|
able to provision. This fix discards the exception that is caused by the
|
|
non 0 error code returned by the multipathd startup process. In case there
|
|
is a genuine issue with the multipath service, that would be caught when
|
|
the actual multipath device listing command is executed (multipath -ll).
|