headers
puppet | 1 Jan 2007 01:08

Re: [Puppet-dev] #369: mount does not seem to fix broken entries

#369: mount does not seem to fix broken entries
---------------------------------+------------------------------------------
 Reporter:  digant <at> stanford.edu  |        Owner:  luke  
     Type:  defect               |       Status:  closed
 Priority:  low                  |    Milestone:  minor 
Component:  library              |      Version:        
 Severity:  normal               |   Resolution:  fixed 
 Keywords:                       |  
---------------------------------+------------------------------------------
Changes (by luke):

  * status:  assigned => closed
  * resolution:  => fixed

Comment:

 Fixed in [2008].

--

-- 
Ticket URL: <https://reductivelabs.com/cgi-bin/puppet.cgi/ticket/369#comment:4>
puppet <https://reductivelabs.com>
Puppet - Portable System Automation
Permalink | Reply | 0 comments |
headers
puppet | 1 Jan 2007 22:59

Re: [Puppet-dev] #360: sshkey collect/export example broken

#360: sshkey collect/export example broken
---------------------+------------------------------------------------------
 Reporter:  puppet   |        Owner:  luke    
     Type:  defect   |       Status:  assigned
 Priority:  normal   |    Milestone:  minor   
Component:  library  |      Version:          
 Severity:  normal   |   Resolution:          
 Keywords:           |  
---------------------+------------------------------------------------------
Changes (by luke):

  * status:  new => assigned
  * milestone:  => minor

--

-- 
Ticket URL: <https://reductivelabs.com/cgi-bin/puppet.cgi/ticket/360#comment:2>
puppet <https://reductivelabs.com>
Puppet - Portable System Automation
Permalink | Reply | 0 comments |
headers
Luke Kanies | 2 Jan 2007 00:18
Gravatar

[Puppet-dev] Bug #393: Looking for Rails help

Hi all (and especially Blake and Matt),

I'm having some problems with Rails:  https://reductivelabs.com/cgi- 
bin/puppet.cgi/ticket/393

I've modified the existing test for 'Puppet::Rails::Host#store' so  
that it exposes this bug, but it seems to expose a couple more problems.

All of the issues seem to be related to saving modified rails  
objects.  The bug report points to a problem where new resources are  
saved with no host_id, even though they are all set up with the  
correct value.  Somehow, saving the resource loses the value.  The  
only place I explicitly save any objects are when I call save on the  
host itself (this is because saving everything at once is *much*  
faster than saving everything piecemeal), so it appears that I'm  
somehow losing the association between the new resources and the  
existing host.

Notably, if neither the host nor the resource exist when 'save' is  
called, it all works fine.

The problem persists below the level of the resource, from what I can  
tell.

I'm going to take a break and re-attack this bug tomorrow, but I'd  
certainly appreciate any insight anyone might have.

Cheers,
Luke
(Continue reading)

Permalink | Reply | 0 comments |
headers
puppet | 1 Jan 2007 22:58

[Puppet-dev] #393: New resources are not added to existing Rails hosts

#393: New resources are not added to existing Rails hosts
---------------------+------------------------------------------------------
 Reporter:  luke     |       Owner:  luke 
     Type:  defect   |      Status:  new  
 Priority:  normal   |   Milestone:  minor
Component:  library  |     Version:       
 Severity:  blocker  |    Keywords:  rails
---------------------+------------------------------------------------------
 It appears that when new resources are created for existing hosts, they do
 not correctly get their host_id set, which kinda breaks the relationship.

--

-- 
Ticket URL: <https://reductivelabs.com/cgi-bin/puppet.cgi/ticket/393>
puppet <https://reductivelabs.com>
Puppet - Portable System Automation
Permalink | Reply | 1 comment |
headers
puppet | 2 Jan 2007 01:26

[Puppet-dev] #394: Removing template files makes puppetmasterd stop working

#394: Removing template files makes puppetmasterd stop working
---------------------+------------------------------------------------------
 Reporter:  mpalmer  |       Owner:  luke  
     Type:  defect   |      Status:  new   
 Priority:  high     |   Milestone:        
Component:  server   |     Version:  0.20.1
 Severity:  normal   |    Keywords:        
---------------------+------------------------------------------------------
 If you define an object that uses a template, and then later rename that
 file (or remove it) and edit the manifest to match, {{{puppetmasterd}}}
 refuses to serve clients any more, and gives error messages like this in
 the log:

 {{{
 Jan  2 09:12:59 pmaster puppetmasterd[30963]: No such file or directory -
 /etc/puppet/config/templated-file.erb
 }}}

 The only workaround I have found for this is to restart
 {{{puppetmasterd}}}.

--

-- 
Ticket URL: <https://reductivelabs.com/cgi-bin/puppet.cgi/ticket/394>
puppet <https://reductivelabs.com>
Puppet - Portable System Automation
Permalink | Reply | 2 comments |
headers
puppet | 2 Jan 2007 03:49

[Puppet-dev] #395: Files in non-existent directories cause execution to halt

#395: Files in non-existent directories cause execution to halt
---------------------+------------------------------------------------------
 Reporter:  mpalmer  |       Owner:  luke
     Type:  defect   |      Status:  new 
 Priority:  normal   |   Milestone:      
Component:  types    |     Version:      
 Severity:  normal   |    Keywords:      
