-
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
Error executing action create
on resource 'lvm_physical_volume['/dev/sdb']'
#99
Comments
provide Marking -ff implies that you need to force pvcreate, aka a phys volume has already been created on that block device |
Hello @fooshards , I am unfortunately running into the same issue... is there a way to "force" the pvcreate in this type of situation? I have a VG that already exists and I am trying to add the physical volume to the VG. I've added the "wipe_signatures true" attribute in my code but am still getting the same error as @bcorner13... not sure if this is the appropriate way to resolve this issue, or if there is something else I could be missing? Error: Using version 6.1.0 of the LVM cookbook... The following code block is what is failing:
|
Cookbook version
2.1
Chef-client version
version 12.8.1
Platform Details
Red Hat Enterprise Linux Server release 6.7 (Santiago)
Scenario:
execute lvm_physical_volume physical_volumes.to_s on subsequent executions of the chef client
Steps to Reproduce:
lvm_physical_volume physical_volumes.to_s
lvm_volume_group group.to_s do
physical_volumes physical_volumes.to_s
end
lvm_logical_volume name.to_s do
group group.to_s
size size.to_s
filesystem filesystem.to_s
mount_point mount_point.to_s
if stripes.to_i > 0
stripes = stripes.to_s
end
end
If I comment out the lvm_physical_volume it completes. So its not detecting that the pvcreate has already been run.
Expected Result:
to see the pvcreate has already been executed and continue execution of cookbook.
Actual Result:
The text was updated successfully, but these errors were encountered: