[BUG] `Umount.sh` script's Cleanup Logic Doesn't Recognize Non-Default VG Names
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 10
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
If invoking Umount.sh with the -C flag-argument and the build-target disk contains a VG other than RootVG, it may not work as expected.
Expected behavior
Using Umount.sh -C <DEVICE> results in <DEVICE> being immediately (re)usable by the DiskSetup.sh script
Deviance Description
If the build-target disk contains a VG other than RootVG, it won't find and delete the LVM2 volume-group and associated objects, leaving the named-device not immediately (re)usable by the DiskSetup.sh script
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Umount.sh and trace the cleanup path used by the -C flag, then compare its expectations with DiskSetup.sh. Reproduce the behavior using a build-target disk whose volume group is not RootVG. Done means Umount.sh -C leaves the device immediately reusable by DiskSetup.sh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100