-
Notifications
You must be signed in to change notification settings - Fork 276
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
volume_group type does not handle passing of physical_volumes as a hash #219
Conversation
|
I'd love to see this getting merged. |
|
What's preventing this change from being merged? We need a corrective release as well. Example from README.md where physical_volumes represented as a hash is not working. |
|
I wish somebody merged this fix. It's obviously bug being spotted 9 month ago. Example from README.md doesn't work and nobody cares. |
|
Yeah. It sucks. Guess its time to switch to Ansible. |
|
@rodjek is there anyone you can lean on to get this reviewed and - if appropriately fixed - merged? |
|
Hi @dacron, I'm sorry that this PR has lingered so long without action :( I've pinged some people internally to have a look at it and get back to you. |
|
Hi @dacron thanks for the fix ! |
|
Hi, @tphoney. Here is part of my config in Hiera. Puppet throws error. We have embedded array [ ['/dev/disk/by-id/nvme-eui.0025388191bd020c']]. It happens only for one-key hash of physical_volumes. It works properly in this case (one key) with the patch. |
|
Thanks @dacron i have reverted this PR, we need some testing around this PR. Looking into it |
|
@tphoney, @dacron, can you try this branch on my fork? https://github.com/michaeltlombardi/puppetlabs-lvm/tree/maint/master/volume_group-hash-handling Got a WIP PR up with (some) testing last night: |
volume_group type does not handle passing of physical_volumes as a hash
The documentation (README) indicates that we can do this:
However, this results in a message like so:
The issue is that although the defines permit the passing of physical_volumes as a hash, the type/provider does not.
This pull request attempts to fix that.