52537418e6
Historically, with CentOS, we had issues related to LV activation
occurring in a non-deterministic way and causing an assortment of
provisioning issues. More deterministic LV activation was achieved by
setting use_lvmetad = 0 in /etc/lvm/lvm.conf
In the migration to Debian, a much more recent version of the lvm2
package is in use. In the intervening versions of lvm2, lvmetad was
removed making use_lvmetad and the associated behavior now obsolete.
In some current random testing scenarios, emergency mode is seen when
booting the Debian ISO. Reviewing the systemd dump of services
initiating when emergency mode occurs, it is observed that LV activation
is occurring at a different time and order vs. a successful boot.
The Debian lvm2 version provides configuration parameter
global/event_activation which when set to 0 will change LV activation
behavior when a PV appears. No noticable change was observed when this
variable is set.
The current upstream version from Debian Bullseye is missing an lvm2
upstream patch the should address this issue.
Patch the Debian lvm2 version with this upstream patch to enable testing
with this enabled.
Test Plan:
PASS - Build ISO, install/provision in AIO-SX virtual/hardware labs
PASS - Perform numerous reboot cycles an observe no issues
PASS - Test on H/W setup that has shown energency mode behavior to
confirm that this version and associated config file change
resolved emergency mode PV/LV activation issues
Change-Id: If22e446126f33c2155bd70988ed9b0444d230730
Partial-Bug: #1979105
Signed-off-by: Robert Church <robert.church@windriver.com>
2 lines
52 B
Plaintext
2 lines
52 B
Plaintext
0001-pvscan-support-disabled-event_activation.patch
|