---------------------+------------------------------------------------------
 (currently running svn2013)

 If I try to copy a file into a directory which doesn't exist at the
 beginning of the Puppet execution run, I get an error like this:

 {{{
 err: Could not apply complete configuration: Could not retrieve object
 '/usr/share/ruby-snmpd/plugins/last_puppet_run.rb' of type
 'Puppet::Type::File' at /etc/puppet/manifests/classes/snmp_enabled.pp:36
 }}}

 and the manifest stops running.  The real problem is that the directory
 that I want to copy the file into is part of a package, and that package
 is depended on by this file, like so:

 {{{
 file { "/usr/share/ruby-snmpd/plugins/last_puppet_run.rb":
   content =>
 template("/etc/puppet/config/classes/snmp_enabled/last_puppet_run.rb",
   require => package["ruby-snmpd"]
 }
(Continue reading)

Permalink | Reply | 2 comments |
headers
puppet | 2 Jan 2007 04:01

Re: [Puppet-dev] #395: subscribing to non-existant objects confuses Matt

#395: subscribing to non-existant objects confuses Matt
---------------------+------------------------------------------------------
 Reporter:  mpalmer  |        Owner:  luke   
     Type:  defect   |       Status:  closed 
 Priority:  normal   |    Milestone:         
Component:  types    |      Version:         
 Severity:  normal   |   Resolution:  invalid
 Keywords:           |  
---------------------+------------------------------------------------------
Changes (by mpalmer):

  * status:  new => closed
  * resolution:  => invalid
  * summary:  Files in non-existent directories cause execution to halt =>
              subscribing to non-existant objects confuses
              Matt

Comment:

 This was a stuff-up on my part.  It wasn't that I was trying to put a file
 into a non-existent directory, if was that I was subscribing to a file
 object that didn't exist.

--

-- 
Ticket URL: <http://reductivelabs.com/cgi-bin/puppet.cgi/ticket/395#comment:1>
puppet <https://reductivelabs.com>
Puppet - Portable System Automation
Permalink | Reply | 0 comments |
headers
puppet | 2 Jan 2007 04:22

[Puppet-dev] #396: Missing packages produce spurious output

#396: Missing packages produce spurious output
---------------------+------------------------------------------------------
 Reporter:  mpalmer  |       Owner:  luke
     Type:  defect   |      Status:  new 
 Priority:  normal   |   Milestone:      
Component:  types    |     Version:      
 Severity:  minor    |    Keywords:      
---------------------+------------------------------------------------------
 (svn2013 again)

 Each package that Puppet installs heralds an error message, like so:

 {{{
 No packages found matching elinks.
 }}}

 After this, Puppet actually goes ahead and installs the package, so it's
 purely cosmetic -- just annoying.

 There's no mention of 'No packages found' in the source code, so I'm at a
 bit of a loss as to where exactly it's coming from.

--

-- 
Ticket URL: <http://reductivelabs.com/cgi-bin/puppet.cgi/ticket/396>
puppet <https://reductivelabs.com>
Puppet - Portable System Automation
Permalink | Reply | 2 comments |
headers
puppet | 2 Jan 2007 04:52

Re: [Puppet-dev] #396: Missing packages produce spurious output

#396: Missing packages produce spurious output
---------------------+------------------------------------------------------
 Reporter:  mpalmer  |        Owner:  luke
     Type:  defect   |       Status:  new 
 Priority:  normal   |    Milestone:      
Component:  types    |      Version:      
 Severity:  minor    |   Resolution:      
 Keywords:           |  
---------------------+------------------------------------------------------
Comment (by mpalmer):

 I had a bit more of a ponder, and decided the output was probably coming
 from an external command.  Sure enough, if you run {{{dpkg-query}}} and
 give it a package that it doesn't know anything about, you get exactly the
 same error message.

 The call in question is at {{{lib/puppet/provider/package/dpkg.rb:57}}}
 (of svn2013).  I think the correct solution is ''probably'' to redirect
 stderr to stdout, or perhaps to {{{/dev/null}}}, but we might want to
 capture the output somewhere, or do something else funky.  I leave it to
 you, Luke, to decide what's best there.

--

-- 
Ticket URL: <http://reductivelabs.com/cgi-bin/puppet.cgi/ticket/396#comment:1>
puppet <https://reductivelabs.com>
Puppet - Portable System Automation
Permalink | Reply | 0 comments |
headers
puppet | 2 Jan 2007 07:54

Re: [Puppet-dev] #396: Missing packages produce spurious output

#396: Missing packages produce spurious output
---------------------+------------------------------------------------------
 Reporter:  mpalmer  |        Owner:  luke  
     Type:  defect   |       Status:  closed
 Priority:  normal   |    Milestone:        
Component:  types    |      Version:        
 Severity:  minor    |   Resolution:  fixed 
 Keywords:           |  
---------------------+------------------------------------------------------
Changes (by luke):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 Yeah, I figured this was a problem with an external command as soon as I
 saw it.  Fixed in [2014].

--

-- 
Ticket URL: <http://reductivelabs.com/cgi-bin/puppet.cgi/ticket/396#comment:2>
puppet <https://reductivelabs.com>
Puppet - Portable System Automation
Permalink | Reply | 0 comments |

Gmane