Jira (PUP-9998) Puppet agent --disable is ignored with cron puppet agent (splay).

[Daniel Steininger (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Steininger commented on  PUP-9998  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet agent --disable is ignored with cron puppet agent (splay).   
 

  
 
 
 
 

 
 A better behaviour would be if puppet agent would check the lock file again after the sleep.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323623.1567679385000.86467.1567679640126%40Atlassian.JIRA.

Jira (PUP-9998) Puppet agent --disable is ignored with cron puppet agent (splay).

[Daniel Steininger (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Steininger created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9998  
 
 
  Puppet agent --disable is ignored with cron puppet agent (splay).   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 4.10.12  
 
 
Assignee: 
 Henrik Lindberg  
 
 
Components: 
 Functions  
 
 
Created: 
 2019/09/05 3:29 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Daniel Steininger  
 

  
 
 
 
 

 
 Puppet Version: v4.10.12 OS Name/Version: Debian GNU/Linux 8 (jessie) Desired Behavior: All puppet runs should not start until the lock file is available.  Actual Behavior: It seems that the puppet agent command checks if the lock file exists in the early state. If not, the splay sleep starts. Then the puppet run itself starts. When I call "puppet agent - disabled" after Cron based puppet is started. The lock file has no effect on the puppet run, which starts after the sleep phase.  Test scenario  2019-09-05 07:48:46 /opt/puppetlabs/bin/puppet agent --config /etc/puppetlabs/puppet/puppet.conf --onetime --no-daemonize --logdest /var/log/puppetlabs/puppet/puppet.log  starts and is in sleep mode ... 2019-09-05 07:49:25 puppet agent --disable (other shell) ... ... 20 minutes later:  ... sleep over -> Puppet is on going:  ... Puppet is done 2019-09-05 08:18:33 echo $? 0 Lock file is still present: The second run stops correctly.  
 
 
 
 
 root@server:/etc/puppetlabs/puppet# /opt/puppetlabs/bin/puppet agent --config /etc/puppetlabs/puppet/puppet.conf --onetime --no-daemonize --logdest /var/log/puppetlabs/puppet/puppet.log