Jira (PUP-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Fabien Wernli commented on PUP-6759 Re: systemd provider does not understand "indirect" status / tries to turn off service on each run We have the same problem with rpcbind: is-enabled returns 'indirect', and puppet thinks it's not enabled. But we actually need it enabled+running, so in our case, `indirect` should probably return true? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: Jorie Tappa Labels: maintenance provider resolved-issue-added systemd 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Joshua Keiser updated an issue Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: Joshua Keiser Fix Version/s: PUP 4.9.0 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: Eric Thompson QA Risk Assessment Reason: annoyance. covered well by mocked unit tests 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: Eric Thompson QA Risk Assessment: No Action 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: Eric Thompson QA Contact: Eric Thompson 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: William Hopper Status: Ready for CI Test Assignee: qa 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Adrien Thebo commented on PUP-6759 Re: systemd provider does not understand "indirect" status / tries to turn off service on each run A cursory inspection of those states reads to me that things like generated or transient should probably be handled in the same manner as indirect. That being said those seem to be pretty unusual and uncommon, so if there's a good reason to handle this now we should add those fixes - but I'm not feeling a strong compulsion to do that right now. 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title William Hopper commented on PUP-6759 Re: systemd provider does not understand "indirect" status / tries to turn off service on each run Yeah, they should be dealt with in the best way puppet can (systemd kind of breaks some of puppet's abstractions sometimes). For most cases, we handle the state by looking at the return code of is-enabled. This mostly works except for states like indirect and masked, which are special. If you come across any other states that don't work correctly, we'd really appreciate it if you file another ticket for them. Thanks! 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Robert Rosengren commented on PUP-6759 Re: systemd provider does not understand "indirect" status / tries to turn off service on each run That sounds correct to me as a solution to the "indirect" problem. But if any of the other states come up which are described, should that also be dealt with ? 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6759
systemd provider does not understand "indirect" status / tries to turn off service on each run
Change By:
William Hopper
Acceptance Criteria:
The {{rpcbind}} service on RedHat 7 should show up as {{enabled => false}} when puppet is run with {{puppet resource service rpcbind}}.
Labels:
maintenance provider systemd
Story Points:
1
Release Notes Summary:
The systemd provider now considers services with the 'indirect' enabled state to be disabled.
Team:
Agent & Platform Puppet Developer Support
Sprint:
PDS 2016-11-30
Release Notes:
Bug Fix
Add Comment
Jira (PUP-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: William Hopper Assignee: Kylo Ginsberg William Hopper 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title William Hopper commented on PUP-6759 Re: systemd provider does not understand "indirect" status / tries to turn off service on each run Robert Rosengren my understanding of the indirect status (as detailed in https://www.freedesktop.org/software/systemd/man/systemctl.html) is that we should simply return false for is_enabled? when we come across such a service. Does that sound correct to you? 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Robert Rosengren created an issue Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Issue Type: Bug Affects Versions: PUP 3.8.8 Assignee: Kylo Ginsberg Components: Catalog Application, Types and Providers Created: 2016/09/30 4:37 AM Environment: RedHat 7.X - systemd Labels: systemd provider Priority: Normal Reporter: Robert Rosengren Following occurs with each puppet run, which causes annoyance: Service[rpcbind]/enable: enable changed 'true' to 'false' The rpcbind service returns "indirect" as a status to is-enabled _*/bin/systemctl is-enabled rpcbind indirect*_
