Jira (PUP-4540) Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Title: Message Title Victor Danilchenko commented on PUP-4540 Re: Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type That patch looks like it SHOULD work, but it didn't help in my specific case, probably because I could apply it only partially due to version difference (Vivid comes with Puppet 3.7.2, and only two hunks in the patch succeeded for me). I manually applied one of the failed hunks as well (the one that sets systemctl as the default service provider for Vivid), but that didn't work. Since I have a kludgey fix of my own, I decided not to spend more time on this. Just wanted to let you know that at least as far as the Puppet that comes with Vivid, this patch is broken. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4540) Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Title: Message Title Victor Danilchenko commented on PUP-4540 Re: Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type The 'jessie' service provider in the upstream ticket (https://gist.github.com/leepa/9818b46b29b161413824) works – however, so does the stock 'debian' provider. The problem is that the service management gets automatically delegated to the Upstart provider instead. In fact, simply removing service/upstart.rb provider, or replacing it with string-substituted copy of the service/debian.rb, makes the problem go away. Of course this is not the correct solution, but it solves our specific problem. I am not sure if it's the same problem as the one described in PUP-4503, but if it isn't, it seems to be related. However, I don't think it's the same problem, because PUP-4503 apparently offers the 'jessie' provider as a replacement for the 'debian' provider – but in my case, on Vivid, the 'debian' provider actually works; it's not the provider itself that's broken, but the detection for which provider to delegate service management to. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4540) Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Title: Message Title
Victor Danilchenko updated an issue
Puppet / PUP-4540
Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Change By:
Victor Danilchenko
Ifyou tun run apuppetmanifestonUbuntuVivid,certainservicesgetdetectedincorrectly,andPuppetattemptstotreatthemasUpstartservices.Forinstance,{{mysql}}worksthatway.ThefollowingPuppetmanifestexercisestheerror:{code:none}service{'mysql': ensure=running,}notify{test: notify=Service['mysql']}{code}Output:{code:none}$sudopuppetapplytest.ppNotice:Compiledcatalogforvdanilchenko-vivid.vistaprint.netinenvironmentproductionin0.33secondsNotice:testNotice:/Stage[main]/Main/Notify[test]/message:defined'message'as'test'Error:/Stage[main]/Main/Service[mysql]:Couldnotevaluate:Executionof'/sbin/statusmysql'returned1:status:UnabletoconnecttoUpstart:Failedtoconnecttosocket/com/ubuntu/upstart:ConnectionrefusedError:/Stage[main]/Main/Service[mysql]:Failedtocallrefresh:Executionof'/sbin/statusmysql'returned1:status:UnabletoconnecttoUpstart:Failedtoconnecttosocket/com/ubuntu/upstart:ConnectionrefusedError:/Stage[main]/Main/Service[mysql]:Executionof'/sbin/statusmysql'returned1:status:UnabletoconnecttoUpstart:Failedtoconnecttosocket/com/ubuntu/upstart:Connectionrefused{code}Nowthe{{apache2}}service,forinstance,getsdetectedcorrectly(it'salsonotanUpstartservice,andUpstartcommandsalsofail,butPuppettreatsitasInitserviceandmanagesitcorrectly);but{{mysql}}breaks.Ididn'ttestalltheservicesonthesystem,butthe{{cups}}service,forinstance,alsobreaksjustlike{{mysql}}.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4540) Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Title: Message Title
Victor Danilchenko created an issue
Puppet / PUP-4540
Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/05/07 11:00 AM
Priority:
Normal
Reporter:
Victor Danilchenko
If you tun a puppet manifest on Ubuntu Vivid, certain services get detected incorrectly, and Puppet attempts to treat them as Upstart services. For instance, mysql works that way. The following Puppet manifest exercises the error:
service{'mysql':
ensure = running,
}
Jira (PUP-4540) Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Title: Message Title
Victor Danilchenko updated an issue
Puppet / PUP-4540
Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Change By:
Victor Danilchenko
IfyourunapuppetmanifestonUbuntuVivid,certainservicesgetdetectedincorrectly,andPuppetattemptstotreatthemasUpstartservices ,usingthe/sbin/{start,stop,restart,reload,status}commands .Forinstance,{{mysql}}worksthatway.ThefollowingPuppetmanifestexercisestheerror:{code:none}service{'mysql': ensure=running,}notify{test: notify=Service['mysql']}{code}Output:{code:none}$sudopuppetapplytest.ppNotice:Compiledcatalogforvdanilchenko-vivid.vistaprint.netinenvironmentproductionin0.33secondsNotice:testNotice:/Stage[main]/Main/Notify[test]/message:defined'message'as'test'Error:/Stage[main]/Main/Service[mysql]:Couldnotevaluate:Executionof'/sbin/statusmysql'returned1:status:UnabletoconnecttoUpstart:Failedtoconnecttosocket/com/ubuntu/upstart:ConnectionrefusedError:/Stage[main]/Main/Service[mysql]:Failedtocallrefresh:Executionof'/sbin/statusmysql'returned1:status:UnabletoconnecttoUpstart:Failedtoconnecttosocket/com/ubuntu/upstart:ConnectionrefusedError:/Stage[main]/Main/Service[mysql]:Executionof'/sbin/statusmysql'returned1:status:UnabletoconnecttoUpstart:Failedtoconnecttosocket/com/ubuntu/upstart:Connectionrefused{code} Ofcourse,thisfailsbecauserunning{{/sbin/statusmysql}}fails.Thiscanbeverifiedbysimplyrunningitoncommandline. Nowthe{{apache2}}service,forinstance,getsdetectedcorrectly( it'salsonotan Upstart service,andUpstart commandsalsofail,butPuppettreats it apache2 asInitserviceandmanagesitcorrectly);but{{mysql}}breaks.Ididn'ttestalltheservicesonthesystem,butthe{{cups}}service,forinstance,alsobreaks , justlike{{mysql}}.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4540) Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Title: Message Title Victor Danilchenko commented on PUP-4540 Re: Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type I am not sure this is a duplicate, though it might be related. Is there a fix for PUP-4503 that I can grab and see if it fixes the problem? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
