Jira (PUP-6095) Service provider shouldn't die if an smf service is in state "degraded"

[Sean Griffin (JIRA)]

Title: Message Title

Sean Griffin commented on PUP-6095   Re: Service provider shouldn't die if an smf service is in state "degraded" Shawn Ferry, Geoff Nichols, I am having trouble reproducing the failing condition on a Puppet version that predates the fix (build sha 043c6c30b29539bd89e1ab9dc2cc9843ffa13503, from 17 Apr 2016). The ticket description suggest marking dns as degraded, then checking with 'puppet resouce service'. My problem is that I can't seem to get dns to be marked as degraded. The command 'svcadm mark -Is degraded svc:/network/dns/client:default' doesn't return, and the service reports that it is running fine. root@miqmunumnmmxlha:~# svcadm mark -Is degraded svc:/network/dns/client:default (The -I option is for immediate, -s means wait for it to mark.) I'm waiting for this command to complete. In another window: root@miqmunumnmmxlha:~# svcs -x root@miqmunumnmmxlha:~# svcs | grep dns online 13:52:23 svc:/network/dns/client:default root@miqmunumnmmxlha:~# puppet resource service svc:/network/dns/client:default service { 'svc:/network/dns/client:default': ensure => 'running', enable => 'true', } root@miqmunumnmmxlha:~# Any suggestions about how I might get the system into its failing state? Thanks. 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.