We observed failed bigboot jobs on hosts where all logical volumes do not have autoactivation property set. When this is the case, the lsblk commands in bigboot.sh don't detect that the next partition holds an LVM physical volume. That leads to the pvresize not being done and then it all goes come-a-gutsa from there! Recommend fixing this by doing lvm vgchange -ay before kicking off the bigboot.sh script.
We observed failed bigboot jobs on hosts where all logical volumes do not have autoactivation property set. When this is the case, the
lsblk
commands inbigboot.sh
don't detect that the next partition holds an LVM physical volume. That leads to thepvresize
not being done and then it all goes come-a-gutsa from there! Recommend fixing this by doinglvm vgchange -ay
before kicking off thebigboot.sh
script.