I''m having some problems getting puppet to mount NFS exports, and
before I file a bug report, I figured I''d check here to see if anyone
else has run into similar difficulties.
Here''s the relevant portion of my config file:
class base {
# Set up the NFS mount
file { "/mnt/point/here":
ensure => directory,
}
mount {
"/mnt/point/here":
require => File["/mnt/point/here"],
device => "device:/nfs/export",
ensure => mounted,
fstype => nfs,
options => ''defaults'',
atboot => true
}
}
The above code gives this message:
Could not set mounted on ensure: Field ''options'' is required
at /etc/
puppet/manifests/classes/base.pp:20
Clearly, the options field is there, so I''m a little confused by the
above message. Interestingly, when I run the puppet client on a
separate host, the behavior is as expected:
Jul 22 07:53:48 otherhost puppetd[26298]: Starting Puppet client
version 0.24.4
Jul 22 07:53:52 otherhost puppetd[26298]: Starting catalog run
Jul 22 07:53:55 otherhost puppetd[26298]: (//Node[default]/base/Mount[/
mnt/point/here]/ensure) ensure changed ''present'' to
''mounted''
Jul 22 07:53:55 otherhost puppetd[26298]: (//Node[default]/base/Mount[/
mnt/point/here]) Refreshing self
Jul 22 07:53:58 otherhost puppetd[26298]: Finished catalog run in 6.28
seconds
Here''s the log entry from the non-working host in context (the non-
working host is also the puppetmaster server, hence the message from
puppetmasterd mixed in):
Jul 22 01:01:44 host puppetd[19474]: Starting Puppet client version
0.24.4
Jul 22 01:01:47 host puppetmasterd[17374]: Compiled configuration for
host.xyz.com in 1.79 seconds
Jul 22 01:01:48 host puppetd[19474]: Starting catalog run
Jul 22 01:01:52 host puppetd[19474]: (//Node[default]/base/Mount[/mnt/
point/here]/ensure) change from absent to mounted failed: Could not
set mounted on ensure: Field ''options'' is required at
/etc/puppet/
manifests/classes/base.pp:20
Jul 22 01:01:52 host puppetd[19474]: Got an uncaught exception of type
ArgumentError: Field ''options'' is required
Jul 22 01:01:52 host puppetd[19474]: Finished catalog run in 3.63
seconds
Both machines are running CentOS 5.2 with the EPEL RPM version of
puppet, version 0.24.4.
[host] $ rpm -qa | grep puppet
puppet-server-0.24.4-1.el5
puppet-0.24.4-1.el5
[host] $ uname -a
Linux host.xyz.com 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:49:24 EDT
2008 i686 i686 i386 GNU/Linux
[otherhost] $ rpm -qa | grep puppet
puppet-0.24.4-1.el5
[otherhost] $ uname -a
Linux otherhost.xyz.com 2.6.18-92.el5 #1 SMP Tue Jun 10 18:49:47 EDT
2008 i686 i686 i386 GNU/Linux
Is there anything about the puppet client running on the same machine
as the postmaster that could be causing this? Or is there something
else that I''m missing? I did just notice that the ruby packages on the
two machines are different versions, so I''m also wondering if that has
something to do with it.
On host: ruby-1.8.5-5.el5_2.3
On otherhost: ruby-1.8.5-5.el5_1.1
I''m going to patch the ruby version on otherhost. If it breaks it,
then at least I''ve found the source of the problem. :|
Thanks in advance for any other help.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
On Jul 22, 8:07 am, threetee <three...@gmail.com> wrote:> else that I''m missing? I did just notice that the ruby packages on the > two machines are different versions, so I''m also wondering if that has > something to do with it. > > On host: ruby-1.8.5-5.el5_2.3 > On otherhost: ruby-1.8.5-5.el5_1.1 > > I''m going to patch the ruby version on otherhost. If it breaks it, > then at least I''ve found the source of the problem. :|Ruby RPMs are now identical between the two machines, and the behavior is still the same. I don''t think it''s related to the version of ruby. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
I just want to check one thing, which is ''have you restarted puppetmasterd''? Sometimes it gets itself into a state where it won''t see things that are clearly there, and it''s related to it dropping resources when it comes across a syntax error. Before you spend a long time debugging, give it a quick restart just to ensure it''s not that. On Tue, Jul 22, 2008 at 11:07 AM, threetee <threetee@gmail.com> wrote:> > I''m having some problems getting puppet to mount NFS exports, and > before I file a bug report, I figured I''d check here to see if anyone > else has run into similar difficulties. > > Here''s the relevant portion of my config file: > > class base { > # Set up the NFS mount > file { "/mnt/point/here": > ensure => directory, > } > mount { > "/mnt/point/here": > require => File["/mnt/point/here"], > device => "device:/nfs/export", > ensure => mounted, > fstype => nfs, > options => ''defaults'', > atboot => true > } > } > > The above code gives this message: > Could not set mounted on ensure: Field ''options'' is required at /etc/ > puppet/manifests/classes/base.pp:20 > > Clearly, the options field is there, so I''m a little confused by the > above message. Interestingly, when I run the puppet client on a > separate host, the behavior is as expected: > Jul 22 07:53:48 otherhost puppetd[26298]: Starting Puppet client > version 0.24.4 > Jul 22 07:53:52 otherhost puppetd[26298]: Starting catalog run > Jul 22 07:53:55 otherhost puppetd[26298]: (//Node[default]/base/Mount[/ > mnt/point/here]/ensure) ensure changed ''present'' to ''mounted'' > Jul 22 07:53:55 otherhost puppetd[26298]: (//Node[default]/base/Mount[/ > mnt/point/here]) Refreshing self > Jul 22 07:53:58 otherhost puppetd[26298]: Finished catalog run in 6.28 > seconds > > > Here''s the log entry from the non-working host in context (the non- > working host is also the puppetmaster server, hence the message from > puppetmasterd mixed in): > > Jul 22 01:01:44 host puppetd[19474]: Starting Puppet client version > 0.24.4 > Jul 22 01:01:47 host puppetmasterd[17374]: Compiled configuration for > host.xyz.com in 1.79 seconds > Jul 22 01:01:48 host puppetd[19474]: Starting catalog run > Jul 22 01:01:52 host puppetd[19474]: (//Node[default]/base/Mount[/mnt/ > point/here]/ensure) change from absent to mounted failed: Could not > set mounted on ensure: Field ''options'' is required at /etc/puppet/ > manifests/classes/base.pp:20 > Jul 22 01:01:52 host puppetd[19474]: Got an uncaught exception of type > ArgumentError: Field ''options'' is required > Jul 22 01:01:52 host puppetd[19474]: Finished catalog run in 3.63 > seconds > > Both machines are running CentOS 5.2 with the EPEL RPM version of > puppet, version 0.24.4. > [host] $ rpm -qa | grep puppet > puppet-server-0.24.4-1.el5 > puppet-0.24.4-1.el5 > [host] $ uname -a > Linux host.xyz.com 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:49:24 EDT > 2008 i686 i686 i386 GNU/Linux > > [otherhost] $ rpm -qa | grep puppet > puppet-0.24.4-1.el5 > [otherhost] $ uname -a > Linux otherhost.xyz.com 2.6.18-92.el5 #1 SMP Tue Jun 10 18:49:47 EDT > 2008 i686 i686 i386 GNU/Linux > > Is there anything about the puppet client running on the same machine > as the postmaster that could be causing this? Or is there something > else that I''m missing? I did just notice that the ruby packages on the > two machines are different versions, so I''m also wondering if that has > something to do with it. > > On host: ruby-1.8.5-5.el5_2.3 > On otherhost: ruby-1.8.5-5.el5_1.1 > > I''m going to patch the ruby version on otherhost. If it breaks it, > then at least I''ve found the source of the problem. :| > > Thanks in advance for any other help. > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Yes, I''ve run into other problems that went away after a puppetmaster restart. However, in this case, a restart doesn''t change the behavior. On Jul 22, 10:57 am, "Ashley Penney" <apen...@gmail.com> wrote:> I just want to check one thing, which is ''have you restarted > puppetmasterd''? Sometimes it gets itself into a state where it won''t see > things that are clearly there, and it''s related to it dropping resources > when it comes across a syntax error. Before you spend a long time > debugging, give it a quick restart just to ensure it''s not that. > > On Tue, Jul 22, 2008 at 11:07 AM, threetee <three...@gmail.com> wrote: > > > I''m having some problems getting puppet to mount NFS exports, and > > before I file a bug report, I figured I''d check here to see if anyone > > else has run into similar difficulties. > > > Here''s the relevant portion of my config file: > > > class base { > > # Set up the NFS mount > > file { "/mnt/point/here": > > ensure => directory, > > } > > mount { > > "/mnt/point/here": > > require => File["/mnt/point/here"], > > device => "device:/nfs/export", > > ensure => mounted, > > fstype => nfs, > > options => ''defaults'', > > atboot => true > > } > > } > > > The above code gives this message: > > Could not set mounted on ensure: Field ''options'' is required at /etc/ > > puppet/manifests/classes/base.pp:20 > > > Clearly, the options field is there, so I''m a little confused by the > > above message. Interestingly, when I run the puppet client on a > > separate host, the behavior is as expected: > > Jul 22 07:53:48 otherhost puppetd[26298]: Starting Puppet client > > version 0.24.4 > > Jul 22 07:53:52 otherhost puppetd[26298]: Starting catalog run > > Jul 22 07:53:55 otherhost puppetd[26298]: (//Node[default]/base/Mount[/ > > mnt/point/here]/ensure) ensure changed ''present'' to ''mounted'' > > Jul 22 07:53:55 otherhost puppetd[26298]: (//Node[default]/base/Mount[/ > > mnt/point/here]) Refreshing self > > Jul 22 07:53:58 otherhost puppetd[26298]: Finished catalog run in 6.28 > > seconds > > > Here''s the log entry from the non-working host in context (the non- > > working host is also the puppetmaster server, hence the message from > > puppetmasterd mixed in): > > > Jul 22 01:01:44 host puppetd[19474]: Starting Puppet client version > > 0.24.4 > > Jul 22 01:01:47 host puppetmasterd[17374]: Compiled configuration for > > host.xyz.com in 1.79 seconds > > Jul 22 01:01:48 host puppetd[19474]: Starting catalog run > > Jul 22 01:01:52 host puppetd[19474]: (//Node[default]/base/Mount[/mnt/ > > point/here]/ensure) change from absent to mounted failed: Could not > > set mounted on ensure: Field ''options'' is required at /etc/puppet/ > > manifests/classes/base.pp:20 > > Jul 22 01:01:52 host puppetd[19474]: Got an uncaught exception of type > > ArgumentError: Field ''options'' is required > > Jul 22 01:01:52 host puppetd[19474]: Finished catalog run in 3.63 > > seconds > > > Both machines are running CentOS 5.2 with the EPEL RPM version of > > puppet, version 0.24.4. > > [host] $ rpm -qa | grep puppet > > puppet-server-0.24.4-1.el5 > > puppet-0.24.4-1.el5 > > [host] $ uname -a > > Linux host.xyz.com 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:49:24 EDT > > 2008 i686 i686 i386 GNU/Linux > > > [otherhost] $ rpm -qa | grep puppet > > puppet-0.24.4-1.el5 > > [otherhost] $ uname -a > > Linux otherhost.xyz.com 2.6.18-92.el5 #1 SMP Tue Jun 10 18:49:47 EDT > > 2008 i686 i686 i386 GNU/Linux > > > Is there anything about the puppet client running on the same machine > > as the postmaster that could be causing this? Or is there something > > else that I''m missing? I did just notice that the ruby packages on the > > two machines are different versions, so I''m also wondering if that has > > something to do with it. > > > On host: ruby-1.8.5-5.el5_2.3 > > On otherhost: ruby-1.8.5-5.el5_1.1 > > > I''m going to patch the ruby version on otherhost. If it breaks it, > > then at least I''ve found the source of the problem. :| > > > Thanks in advance for any other help. > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Sounds like nobody else has any input. I''ll file a bug report. On Jul 22, 5:24 pm, threetee <three...@gmail.com> wrote:> Yes, I''ve run into other problems that went away after a puppetmaster > restart. However, in this case, a restart doesn''t change the behavior. > > On Jul 22, 10:57 am, "Ashley Penney" <apen...@gmail.com> wrote: > > > I just want to check one thing, which is ''have you restarted > > puppetmasterd''? Sometimes it gets itself into a state where it won''t see > > things that are clearly there, and it''s related to it dropping resources > > when it comes across a syntax error. Before you spend a long time > > debugging, give it a quick restart just to ensure it''s not that. > > > On Tue, Jul 22, 2008 at 11:07 AM, threetee <three...@gmail.com> wrote: > > > > I''m having some problems getting puppet to mount NFS exports, and > > > before I file a bug report, I figured I''d check here to see if anyone > > > else has run into similar difficulties. > > > > Here''s the relevant portion of my config file: > > > > class base { > > > # Set up the NFS mount > > > file { "/mnt/point/here": > > > ensure => directory, > > > } > > > mount { > > > "/mnt/point/here": > > > require => File["/mnt/point/here"], > > > device => "device:/nfs/export", > > > ensure => mounted, > > > fstype => nfs, > > > options => ''defaults'', > > > atboot => true > > > } > > > } > > > > The above code gives this message: > > > Could not set mounted on ensure: Field ''options'' is required at /etc/ > > > puppet/manifests/classes/base.pp:20 > > > > Clearly, the options field is there, so I''m a little confused by the > > > above message. Interestingly, when I run the puppet client on a > > > separate host, the behavior is as expected: > > > Jul 22 07:53:48 otherhost puppetd[26298]: Starting Puppet client > > > version 0.24.4 > > > Jul 22 07:53:52 otherhost puppetd[26298]: Starting catalog run > > > Jul 22 07:53:55 otherhost puppetd[26298]: (//Node[default]/base/Mount[/ > > > mnt/point/here]/ensure) ensure changed ''present'' to ''mounted'' > > > Jul 22 07:53:55 otherhost puppetd[26298]: (//Node[default]/base/Mount[/ > > > mnt/point/here]) Refreshing self > > > Jul 22 07:53:58 otherhost puppetd[26298]: Finished catalog run in 6.28 > > > seconds > > > > Here''s the log entry from the non-working host in context (the non- > > > working host is also the puppetmaster server, hence the message from > > > puppetmasterd mixed in): > > > > Jul 22 01:01:44 host puppetd[19474]: Starting Puppet client version > > > 0.24.4 > > > Jul 22 01:01:47 host puppetmasterd[17374]: Compiled configuration for > > > host.xyz.com in 1.79 seconds > > > Jul 22 01:01:48 host puppetd[19474]: Starting catalog run > > > Jul 22 01:01:52 host puppetd[19474]: (//Node[default]/base/Mount[/mnt/ > > > point/here]/ensure) change from absent to mounted failed: Could not > > > set mounted on ensure: Field ''options'' is required at /etc/puppet/ > > > manifests/classes/base.pp:20 > > > Jul 22 01:01:52 host puppetd[19474]: Got an uncaught exception of type > > > ArgumentError: Field ''options'' is required > > > Jul 22 01:01:52 host puppetd[19474]: Finished catalog run in 3.63 > > > seconds > > > > Both machines are running CentOS 5.2 with the EPEL RPM version of > > > puppet, version 0.24.4. > > > [host] $ rpm -qa | grep puppet > > > puppet-server-0.24.4-1.el5 > > > puppet-0.24.4-1.el5 > > > [host] $ uname -a > > > Linux host.xyz.com 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:49:24 EDT > > > 2008 i686 i686 i386 GNU/Linux > > > > [otherhost] $ rpm -qa | grep puppet > > > puppet-0.24.4-1.el5 > > > [otherhost] $ uname -a > > > Linux otherhost.xyz.com 2.6.18-92.el5 #1 SMP Tue Jun 10 18:49:47 EDT > > > 2008 i686 i686 i386 GNU/Linux > > > > Is there anything about the puppet client running on the same machine > > > as the postmaster that could be causing this? Or is there something > > > else that I''m missing? I did just notice that the ruby packages on the > > > two machines are different versions, so I''m also wondering if that has > > > something to do with it. > > > > On host: ruby-1.8.5-5.el5_2.3 > > > On otherhost: ruby-1.8.5-5.el5_1.1 > > > > I''m going to patch the ruby version on otherhost. If it breaks it, > > > then at least I''ve found the source of the problem. :| > > > > Thanks in advance for any other help. > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---