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.

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

OSMount: fix internal VG name referencing conflict. #322

Merged
merged 1 commit into from
Jul 3, 2024

Conversation

aznashwan
Copy link
Member

The Coriolis OSMount code would internally keep a mapping between names of VGs it should activate and their PVs, which could potentially lead to VGs with multiple PVs to be referneced both by their original name, as well as a new one Coriolis generates to avoid naming conflicts in /dev/$VG_NAME/$LVM_NAME.

Copy link
Contributor

@Dany9966 Dany9966 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code LGTM, but please fix the pep8 errors. You got a couple of "line too longs" :D

@aznashwan aznashwan force-pushed the fix-multi-pv-vg-naming branch 4 times, most recently from bbbf250 to 3e98ade Compare July 3, 2024 10:56
The Coriolis OSMount code would internally keep a mapping between
names of VGs it should activate and their PVs, which could potentially
lead to VGs with multiple PVs to be referneced both by their original
name, as well as a new one Coriolis generates to avoid naming conflicts
in /dev/$VG_NAME/$LVM_NAME.

Signed-off-by: Nashwan Azhari <nazhari@cloudbasesolutions.com>
@Dany9966 Dany9966 merged commit 87401a6 into cloudbase:master Jul 3, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants