Jira (PUP-8770) Puppet resource service status should be more than binary
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-8770 Puppet resource service status should be more than binary Change By: Ciprian Badescu Sprint: ready for triage Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.252196.1527017522000.160539.1634818620032%40Atlassian.JIRA.
Jira (PUP-8770) Puppet resource service status should be more than binary
Title: Message Title Josh Cooper commented on PUP-8770 Re: Puppet resource service status should be more than binary There are a number of issues in this area for different services, see PUP-4993, PUP-5474, PUP-6254 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.252196.1527017522000.55285.1623464280036%40Atlassian.JIRA.
Jira (PUP-8770) Puppet resource service status should be more than binary
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-8770 Puppet resource service status should be more than binary Change By: Bogdan Irimie Sprint: ready for triage Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.252196.1527017522000.72416.1604566321656%40Atlassian.JIRA.
Jira (PUP-8770) Puppet resource service status should be more than binary
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-8770 Puppet resource service status should be more than binary Change By: Bogdan Irimie Sprint: Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.252196.1527017522000.72347.1604566261400%40Atlassian.JIRA.
Jira (PUP-8770) Puppet resource service status should be more than binary
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-8770 Puppet resource service status should be more than binary Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.252196.1527017522000.87980.1592319240032%40Atlassian.JIRA.
Jira (PUP-8770) Puppet resource service status should be more than binary
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8770 Puppet resource service status should be more than binary Change By: Josh Cooper Epic Link: PUP-7803 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.252196.1527017522000.84763.1591856760055%40Atlassian.JIRA.
Jira (PUP-8770) Puppet resource service status should be more than binary
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8770 Puppet resource service status should be more than binary Change By: Josh Cooper Team: Coremunity Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.252196.1527017522000.84764.1591856760111%40Atlassian.JIRA.
Jira (PUP-8770) Puppet resource service status should be more than binary
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8770 Puppet resource service status should be more than binary Change By: Craig Gomes Team: Coremunity 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 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-8770) Puppet resource service status should be more than binary
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-8770 Puppet resource service status should be more than binary Change By: Adam Bottchen CS Priority: Needs Priority Reviewed 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 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-8770) Puppet resource service status should be more than binary
Title: Message Title
Paul Schaffer created an issue
Puppet / PUP-8770
Puppet resource service status should be more than binary
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/05/22 12:32 PM
Priority:
Normal
Reporter:
Paul Schaffer
When the Puppet Agent runs during boot (or at other times, during changes of various sorts), some services may still be starting, which means they show a different state than "active" for the service units. When Puppet runs, it tries to enforce { ensure=>running , enable => true} on the Service resource, which ends up restarting the already-starting service. For example, when restarting a host running a MariaDB Galera cluster, MariaDB is in the process of "catching up" with the cluster (via IST) when Puppet restarts it. That ends up breaking the incremental updates, requiring the node to take even longer to start up again by doing a full SST (which also makes another node in the cluster unavailable at that time). The desired behavior is that Puppet would see that the service is already in the process of starting, and do nothing, or possibly just log a warning. A similar issue likely exists for services which are in the process of stopping. The command `systemctl status is-active mariadb.service` returns this output in these states:
active (exit code 0) – normal "fully started" state
inactive (exit code 3) – fully stopped
deactivating (exit code 3) – in the process of stopping
activating (exit code 3) – in the process of starting
Puppet is simply leveraging an exit code of 0 or nonzero to determine the state, but it should probably be interpreting the actual state, through the contents of STDOUT from `systemctl is-active $SERVICE_NAME` for instance, so that it can properly handle these other states.
