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:
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 wrote:
> Oh well. Maybe thislvmmodule doesn't like centos or something :(
>
> Thanks for all your help Felix.
It's bound to be sub-optimal, but I too found puppet-lvm hard to get started
with. Firstly, I took a long time to discover that I needed to set pluginsync
to get the module copied to all hosts:-
augeas { "puppet-pluginsync":
context => "/files/etc/puppet/puppet.conf/main",
changes
And I kickstart and script (%post kickstart section) where possible but I'm
going to look into the lvm module after finding it a couple of days ago - for
partitions I don't plan on hosts I can't rebuild.
HTH
Den
On 08/02/2012, at 1:00, jcbollinger wrote:
>
>
> On Feb 6, 11:23 am, Luke wrot
On Feb 6, 11:23 am, Luke wrote:
> How does everyone else manage LVM on centos? Do you do it manually? Do
> you have a shell script? Some how through puppet?
I do it manually. If I had to do a lot of identical boxes then I
might script it, maybe via kickstart, but it's not the sort of thing I
n
How does everyone else manage LVM on centos? Do you do it manually? Do
you have a shell script? Some how through puppet?
On Feb 3, 1:59 pm, Luke wrote:
> Oh well. Maybe thislvmmodule doesn't like centos or something :(
>
> Thanks for all your help Felix. If anyone else has any ideas or betterlvmt
Oh well. Maybe this lvm module doesn't like centos or something :(
Thanks for all your help Felix. If anyone else has any ideas or better
lvm type modules please drop a line.
On Feb 3, 1:42 pm, Felix Frank
wrote:
> On 02/03/2012 06:37 PM, Luke wrote:
>
> > if ! defined(Physical_volume[$pv]
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 pr
Just to have it out in the open:
Here is the manifest from the lvm module
define lvm::volume($vg, $pv, $fstype = undef, $size = undef, $ensure)
{
case $ensure {
#
# Clean up the whole chain.
#
cleaned: {
# This may only need to exist once
if ! defined(Physical_volume[
The PV and VG are not defined anywhere else that I can see.
On Feb 3, 11:40 am, Felix Frank
wrote:
> On 02/03/2012 03:45 PM, Luke wrote:
>
> > root@luketest ~]# pvdisplay
>
> Ugh, why do people insist on using this instead of pvs?
>
> Anyway, you're right, the LV isn't there. Neither is the PV.
>
On 02/03/2012 03:45 PM, Luke wrote:
> root@luketest ~]# pvdisplay
Ugh, why do people insist on using this instead of pvs?
Anyway, you're right, the LV isn't there. Neither is the PV.
Are the PV and VG defined somewhere in your manifest? They should be. I
have no experience with this module, but
Hi John,
I did exactly what you said and got the same result:
debug: Creating default schedules
debug: Loaded state in 0.00 seconds
debug: /Stage[main]//Node[luketest.mgmt.mydomain.local]/
Lvm::Volume[setvolume]/Volume_group[myvg]/require: requires
Physical_volume[/dev/sdb]
debug: /Stage[main]//N
On Feb 3, 7:37 am, Luke wrote:
> Hi,
>
> site.pp
>
> manifests]$ cat site.pp
> import "nodes"
That import is appropriate.
> import "modules"
That one should not be needed.
>
>
> manifests]$ cat modules.pp
> import "lvm"
That whole manifest should not be need.
> -
Here you go
root@luketest ~]# pvdisplay
/dev/hdc: open failed: No medium found
--- Physical volume ---
PV Name /dev/sda2
VG Name VolGroup00
PV Size 9.90 GB / not usable 22.76 MB
Allocatable yes (but full)
PE Size (KByte) 32768
Hi,
On 02/03/2012 03:04 PM, Luke wrote:
> Disk /dev/sdb: 8589 MB, 8589934592 bytes
> 255 heads, 63 sectors/track, 1044 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Disk /dev/sdb doesn't contain a valid partition table
>
> Its not even doing anything with /dev/sdb.
What makes
It doesn't matter what I put in it does the same thing:
debug: /Stage[main]//Node[luketest.mgmt.mydomain.local]/
Lvm::Volume[setvolume]/Filesystem[/dev/awesomevg/awesomename]/require:
requires Logical_volume[awesomename]
debug: /Stage[main]//Node[luketest.mgmt.mydomain.local]/
Lvm::Volume[setvolum
Hi Felix,
Thats the thing the LV doesn't exist so I don't know why it is acting
like it does:
Disk /dev/sda: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev
On 02/03/2012 02:51 PM, Luke wrote:
> info: /Whit[/dev/sdb]: valuated in 0.00 seconds
> info: /Whit[myvg]: valuated in 0.00 seconds
> info: /Whit[mylv]: valuated in 0.00 seconds
> info: /Whit[/dev/myvg/mylv]: valuated in 0.00 seconds
Looks like it's working all right. But seeing as the LV exists a
This is the module here that I am trying to get working:
https://github.com/puppetlabs/puppet-lvm
On Feb 3, 9:51 am, Luke wrote:
> [root@luketest ~]# puppet agent --test --evaltrace
> info: Caching catalog for luketest.mgmt.mydomain.local
> info: Applying configuration version '1328245279'
> inf
[root@luketest ~]# puppet agent --test --evaltrace
info: Caching catalog for luketest.mgmt.mydomain.local
info: Applying configuration version '1328245279'
info: /Schedule[puppet]: valuated in 0.00 seconds
info: /Filebucket[puppet]: valuated in 0.00 seconds
info: /Schedule[never]: valuated in 0.00
Hi,
On 02/03/2012 02:37 PM, Luke wrote:
> When I name the module lvm. I applys the config but doesn't do
> anything.
> info: Caching catalog for luketest.mgmt.mydomain.local
> info: Applying configuration version '1328241141'
> notice: Finished catalog run in 0.03 seconds
please repeat with --eva
Hi,
site.pp
manifests]$ cat site.pp
import "nodes"
import "modules"
manifests]$ cat modules.pp
import "lvm"
cat nodes.pp
node 'luketest.mgmt.mydomain.local' {
lvm::volume {'setvolume':
vg => 'myvg',
pv => '/dev/sdb',
fstype => 'ext3
Hi,
On 02/03/2012 01:33 PM, Luke wrote:
> Hmmm that is what I have been doing but for some reason it keeps
> messing up. Do I have to do an include or something for the puppet-lvm
> module? I mean I already have an import statement for it in my
> sites.pp.
please share a relevant excerpt from you
Hmmm that is what I have been doing but for some reason it keeps
messing up. Do I have to do an include or something for the puppet-lvm
module? I mean I already have an import statement for it in my
sites.pp.
On Feb 2, 4:51 pm, jcbollinger wrote:
> On Feb 2, 1:53 pm, Luke wrote:
>
>
>
>
>
>
>
>
On Feb 2, 1:53 pm, Luke wrote:
> Thank you for your help.
>
> I am pretty new to puppet but am making some progress.
>
> One question how do I get the:
>
> lvm::volume {'setvolume':
> vg => 'myvg',
> pv => '/dev/sdb',
> fstype => 'ext3',
> name => 'mylv',
>
Thank you for your help.
I am pretty new to puppet but am making some progress.
One question how do I get the:
lvm::volume {'setvolume':
vg => 'myvg',
pv => '/dev/sdb',
fstype => 'ext3',
name => 'mylv',
size =>'8G',
ensure => 'present',
Judging from the things you wrote here, you need a bit more
understanding of how puppet works with modules. Also, I see that that
specific module implements a define called lvm::volume, so your
manifest should be implementing a resource like so:
lvm::volume {'setvolume':
vg => 'myvg',
I am finding the documentation pretty poor on this. Can someone please
help?
I don't understand why I can't pass my variables.
On Jan 17, 10:56 am, Luke wrote:
> 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
28 matches
Mail list logo
