Hi, I was hoping someone could shed some light on an issue that just came up for us. We are trying to migrate puppet from our Dev environment, which was running puppet 22.4 to a production system running 24.4. On our dev box, we had set up a staging area, where we would create manifests, and run syntax checking against them, using puppet --noop <node>.pp then once that passed, we would copy them to the /etc/puppet/manifests/ nodes directory, and run them. When we try to recreate this behavior on the sew server, we get this area when we run puppet --noop <node>.pp in staging : Could not find default node or by name with ''<localhostname>, <fully.qualified.domain.name>'' on node <localhostname> However, if I manually copy the node.pp file to /etc/puppet/manifests/ nodes/ and run puppet --noop it checks the syntax as appropriate. Was there some sort of behavior changed in /usr/bin/puppet that we need to take into account? If we could get our "staging" are a working again that would be awesome, as it was really useful! Thanks! Alaric --~--~---------~--~----~------------~-------~--~----~ 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 folks, I don''t mean to be a bother, but has anyone seen anything similar to what I''ve described? Could provide more information that might be helpful? I''d really like to have puppet up and running in production, and this is sort of stalling us out... We would really like to be able to test the language of a manifest before moving it into /etc/ puppet/manifests I''d be grateful for any assistance! Thanks -Alaric On Apr 17, 3:25 pm, alaric <paxindust...@gmail.com> wrote:> Hi, > > I was hoping someone could shed some light on an issue that just came > up for us. > > We are trying to migrate puppet from our Dev environment, which was > running puppet 22.4 to a production system running 24.4. On our dev > box, we had set up a staging area, where we would create manifests, > and run syntax checking against them, using puppet --noop <node>.pp > then once that passed, we would copy them to the /etc/puppet/manifests/ > nodes directory, and run them. When we try to recreate this behavior > on the sew server, we get this area when we run puppet --noop > <node>.pp in staging : > > Could not find default node or by name with ''<localhostname>, > <fully.qualified.domain.name>'' on node <localhostname> > > However, if I manually copy the node.pp file to /etc/puppet/manifests/ > nodes/ and run puppet --noop it checks the syntax as appropriate. > > Was there some sort of behavior changed in /usr/bin/puppet that we > need to take into account? If we could get our "staging" are a > working again that would be awesome, as it was really useful! > > Thanks! > > Alaric--~--~---------~--~----~------------~-------~--~----~ 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 think you re looking for --parseonly On Thu, Apr 24, 2008 at 9:24 AM, alaric <paxindustria@gmail.com> wrote:> > I folks, > > I don''t mean to be a bother, but has anyone seen anything similar to > what I''ve described? Could provide more information that might be > helpful? I''d really like to have puppet up and running in production, > and this is sort of stalling us out... We would really like to be > able to test the language of a manifest before moving it into /etc/ > puppet/manifests > > I''d be grateful for any assistance! > Thanks > > -Alaric > > > > > On Apr 17, 3:25 pm, alaric <paxindust...@gmail.com> wrote: > > Hi, > > > > I was hoping someone could shed some light on an issue that just came > > up for us. > > > > We are trying to migrate puppet from our Dev environment, which was > > running puppet 22.4 to a production system running 24.4. On our dev > > box, we had set up a staging area, where we would create manifests, > > and run syntax checking against them, using puppet --noop <node>.pp > > then once that passed, we would copy them to the /etc/puppet/manifests/ > > nodes directory, and run them. When we try to recreate this behavior > > on the sew server, we get this area when we run puppet --noop > > <node>.pp in staging : > > > > Could not find default node or by name with ''<localhostname>, > > <fully.qualified.domain.name>'' on node <localhostname> > > > > However, if I manually copy the node.pp file to /etc/puppet/manifests/ > > nodes/ and run puppet --noop it checks the syntax as appropriate. > > > > Was there some sort of behavior changed in /usr/bin/puppet that we > > need to take into account? If we could get our "staging" are a > > working again that would be awesome, as it was really useful! > > > > Thanks! > > > > Alaric > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Paul, Thanks for the help! I think that will lead us to where we want to go! -Alaric On Thu, Apr 24, 2008 at 1:04 PM, Paul Lathrop <paul@tertiusfamily.net> wrote:> > I think you re looking for --parseonly > > On Thu, Apr 24, 2008 at 9:24 AM, alaric <paxindustria@gmail.com> wrote: > > > > I folks, > > > > I don''t mean to be a bother, but has anyone seen anything similar to > > what I''ve described? Could provide more information that might be > > helpful? I''d really like to have puppet up and running in production, > > and this is sort of stalling us out... We would really like to be > > able to test the language of a manifest before moving it into /etc/ > > puppet/manifests > > > > I''d be grateful for any assistance! > > Thanks > > > > -Alaric > > > > > > > > > > On Apr 17, 3:25 pm, alaric <paxindust...@gmail.com> wrote: > > > Hi, > > > > > > I was hoping someone could shed some light on an issue that just came > > > up for us. > > > > > > We are trying to migrate puppet from our Dev environment, which was > > > running puppet 22.4 to a production system running 24.4. On our dev > > > box, we had set up a staging area, where we would create manifests, > > > and run syntax checking against them, using puppet --noop <node>.pp > > > then once that passed, we would copy them to the > /etc/puppet/manifests/ > > > nodes directory, and run them. When we try to recreate this behavior > > > on the sew server, we get this area when we run puppet --noop > > > <node>.pp in staging : > > > > > > Could not find default node or by name with ''<localhostname>, > > > <fully.qualified.domain.name>'' on node <localhostname> > > > > > > However, if I manually copy the node.pp file to /etc/puppet/manifests/ > > > nodes/ and run puppet --noop it checks the syntax as appropriate. > > > > > > Was there some sort of behavior changed in /usr/bin/puppet that we > > > need to take into account? If we could get our "staging" are a > > > working again that would be awesome, as it was really useful! > > > > > > Thanks! > > > > > > Alaric > > > > > > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---