Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bigboot can fail if autoactivation property not set #57

Closed
swapdisk opened this issue Feb 13, 2024 · 2 comments
Closed

Bigboot can fail if autoactivation property not set #57

swapdisk opened this issue Feb 13, 2024 · 2 comments

Comments

@swapdisk
Copy link
Member

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.
@swapdisk swapdisk self-assigned this Feb 13, 2024
@swapdisk
Copy link
Member Author

@jchristianh - I'll leave this to you. Thanks!

@swapdisk swapdisk removed their assignment Feb 13, 2024
jchristianh added a commit to jchristianh/infra.lvm_snapshots that referenced this issue Feb 13, 2024
@jchristianh
FIX redhat-cop#57 - Add activate_volume_groups to increase-boot-parti…
e584d12 
…tion.sh.j2
@jchristianh
Copy link
Contributor

@swapdisk Please review and test the proposed fix. Thanks!

@swapdisk swapdisk mentioned this issue Feb 15, 2024
Merged
swapdisk added a commit that referenced this issue Mar 6, 2024
@swapdisk
changelog for fixing issue #57
03add12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@swapdisk @jchristianh