What is puppet doing here?
Nov 17 00:02:01 gumby yum: Installed: tf-starterkit-tfel0-1.0-1.tf.noarch
Nov 17 00:02:01 gumby puppetd[720]:
(//Node[gumby.fr.xxx.com]/Starterkit::Setup[tfel0]/Package[tf-starterkit-tfel0]/ensure)
created
Nov 17 00:02:07 gumby yum: Installed: tf-jboss-server-4.2.3.GA-1.tf.noarch
Nov 17 00:02:07 gumby puppetd[720]:
(//Node[app_node]/jboss::server/Package[tf-jboss-server]/ensure)
created
Nov 17 00:02:07 gumby puppetd[720]:
(//Node[app_node]/jboss::server/File[/opt/jboss/current]) Recursively
backing up to filebucket
Nov 17 00:02:43 gumby puppetd[720]:
(//Node[app_node]/jboss::server/File[/opt/jboss/current]) Filebucketed
/opt/jboss/current/server/tfel0/deploy/eazye.ear to main with sum 703
b44a0459ed5f1569c0096ab435ea0
Nov 17 00:02:43 gumby puppetd[720]:
(//Node[app_node]/jboss::server/File[/opt/jboss/current]) Not removing
directory; use ''force'' to override
Nov 17 00:02:43 gumby puppetd[720]:
(//Node[app_node]/jboss::server/File[/opt/jboss/current]) Recursively
backing up to filebucket
Nov 17 00:03:18 gumby puppetd[720]:
(//Node[app_node]/jboss::server/File[/opt/jboss/current]) Filebucketed
/opt/jboss/current/server/tfel0/deploy/eazye.ear to main with sum 703
b44a0459ed5f1569c0096ab435ea0
Nov 17 00:03:18 gumby puppetd[720]:
(//Node[app_node]/jboss::server/File[/opt/jboss/current]) Not removing
directory; use ''force'' to override
Nov 17 00:03:18 gumby puppetd[720]:
(//Node[app_node]/jboss::server/File[/opt/jboss/current]/ensure)
change from directory to link failed: Could not remove existing file
Why is it trying to remove a directory? (Which directory?). I didn''t
tell it to do that in the manifest. I do have this..
file {
"/opt/jboss/current":
links => manage,
ensure => "/opt/jboss/jboss-${jboss_version}",
require => Package["tf-jboss-server"];
}
that should create a symlink. Puppet seems to encounter this problem
approx 50% of the time, with the same input conditions (ie I blow away
all rpms'' and directories). Interesting how it toggles the result from
the same inputs. The other half of the time, it works just fine,
creates the symlink and doesn''t barf.
I did read this...
http://projects.reductivelabs.com/issues/1825
... not really following the reductive labs doc on symlinks, I put a
links => manage as luke suggested, in a File {} in my site.pp. Same
problem.
Also noticed that when this problem occurs, the symlink doesn''t get
created. Instead puppet creates a new directory called
''current''.
What''s up with this?
Doug.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
Hi Doug,
It looks like you want to create the link
/opt/jboss/current => /opt/jboss/jboss-${jboss_version}
but
/opt/jboss/current
already exists and is a directory
can you show me
>ls -l /opt/jboss/current
Is it possible that another resource creates this path as a dir? maybe thats
why it happens half of the time (depending on which gets applied first, the
link or dir)
can you also run
>ls -l /opt/jboss/current;puppetd --test | grep /opt/jboss/current;ls -l
/opt/jboss/current
to get a more condensed view on how this resource is managed during the
entire run.
regards,
Dan
On Tue, Nov 17, 2009 at 2:10 AM, Douglas Garstang
<doug.garstang@gmail.com>wrote:
>
> What is puppet doing here?
>
> Nov 17 00:02:01 gumby yum: Installed: tf-starterkit-tfel0-1.0-1.tf.noarch
> Nov 17 00:02:01 gumby puppetd[720]:
> (//Node[gumby.fr.xxx.com
> ]/Starterkit::Setup[tfel0]/Package[tf-starterkit-tfel0]/ensure)
> created
> Nov 17 00:02:07 gumby yum: Installed: tf-jboss-server-4.2.3.GA-1.tf.noarch
> Nov 17 00:02:07 gumby puppetd[720]:
> (//Node[app_node]/jboss::server/Package[tf-jboss-server]/ensure)
> created
> Nov 17 00:02:07 gumby puppetd[720]:
> (//Node[app_node]/jboss::server/File[/opt/jboss/current]) Recursively
> backing up to filebucket
> Nov 17 00:02:43 gumby puppetd[720]:
> (//Node[app_node]/jboss::server/File[/opt/jboss/current]) Filebucketed
> /opt/jboss/current/server/tfel0/deploy/eazye.ear to main with sum 703
> b44a0459ed5f1569c0096ab435ea0
> Nov 17 00:02:43 gumby puppetd[720]:
> (//Node[app_node]/jboss::server/File[/opt/jboss/current]) Not removing
> directory; use ''force'' to override
> Nov 17 00:02:43 gumby puppetd[720]:
> (//Node[app_node]/jboss::server/File[/opt/jboss/current]) Recursively
> backing up to filebucket
> Nov 17 00:03:18 gumby puppetd[720]:
> (//Node[app_node]/jboss::server/File[/opt/jboss/current]) Filebucketed
> /opt/jboss/current/server/tfel0/deploy/eazye.ear to main with sum 703
> b44a0459ed5f1569c0096ab435ea0
> Nov 17 00:03:18 gumby puppetd[720]:
> (//Node[app_node]/jboss::server/File[/opt/jboss/current]) Not removing
> directory; use ''force'' to override
> Nov 17 00:03:18 gumby puppetd[720]:
> (//Node[app_node]/jboss::server/File[/opt/jboss/current]/ensure)
> change from directory to link failed: Could not remove existing file
>
> Why is it trying to remove a directory? (Which directory?). I
didn''t
> tell it to do that in the manifest. I do have this..
>
> file {
> "/opt/jboss/current":
> links => manage,
> ensure => "/opt/jboss/jboss-${jboss_version}",
> require => Package["tf-jboss-server"];
> }
>
> that should create a symlink. Puppet seems to encounter this problem
> approx 50% of the time, with the same input conditions (ie I blow away
> all rpms'' and directories). Interesting how it toggles the result
from
> the same inputs. The other half of the time, it works just fine,
> creates the symlink and doesn''t barf.
>
> I did read this...
> http://projects.reductivelabs.com/issues/1825
>
> ... not really following the reductive labs doc on symlinks, I put a
> links => manage as luke suggested, in a File {} in my site.pp. Same
> problem.
>
> Also noticed that when this problem occurs, the symlink doesn''t
get
> created. Instead puppet creates a new directory called
''current''.
>
> What''s up with this?
>
> Doug.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
Hi Dan. Thanks for the swift reply. I worked it out. It was a dependancy problem. An RPM was being installed before hand and creating /opt/jboss/current as a directory, which puppet didn''t like. I guess the error message is pretty unintuitive here. I tell ya... the puppet dependancies do my head in. It''s getting to the point where I''m going to be afraid to touch any part of this puppet code in the future for fear of breaking a dependancy. :( Doug. On Tue, Nov 17, 2009 at 12:34 AM, Dan Bode <dan@reductivelabs.com> wrote:> Hi Doug, > > It looks like you want to create the link > > /opt/jboss/current => /opt/jboss/jboss-${jboss_version} > > but > > /opt/jboss/current > > already exists and is a directory > > can you show me > >>ls -l /opt/jboss/current > > Is it possible that another resource creates this path as a dir? maybe thats > why it happens half of the time (depending on which gets applied first, the > link or dir) > > can you also run > >>ls -l /opt/jboss/current;puppetd --test | grep /opt/jboss/current;ls -l >> /opt/jboss/current > > to get a more condensed view on how this resource is managed during the > entire run. > > regards, > > Dan > > On Tue, Nov 17, 2009 at 2:10 AM, Douglas Garstang <doug.garstang@gmail.com> > wrote: >> >> What is puppet doing here? >> >> Nov 17 00:02:01 gumby yum: Installed: tf-starterkit-tfel0-1.0-1.tf.noarch >> Nov 17 00:02:01 gumby puppetd[720]: >> >> (//Node[gumby.fr.xxx.com]/Starterkit::Setup[tfel0]/Package[tf-starterkit-tfel0]/ensure) >> created >> Nov 17 00:02:07 gumby yum: Installed: tf-jboss-server-4.2.3.GA-1.tf.noarch >> Nov 17 00:02:07 gumby puppetd[720]: >> (//Node[app_node]/jboss::server/Package[tf-jboss-server]/ensure) >> created >> Nov 17 00:02:07 gumby puppetd[720]: >> (//Node[app_node]/jboss::server/File[/opt/jboss/current]) Recursively >> backing up to filebucket >> Nov 17 00:02:43 gumby puppetd[720]: >> (//Node[app_node]/jboss::server/File[/opt/jboss/current]) Filebucketed >> /opt/jboss/current/server/tfel0/deploy/eazye.ear to main with sum 703 >> b44a0459ed5f1569c0096ab435ea0 >> Nov 17 00:02:43 gumby puppetd[720]: >> (//Node[app_node]/jboss::server/File[/opt/jboss/current]) Not removing >> directory; use ''force'' to override >> Nov 17 00:02:43 gumby puppetd[720]: >> (//Node[app_node]/jboss::server/File[/opt/jboss/current]) Recursively >> backing up to filebucket >> Nov 17 00:03:18 gumby puppetd[720]: >> (//Node[app_node]/jboss::server/File[/opt/jboss/current]) Filebucketed >> /opt/jboss/current/server/tfel0/deploy/eazye.ear to main with sum 703 >> b44a0459ed5f1569c0096ab435ea0 >> Nov 17 00:03:18 gumby puppetd[720]: >> (//Node[app_node]/jboss::server/File[/opt/jboss/current]) Not removing >> directory; use ''force'' to override >> Nov 17 00:03:18 gumby puppetd[720]: >> (//Node[app_node]/jboss::server/File[/opt/jboss/current]/ensure) >> change from directory to link failed: Could not remove existing file >> >> Why is it trying to remove a directory? (Which directory?). I didn''t >> tell it to do that in the manifest. I do have this.. >> >> file { >> "/opt/jboss/current": >> links => manage, >> ensure => "/opt/jboss/jboss-${jboss_version}", >> require => Package["tf-jboss-server"]; >> } >> >> that should create a symlink. Puppet seems to encounter this problem >> approx 50% of the time, with the same input conditions (ie I blow away >> all rpms'' and directories). Interesting how it toggles the result from >> the same inputs. The other half of the time, it works just fine, >> creates the symlink and doesn''t barf. >> >> I did read this... >> http://projects.reductivelabs.com/issues/1825 >> >> ... not really following the reductive labs doc on symlinks, I put a >> links => manage as luke suggested, in a File {} in my site.pp. Same >> problem. >> >> Also noticed that when this problem occurs, the symlink doesn''t get >> created. Instead puppet creates a new directory called ''current''. >> >> What''s up with this? >> >> Doug. >> >> > > > > >-- Regards, Douglas Garstang http://www.linkedin.com/in/garstang Email: doug.garstang@gmail.com Cell: +1-805-340-5627 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---