The problem is not in the OS. I had the same issue and I have CentOS 6.2. It turned out that puppet-lvm is not a regular module but a puppet plugin. So, after installing the module, it needs to be sync'ed to the client machines. pluginsync and factsync are not enabled by default. The command: sudo puppet agent --test --verbose --pluginsync worked for me. In case anybody is having the same issue as I couldn't find a solution anywhere. Jesus.
El miércoles, 29 de febrero de 2012 03:41:22 UTC-5, Matt escribió: > I get the same problem with CentOS. > No error but no LV created. > > I've tried with Ubuntu client and same issue. > > Something might be wrong within the module... > > Matt > > On Feb 4, 1:59 am, Luke <[email protected]> wrote: > > Oh well. Maybe thislvmmodule doesn't like centos or something :( > > > > Thanks for all your help Felix. If anyone else has any ideas or > betterlvmtype modules please drop a line. > > > > On Feb 3, 1:42 pm, Felix Frank <[email protected]> > > wrote: > > > > > > > > > > > > > > > > > On 02/03/2012 06:37 PM, Luke wrote: > > > > > > if ! defined(Physical_volume[$pv]) { > > > > physical_volume { $pv: ensure => present } > > > > } > > > > > Ah, dreadful ;-) > > > > > But there goes that theory - the PV and VG are implicitly created, so > > > the module really *should* do the right thing. > > > > > So the issue is probably with the provider(?) > > > I'm stumped. > > > > > Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/hRL9Jia7TFwJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
