Jira (PUP-5891) Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run

2019-10-14 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa assigned an issue to Jorie Tappa  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-5891  
 
 
  Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 
 
Assignee: 
 Jorie Tappa  
 

  
 
 
 
 

 
 
 

 
 
 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.116471.1455280719000.142709.1571084580639%40Atlassian.JIRA.


Jira (PUP-5891) Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run

2017-05-25 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5891 
 
 
 
  Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Team:
 
 Agent 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5891) Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run

2017-05-15 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5891 
 
 
 
  Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Labels:
 
 triaged 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5891) Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run

2016-04-21 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  PUP-5891 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run  
 
 
 
 
 
 
 
 
 
 
I think this falls into the same bucket as our failure to report well on service refreshes. We need to better integrate "Stuff that happens due to a refresh" into the overall logging and reporting structure, and this is just one facet of that 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5891) Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run

2016-02-19 Thread Julien Pivotto (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Julien Pivotto commented on  PUP-5891 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run  
 
 
 
 
 
 
 
 
 
 
We could use  
 
 
 
 
 
 
Notice: /Stage[main]/Main/Refreshme[test]/Exec[This is not executed]: Triggered 'refresh' from 1 events (notrun)
 
 
 
 
 
 
 
Or add a 
 
 
 
 
 
 
/Notice: /Stage[main]/Main/Refreshme[test]/Exec[This is executed]/returns: executed successfully
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 post to this group, send 

Jira (PUP-5891) Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run

2016-02-13 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-5891 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run  
 
 
 
 
 
 
 
 
 
 
It seems like we could drop an additional Notice in https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/exec.rb#L107-L118. 
It would also be nice if one could distinguish the two cases in the report, but if that gets sticky, we could do so under a separate ticket. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5891) Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run

2016-02-12 Thread Julien Pivotto (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Julien Pivotto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5891 
 
 
 
  Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run  
 
 
 
 
 
 
 
 
 

Change By:
 
 Julien Pivotto 
 
 
 

Summary:
 
 Impossible to see the  differencd  difference  in the logs between a refreshed exec that has run and one that has not run 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.