-
Notifications
You must be signed in to change notification settings - Fork 273
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
Don't execute the lvm commands when not supported. #193
Conversation
When lvm_support was not present, facter would still attempt to execute the vgs and pvs commands.
@smithj4 many thanks for your contribution. |
@pmcmaw Any chance of getting a puppetlabs-lvm module release with this fix included? |
Hey @fatmcgav, |
Version 1.0.1 has now been released. Thank you for your patience @fatmcgav |
@pmcmaw Cheers for the quick turn-around :D |
Unfortunately you've deleted the changes, merged in puppetlabs#193 with the new release 1.1.0. Error: Facter: error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/lvm_support.rb: execution of command "vgs -o name --noheadings 2>/dev/null" failed: command not found.
Don't execute the lvm commands when not supported. #193
For anyone landing here, it seems that version 1.1.0 misses this PR, while 1.2.0 brings it back. So if you need this patch, remember to use at least version 1.2.0. |
Don't execute the lvm commands when not supported.
Unfortunately you've deleted the changes, merged in puppetlabs#193 with the new release 1.1.0. Error: Facter: error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/lvm_support.rb: execution of command "vgs -o name --noheadings 2>/dev/null" failed: command not found.
Don't execute the lvm commands when not supported. puppetlabs#193
When lvm_support was not present, facter would still attempt to execute the vgs and pvs commands.