thr3ads.net - Puppet users - [Puppet Users] OpenVZ configuration of networking with puppet

If this information is useful, please help other people find it:
Share via:

Jeff Leggett

2008-Jul-01 18:15 UTC

[Puppet Users] OpenVZ configuration of networking with puppet - big crash

I am trying to streamline the current distribution specific setup and
creation of VE''s within OpenVZ with puppet.  My first attempt has gone
horribly wrong as you will see below.  Here''s the script I wrote to
replace the redhat specific setup that OpenVZ used:

[jleggett@lxp6d15m3 scripts]$ cat redhat-add_ip.sh
#!/bin/bash
#

# Debug - take out later
set -x
LOGFILE=/tmp/add_ip-dbug.log
exec >$LOGFILE 2>&1

FACTER_IP_ADDR=$1
FACTER_VENET_DEV=venet0
FACTER_VENET_DEV_CFG=ifcfg-$FACTER_VENET_DEV
FACTER_IFNUM=$2
echo "Running puppet-ized version of redhat-add_ip.sh"
/bin/cat <<EOM | /usr/bin/puppet
file {"/etc/sysconfig/network-scripts/$VENET_DEV_CFG":
        owner => root,
        mode => 644,
        ensure => present,
        content => "DEVICE=$VENET_DEV\nBOOTPROTO=static\nONBOOT=yes
\nIPADDR=127.0.0.1\nNETMASK=255.255.255.255\nBROADCAST=0.0.0.0",
}
file {"/etc/sysconfig/network":
        owner => root,
        mode => 644,
        content => "NETWORKING=\"yes\"\nNETWORKING_IPV6=no
\nHOSTNAME=localhost.localdomain\nGATEWAY=\"192.0.2.1\"",
}
file {"/etc/sysconfig/network-scripts/$VENET_DEV_CFG:$IFNUM":
        owner => root,
        mode => 644,
        ensure => present,
        content => "ONBOOT=yes\nIPADDR=$IP_ADDR
\nNETMASK=255.255.255.255",
}
host {"localhost":
        alias => "localhost.localdomain",
        ip => "127.0.0.1",
        ensure => present,
        require => File["/etc/sysconfig/network-scripts/
$VENET_DEV_CFG"],
}
service {"network":
        enable => true,
        ensure => running,
        require => Host["localhost"],
}
EOM
[jleggett@lxp6d15m3 scripts]$

So when I start it all seems I get:

[jleggett@lxp6d15m3 ~]$ vzctl start 104
Warning: configuration file for distribution rhel-5-i386-minimal not
found default used
Starting VE ...
VE is mounted
Adding IP address(es): 192.168.0.3
+ LOGFILE=/tmp/add_ip-dbug.log
+ exec
Setting CPU units: 1000
Configure meminfo: 65536
VE start in progress...
[jleggett@lxp6d15m3 ~]$ vzctl enter 104
entered into VE 104
[root@localhost /]#

BUT the debug file log shows puppet puked on running in a starting VE:

[root@localhost /]# cat /tmp/add_ip-dbug.log
+ FACTER_IP_ADDR+ FACTER_VENET_DEV=venet0
+ FACTER_VENET_DEV_CFG=ifcfg-
+ FACTER_IFNUM+ echo ''Running puppet-ized version of
redhat-add_ip.sh''
Running puppet-ized version of redhat-add_ip.sh
+ /bin/cat
+ /usr/bin/puppet
Warning: cannot open /proc/net/dev (No such file or directory).
Limited output.
Could not load /usr/lib/ruby/site_ruby/1.8/facter/processor.rb: No
such file or directory - /proc/cpuinfo
dnsdomainname: Host name lookup failure
/usr/lib/ruby/site_ruby/1.8/facter/memory.rb:26:in `readlines'': No
such file or directory - /proc/meminfo (Errno::ENOENT)
        from /usr/lib/ruby/site_ruby/1.8/facter/memory.rb:26:in
`meminfo_number''
        from /usr/lib/ruby/1.8/thread.rb:33:in `exclusive''
        from /usr/lib/ruby/site_ruby/1.8/facter/memory.rb:24:in
`meminfo_number''
        from /usr/lib/ruby/site_ruby/1.8/facter/memory.rb:65
        from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `call''
        from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `value''
        from /usr/lib/ruby/site_ruby/1.8/facter.rb:355:in `value''
        from /usr/lib/ruby/site_ruby/1.8/facter.rb:352:in `each''
         ... 6 levels...
        from /usr/lib/ruby/site_ruby/1.8/puppet/indirector/facts/
facter.rb:60:in `find''
        from /usr/lib/ruby/site_ruby/1.8/puppet/indirector/
indirection.rb:170:in `find''
        from /usr/lib/ruby/site_ruby/1.8/puppet/indirector.rb:42:in
`find''
        from /usr/bin/puppet:185
[root@localhost /]#

But the files in /proc it wants to parse ARE there:

[root@localhost /]# cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 107
model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 4800+
stepping        : 2
cpu MHz         : 2505.680
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm
extapic cr8_legacy misalignsse
bogomips        : 5015.16
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps

processor       : 1
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 107
model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 4800+
stepping        : 2
cpu MHz         : 2505.680
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm
extapic cr8_legacy misalignsse
bogomips        : 5018.86
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps

[root@localhost /]#  cat /proc/meminfo
MemTotal:       262144 kB
MemFree:        256664 kB
Buffers:             0 kB
Cached:              0 kB
SwapCached:          0 kB
Active:              0 kB
Inactive:            0 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       262144 kB
LowFree:        256664 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:               0 kB
Writeback:           0 kB
AnonPages:           0 kB
Mapped:              0 kB
Slab:                0 kB
PageTables:          0 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:         0 kB
Committed_AS:        0 kB
VmallocTotal:        0 kB
VmallocUsed:         0 kB
VmallocChunk:        0 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB
[root@localhost /]#

You may be asking why I want to do this.  The answer is, I can get rid
of all the distro-specific shell scripts that openVZ includes by
default and boil it down to simple puppet manifests streamlined by use
of Puppet''s Resource Abstraction layer.

[jleggett@lxp6d15m3 scripts]$ ls
arch-add_ip.sh          gentoo-set_hostname.sh
slackware-9.x_del_ip.sh
arch-del_ip.sh          gentoo-set_ugid_quota.sh  slackware-add_ip.sh
arch-set_hostname.sh    postcreate.sh             slackware-del_ip.sh
arch-set_ugid_quota.sh  redhat-7.x_add_ip.sh      slackware-
set_hostname.sh
debian-add_ip.sh        redhat-add_ip.sh          slackware-
set_ugid_quota.sh
debian-del_ip.sh        redhat-add_ip.sh.orig     suse-7.x_add_ip.sh
debian-set_hostname.sh  redhat-del_ip.sh          suse-8.x_add_ip.sh
etcnet-add_ip.sh        redhat-set_hostname.sh    suse-8.x_del_ip.sh
etcnet-del_ip.sh        set_dns.sh                suse-add_ip.sh
functions               set_ugid_quota.sh         suse-del_ip.sh
gentoo-add_ip.sh        set_userpass.sh           suse-set_hostname.sh
gentoo-del_ip.sh        slackware-9.x_add_ip.sh
[jleggett@lxp6d15m3 scripts]$ pwd
/etc/vz/dists/scripts
[jleggett@lxp6d15m3 scripts]$


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Luke Kanies

2008-Jul-01 18:48 UTC

head link

[Puppet Users] Re: OpenVZ configuration of networking with puppet - big crash

On Jul 1, 2008, at 1:15 PM, Jeff Leggett wrote:
> Warning: cannot open /proc/net/dev (No such file or directory).
> Limited output.
> Could not load /usr/lib/ruby/site_ruby/1.8/facter/processor.rb: No
> such file or directory - /proc/cpuinfo
> dnsdomainname: Host name lookup failure
> /usr/lib/ruby/site_ruby/1.8/facter/memory.rb:26:in `readlines'': No
> such file or directory - /proc/meminfo (Errno::ENOENT)
>        from /usr/lib/ruby/site_ruby/1.8/facter/memory.rb:26:in
> `meminfo_number''
>        from /usr/lib/ruby/1.8/thread.rb:33:in `exclusive''
>        from /usr/lib/ruby/site_ruby/1.8/facter/memory.rb:24:in
> `meminfo_number''
>        from /usr/lib/ruby/site_ruby/1.8/facter/memory.rb:65
>        from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `call''
>        from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `value''
>        from /usr/lib/ruby/site_ruby/1.8/facter.rb:355:in `value''
>        from /usr/lib/ruby/site_ruby/1.8/facter.rb:352:in `each''
>         ... 6 levels...
>        from /usr/lib/ruby/site_ruby/1.8/puppet/indirector/facts/
> facter.rb:60:in `find''
>        from /usr/lib/ruby/site_ruby/1.8/puppet/indirector/
> indirection.rb:170:in `find''
>        from /usr/lib/ruby/site_ruby/1.8/puppet/indirector.rb:42:in
> `find''
>        from /usr/bin/puppet:185
> [root@localhost /]#

These are facter errors.  What does facter say when you run it?

-- 
I object to doing things that computers can do. --Olin Shivers
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Jeff Leggett

2008-Jul-01 19:32 UTC

head link

[Puppet Users] Re: OpenVZ configuration of networking with puppet - big crash

[root@localhost tmp]# facter
/usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
writable dir /tmp/, mode 041777
/usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
writable dir /tmp/, mode 041777
/usr/lib/ruby/site_ruby/1.8/facter/ipmess.rb:22: warning: Insecure
world writable dir /tmp/, mode 041777
/usr/lib/ruby/site_ruby/1.8/facter/ipmess.rb:25: warning: Insecure
world writable dir /tmp/, mode 041777
/usr/lib/ruby/site_ruby/1.8/facter/ipmess.rb:25: warning: Insecure
world writable dir /tmp/, mode 041777
/usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
writable dir /tmp/, mode 041777
/usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
writable dir /tmp/, mode 041777
/usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
writable dir /tmp/, mode 041777
/usr/lib/ruby/site_ruby/1.8/facter.rb:929: warning: Insecure world
writable dir /tmp/, mode 041777
/usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
writable dir /tmp/, mode 041777
/usr/lib/ruby/site_ruby/1.8/facter.rb:972: warning: Insecure world
writable dir /tmp/, mode 041777
/usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
writable dir /tmp/, mode 041777
architecture => i386
domain => localdomain
facterversion => 1.3.8
fqdn => localhost.localdomain
hardwareisa => athlon
hardwaremodel => i686
hostname => localhost
id => root
ipaddress => 192.168.0.3
kernel => Linux
kernelrelease => 2.6.18-53.1.19.el5.028stab053.14
lsbdistcodename => Tikanga
lsbdistdescription => Red Hat Enterprise Linux Server release 5.1
(Tikanga)
lsbdistid => RedHatEnterpriseServer
lsbdistrelease => 5.1
lsbrelease => :core-3.1-ia32:core-3.1-noarch:graphics-3.1-
ia32:graphics-3.1-noarch
memoryfree => 247.26 MB
memorysize => 256.00 MB
operatingsystem => RedHat
operatingsystemrelease => 5
processor0 => AMD Athlon(tm) 64 X2 Dual Core Processor 4800+
processor1 => AMD Athlon(tm) 64 X2 Dual Core Processor 4800+
processorcount => 2
ps => ps -ef
puppetversion => 0.24.4
rubysitedir => /usr/lib/ruby/site_ruby/1.8
rubyversion => 1.8.5
sshdsakey => AAAAB3NzaC1kc3MAAACBAOSp1uqyShTWwZkZ5Ru4hiWOZQy/
tNISOj6JQjl6WQ8qP6CzfTR+ycFEWkwUO7dX6xgFnMSf
+rpafipP30R1hhXbDUVEozVs36QZ7PuuqUnKabkMxZHeaRF8xCbk6Rq6e5LXhAT4K4zibsVFpO1uyvSgBzcBi/
w6kbP
+LTp2p6DjAAAAFQCuesJsRsekNp50u7ecU9Hg78UNeQAAAIBccgW6UfOfFjhNX7Hu3qHqIz0ViVHHNjhOhoZhJVu15o
++GbCkdKt7mfeSQIZljkvLHfM0MU4wMsJxJ7DcXcx9/dwRsXrQ/
0zJDM6nX4ZxOqfblQEZsRFZ6htOjrsJFHU9zaEHHT6LW40RnKFfwm6e18Arhzh/
FTFNIvYqkArzOgAAAIBa4NvI4qy4lmtZLYhaIjA8axcPTl85EUgBgl3GxUXr2oB9/oL
+VJLe8PoHgHWAaiDGAFyAuUbNlsdWvy96UgApzmdkPzPS9FrNAKGH+wn8CxQdfTHIx/SA
+fJaAc9I8FFBPso5O4Nw6ikzPM+0L3axcOiAldjNRT4JrSwt6N4lXg=sshrsakey =>
AAAAB3NzaC1yc2EAAAABIwAAAQEAllaO37QUe7uhm+PL1GulPGsd0fp/
iNgsmfs8JlnJGdZCIFpMHdALKnIpHCnkiuzQx6MO5c
+ltw9i7+auYzDB85IEYkkKPuSVrJ0OvkfyD3upk3TCkNBqQ41QVV8JgbecNsI7xPMlDtNg63J
+S6zpmxsMGdFPa8rc0WhRY08b/z6+gXxLcCJIp/
H3+9EjFOkm3gKbFDaO5I0GdPEGfRrGRkwPMIs9Fqh6VHSRHcujMC/mvbF9Q4+voDZzQ
+fyFVIpV2WopxZL1xKZhV02qzVNIeKqU7IQx5rmimp+tf4BI/DV3ihN18k0j+OaAaTLH1K/
fP6IqjXuim3GN4AiwPZquw=swapfree => 0.00 kB
swapsize => 0.00 kB
uniqueid => 007f0100
[root@localhost tmp]#

Never seen that world-writeable error before.

On Jul 1, 2:48 pm, Luke Kanies <l...@madstop.com>
wrote:> On Jul 1, 2008, at 1:15 PM, Jeff Leggett wrote:
>
>
>
> > Warning: cannot open /proc/net/dev (No such file or directory).
> > Limited output.
> > Could not load /usr/lib/ruby/site_ruby/1.8/facter/processor.rb: No
> > such file or directory - /proc/cpuinfo
> > dnsdomainname: Host name lookup failure
> > /usr/lib/ruby/site_ruby/1.8/facter/memory.rb:26:in
`readlines'': No
> > such file or directory - /proc/meminfo (Errno::ENOENT)
> >        from /usr/lib/ruby/site_ruby/1.8/facter/memory.rb:26:in
> > `meminfo_number''
> >        from /usr/lib/ruby/1.8/thread.rb:33:in `exclusive''
> >        from /usr/lib/ruby/site_ruby/1.8/facter/memory.rb:24:in
> > `meminfo_number''
> >        from /usr/lib/ruby/site_ruby/1.8/facter/memory.rb:65
> >        from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in
`call''
> >        from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in
`value''
> >        from /usr/lib/ruby/site_ruby/1.8/facter.rb:355:in
`value''
> >        from /usr/lib/ruby/site_ruby/1.8/facter.rb:352:in
`each''
> >         ... 6 levels...
> >        from /usr/lib/ruby/site_ruby/1.8/puppet/indirector/facts/
> > facter.rb:60:in `find''
> >        from /usr/lib/ruby/site_ruby/1.8/puppet/indirector/
> > indirection.rb:170:in `find''
> >        from /usr/lib/ruby/site_ruby/1.8/puppet/indirector.rb:42:in
> > `find''
> >        from /usr/bin/puppet:185
> > [root@localhost /]#
>
> These are facter errors.  What does facter say when you run it?
>
> --
> I object to doing things that computers can do. --Olin Shivers
> ---------------------------------------------------------------------
> Luke Kanies |http://reductivelabs.com|http://madstop.com--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Luke Kanies

2008-Jul-01 19:40 UTC

head link

[Puppet Users] Re: OpenVZ configuration of networking with puppet - big crash

On Jul 1, 2008, at 2:32 PM, Jeff Leggett wrote:> /usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
> writable dir /tmp/, mode 041777
[...]>
> memoryfree => 247.26 MB
> memorysize => 256.00 MB
> operatingsystem => RedHat[...]

So it works fine on its own but not when running as part of Puppet?   
That''s, um, unreasonable.

I''ve seen the warning, but it''s not produced by Facter, IIRC.

-- 
Somebody has to do something, and it''s just incredibly pathetic that it
has to be us. --Jerry Garcia
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Jeff Leggett

2008-Jul-01 20:10 UTC

head link

[Puppet Users] Re: OpenVZ configuration of networking with puppet - big crash

I am sorry Luke, I am not clear on your response - is there anything I
am doing wrong?  Or are you researching?  have I found a possible
bug?

This is interesting... if I start the VE, then enter it and run the
script internally, it *seems* to work:

[root@localhost jleggett]# service network stop
Shutting down interface venet0:                            [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Disabling IPv4 packet forwarding:  net.ipv4.ip_forward = 0
                                                           [  OK  ]
[root@localhost jleggett]# bash redhat-add_ip.sh
+ LOGFILE=/tmp/add_ip-dbug.log
+ exec
[root@localhost jleggett]# service network status
Configured devices:
lo venet0
Currently active devices:
lo venet0
[root@localhost jleggett]# ping www.yahoo.com
PING www.yahoo-ht3.akadns.net (69.147.76.15) 56(84) bytes of data.
64 bytes from f1.www.vip.re1.yahoo.com (69.147.76.15): icmp_seq=1
ttl=56 time=18.1 ms
64 bytes from f1.www.vip.re1.yahoo.com (69.147.76.15): icmp_seq=2
ttl=56 time=18.1 ms

--- www.yahoo-ht3.akadns.net ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 18.100/18.144/18.188/0.044 ms
[root@localhost jleggett]#

HOWEVER, I was expecting to see puppet output for the resource types I
modify in the script.  BUt I see no output from puppet on either
STDOUT or in the redirected STDERR, STDOUT log file:

[root@localhost tmp]# cat add_ip-dbug.log
+ FACTER_IP_ADDR+ FACTER_VENET_DEV=venet0
+ FACTER_VENET_DEV_CFG=ifcfg-venet0
+ FACTER_IFNUM+ echo ''Running puppet-ized version of
redhat-add_ip.sh''
Running puppet-ized version of redhat-add_ip.sh
+ /bin/cat
+ /usr/bin/puppet
[root@localhost tmp]#


On Jul 1, 3:40 pm, Luke Kanies <l...@madstop.com>
wrote:> On Jul 1, 2008, at 2:32 PM, Jeff Leggett wrote:>
/usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world
> > writable dir /tmp/, mode 041777
> [...]
>
> > memoryfree => 247.26 MB
> > memorysize => 256.00 MB
> > operatingsystem => RedHat
>
> [...]
>
> So it works fine on its own but not when running as part of Puppet?
> That''s, um, unreasonable.
>
> I''ve seen the warning, but it''s not produced by Facter,
IIRC.
>
> --
> Somebody has to do something, and it''s just incredibly pathetic
that it
> has to be us. --Jerry Garcia
> ---------------------------------------------------------------------
> Luke Kanies |http://reductivelabs.com|http://madstop.com--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Marcin Owsiany

2008-Jul-02 18:36 UTC

head link

[Puppet Users] Re: OpenVZ configuration of networking with puppet - big crash

On Tue, Jul 01, 2008 at 11:15:41AM -0700, Jeff Leggett
wrote:> [jleggett@lxp6d15m3 scripts]$ cat redhat-add_ip.sh
My theory is that you get errors about files in /proc being unavailable
because when vzctl runs your "add_ip" script, the /proc filesystem is
not mounted yet in the VE.

Incidentally, for the last few weeks I''ve actually been investigating
closely how and when those event scripts get run, for another reason.
What I can say at this point is that the documentation on these scripts
is very scarce and inaccurate. However as far as I can tell, at least in
some cases these scripts get run before init is started in the
VE/container.

regards,
-- 
Marcin Owsiany <marcin@owsiany.pl>              http://marcin.owsiany.pl/
GnuPG: 1024D/60F41216  FE67 DA2D 0ACA FC5E 3F75  D6F6 3A0D 8AA0 60F4 1216
 
"Every program in development at MIT expands until it can read mail."
                                                              -- Unknown

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Luke Kanies

2008-Jul-03 04:13 UTC

head link

[Puppet Users] Re: OpenVZ configuration of networking with puppet - big crash

On Jul 1, 2008, at 3:10 PM, Jeff Leggett wrote:
>
> I am sorry Luke, I am not clear on your response - is there anything I
> am doing wrong?  Or are you researching?  have I found a possible
> bug?
I''m trying to figure out what the problem is.  It seems to be a Facter
issue, not a Puppet issue (even if it only shows up when Facter is  
used with Puppet).

Are you using any custom facts?  Maybe they''re breaking Facter somehow.

I don''t even know where the failure is, so it''s hard to know
if this
is a bug.  Given that it works in most circumstances, it seems to be  
an issue with your environment.

-- 
The truth is that there is nothing noble in being superior to somebody
else. The only real nobility is in being superior to your former self.
     -- Whitney Young
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reasonably Related Threads

Search for more seemingly similar threads

Puppet users - Jul 2008 - OpenVZ configuration of networking with puppet - big crash

[Puppet Users] OpenVZ configuration of networking with puppet - big crash

[Puppet Users] Re: OpenVZ configuration of networking with puppet - big crash

[Puppet Users] Re: OpenVZ configuration of networking with puppet - big crash

[Puppet Users] Re: OpenVZ configuration of networking with puppet - big crash

[Puppet Users] Re: OpenVZ configuration of networking with puppet - big crash

[Puppet Users] Re: OpenVZ configuration of networking with puppet - big crash

[Puppet Users] Re: OpenVZ configuration of networking with puppet - big crash

Reasonably Related Threads