-
Notifications
You must be signed in to change notification settings - Fork 122
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
LV Fails to create logical volumes with undefined method gsub #123
Comments
The attributes used were |
I tried to hard set the the LV with the following Doing that resulted in the EXACT same error. This is being run against a RHEL 7.2 system. Any ideas? Im pretty sure this is a bug. I did try to run it against the 4.0.4 version as well. |
I think you need to specify a volume group. group = new_resource.group |
The volume group name is specified. At least according to the examples.
…On Tue, Jan 24, 2017 at 5:47 PM Mark Gibbons ***@***.***> wrote:
I think you need to specify a volume group.
group = new_resource.group
device_name = "/dev/mapper/#{**to_dm_name(group)**}-#{to_dm_name(name)}"
```
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK5Pc7v08F3eg4710WmxPL9RyBzhjoZKks5rVn-SgaJpZM4LsX97>
.
--
--------------------------------------------------
This e-mail transmission contains information intended only for the use of
the recipient(s) named above. Further, it contains information that may be
privileged and confidential. If you are not the intended recipient, you
are hereby notified that any dissemination, distribution, or copying of
this message (including any attachments) is strictly prohibited. If you
have received this e-mail in error, please notify the sender by reply
e-mail and then delete this message from your mail system. Thank you for
your compliance.
|
lvm_logical_volume key do I still don't see it. |
I will post the full recipe tomorrow. It's all at work. I thought I had
posted it all in the origins. Sorrry.
…On Tue, Jan 24, 2017 at 6:33 PM Mark Gibbons ***@***.***> wrote:
lvm_logical_volume key do
size "#{size}G"
filesystem 'xfs'
mount_point location: "#{path}, options: 'noatime,nodiratime'"
end
I still don't see it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK5Pc8M4RUDWayskegcpnj_DtTyG1Fa6ks5rVoo-gaJpZM4LsX97>
.
--
--------------------------------------------------
This e-mail transmission contains information intended only for the use of
the recipient(s) named above. Further, it contains information that may be
privileged and confidential. If you are not the intended recipient, you
are hereby notified that any dissemination, distribution, or copying of
this message (including any attachments) is strictly prohibited. If you
have received this e-mail in error, please notify the sender by reply
e-mail and then delete this message from your mail system. Thank you for
your compliance.
|
Just saying, rather than post the recipe, try specifying the the volume_group for the resource. Fixing "volume_group is not required" is in my back log of PRs to make against this product. It's a pretty well known problem. |
I had the lvm_logical_volume within a lvm_volume_group block and didn't understand that you were stating to remove it from the block and just add the group option to the lvm_logical_volume resource. The reason the lvm_volume_group was not shown but I stated it was given was because it was in the outer block. As you stated, adding the group option to the lvm_logical_volume resource worked perfectly. Thanks again for the help. |
Cool. Cheers |
Cookbook version
4.0.5
Chef-client version
12.13.7
Platform Details
RHEL 7.2 AWS
Scenario:
Creating a VG Data with a Raw disk size of 10G. Calculating the remaining size of the disk from after 3 filesystems and creating a 4th with the remainder. The issue occurs long before that.
Steps to Reproduce:
The issue occurs during the first creation of an LV object.
Expected Result:
4 Filesystems of the proper size to be created.
Actual Result:
The text was updated successfully, but these errors were encountered: