similar to: Resource Scope

Hello, I have this bit of code that tries to remove a physical volume from the VG (which consists of /dev/sda5 amd /dev/sdb1): volume_group { "system": ensure => absent, physical_volumes => "/dev/sdb1", } But I get this error: Error: Execution of

Trying to setup a volume group with puppet lvm and this:- volume_group { "my_vg": ensure => present, physical_volumes => "/dev/sdb /dev/sdc /dev/sdd", require => [ Physical_volume["/dev/sdb"], Physical_volume["/dev/sdc"], Physical_volume["/dev/sdd"] ] } Fails with this in the debug

Hello, Using the LVM module/providers from the forge I want to create a logical volume at the maximum size and I cannot work out how to do this. physical_volume -> volume_group -> logical_volume -> filesystem -> mount All works fine but you have to hard code the size for the logical volume. Anyone know if this is possible ? Thanks Paul -- You received this message because you

First run of puppet performs a configsync and an attempt to load the downloaded plugins, the provider fails to be found by puppet in this first run, another re-run of puppet is needed for the provider to work, see debug output below. Is this a bug or am I missing something you think? The error in short: err: /Stage[main]/Ibe::Slave/Logical_volume[mysql]: Could not evaluate: No ability to

i would like to use the module puppet-lvm and would like to pass values to it. I have it setup properly as a module but I can''t for the lfe of me get it to take any values that I put in my baseconfig.pp in my home folder. like shouldn''t something like this work?? puppet-lvm {''setvolume'': vg => ''myvg'', pv =>

I''ve installed the puppet labs lvm module. After fixing the missing "}" at line 20 in init.pp (really?!?!), I''m getting this:'' err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type physical_volume at /truth/sauce/env/prod/modules/role/manifests/common.pp:43

How can I pass an array to a define? It''s not documented in the puppet language guide. I''ve got: define lvm::create_vg ( $pvdisks ) { exec { ''pvcreate'': command => "/sbin/pvcreate -yf $pvdisks", unless => "/sbin/pvdisplay $pvdisks", ... } } class someclass { lvm::create_vg {

We need to refer to common variables across multiple modules. For example, our dns module, firewall module and monitoring module need knowledge of our radius server IP address. Is the correct approach to create a ''common'' class where these variables are defined and then reference them from each module and create a class dependancy as below. We are using a custom ENC which

Hello people, I''m starting using XEN with LVM and I have to say that LVM seems very good to me. But I have a problem, the Volume Group that I create (with Physical Volumes and formatted Logical Volumes inside) dissappears when I reboot my computer. I mean it doesn''t disappears, /dev/volume_group directory disappears, so I can''t mount it, or use them with XEN. Could

My issue may be related to this bug: http://projects.puppetlabs.com/issues/13858 "Custom types in environments require loading into master''s libdir" However, now I''m not so sure, This was working previously with a given client. However, after trying on a fresh client, it''s failing with: err: Could not run Puppet configuration client: Could not find a

We''re trying to set a role variable in one of our role classes i.e. class role::nameserver { $::role = ''nameserver'' include profile::baseline } however we get the following error Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment production: Cannot assign to variables in other namespaces We do not get