Jira (PUP-6552) Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6552 Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad. Change By: Kylo Ginsberg Scrum Team: Client Platform 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-6552) Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6552 Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad. Change By: Kylo Ginsberg Sprint: Client Triage 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-6552) Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-6552 Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad. Change By: Kylo Ginsberg Assignee: Kylo Ginsberg 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-6552) Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Title: Message Title Michael Smith commented on PUP-6552 Re: Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad. This suggests our fix for PUP-2744 may not have been the right choice. 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-6552) Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Title: Message Title
Paul Anderson updated an issue
Puppet / PUP-6552
Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Change By:
Paul Anderson
Discovered this while working with a customer to migrate from a PE 3.x to 2016.2In puppet 3.x, This service definition worked equally well for Solaris 10 and 11 and RedHat 6 and 7:service{ $service_name : tag => 'mytag', hasrestart => false, hasstatus => true, provider => 'init', }In puppet PE 2016.2, it works well for Solaris 10 and 11. However, Redhat 6 and 7 fail: Provider init is not functional on this hostIf the provider is changed to redhat, it fails differently: Service[]/enable) change from false to true failed: Could not enable : Execution of '/sbin/chkconfig --add ' returned 1: service does not support chkconfig [Service name censored to protect the innocent]
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-6552) Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Title: Message Title Paul Anderson commented on PUP-6552 Re: Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad. I understand a PS Engineer has encountered a similar situation with Ubuntu. 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-6552) Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Title: Message Title Paul Anderson updated an issue Puppet / PUP-6552 Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad. Change By: Paul Anderson Environment: RHEL 6 and 7Solaris 10 and 113rd party commercial software that runs on both RHEL and Solaris 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-6552) Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Title: Message Title
Paul Anderson updated an issue
Puppet / PUP-6552
Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Change By:
Paul Anderson
Discovered this while working with a customer to migrate from a PE 3.x to 2016.2In puppet 3.x, This service definition worked equally well for Solaris 10 and 11 and RedHat 6 and 7:service{ $service_name : tag => ' volatile mytag ', hasrestart => false, hasstatus => true, provider => 'init', }In puppet 2016.2, it works well for Solaris 10 and 11. However, Redhat 6 and 7 fail: Provider init is not functional on this hostIf the provider is changed to redhat, it fails differently: Service[]/enable) change from false to true failed: Could not enable : Execution of '/sbin/chkconfig --add ' returned 1: service does not support chkconfig [Service name censored to protect the innocent]
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-6552) Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Title: Message Title
Paul Anderson updated an issue
Puppet / PUP-6552
Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Change By:
Paul Anderson
Discovered this while working with a customer to migrate from a PE 3.x to 2016.2In puppet 3.x, This service definition worked equally well for Solaris 10 and 11 and RedHat 6 and 7:service{ $service_name : tag => 'volatile', hasrestart => false, hasstatus => true, provider => 'init', }In puppet 2016.2, it works well for Solaris 10 and 11. However, Redhat 6 and 7 fail: Provider init is not functional on this hostIf the provider is changed to redhat, it fails differently: Service[]/enable) change from false to true failed: Could not enable : Execution of '/sbin/chkconfig --add ' returned 1: service does not support chkconfig [Service name censored to protect the innocent]
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-6552) Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Title: Message Title
Paul Anderson updated an issue
Puppet / PUP-6552
Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Change By:
Paul Anderson
Discovered this while working with a customer to migrate from a PE 3.x to 2016.2 Basically In puppet 3.x , a 3rd party writes commercial software This service definition worked equally well for RedHat and Solaris . They have a hand crafted init script that works for both Solaris 10 and Redhat, BUT that script is not compatible with upstart or systemd. (run the script, start the service, etc...) 11 and RedHat 6 and 7: Thus service{ $service_name : tag => 'volatile' , the redhat hasrestart => false, hasstatus => true, provider can => ' t start the script while the init provider on Solaris can do it perfectly well. ', } These days init forces Redhat In puppet 2016.2 , Debian it works well for Solaris 10 and Ubuntu to use their own providers (Upstart, SystemD, etc 11 . )Consequently However , the customer Redhat 6 and 7 fail: Provider init is left with a difficult choice, should they hack puppet or hack their commercial application, each with support implications. not functional on this host I'll work with If the customer provider is changed to get specific code and output and open + link a private ticket with the relevant information. redhat, it fails differently: Service[]/enable) change from false to true failed: Could not enable : Execution of '/sbin/chkconfig --add ' returned 1: service does not support chkconfig
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6552) Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad.
Title: Message Title Paul Anderson created an issue Puppet / PUP-6552 Forcing Redhat, Debian and Ubuntu away from Init provider in all circumstances is bad. Issue Type: Bug Affects Versions: PUP 4.5.3 Assignee: Kylo Ginsberg Components: Breaking Change, Types and Providers Created: 2016/07/26 2:54 PM Environment: RHEL 6 and 7 Solaris 10 and 11 3rd party software that runs on both RHEL and Solaris Priority: Normal Reporter: Paul Anderson Discovered this while working with a customer to migrate from a PE 3.x to 2016.2 Basically, a 3rd party writes commercial software for RedHat and Solaris. They have a hand crafted init script that works for both Solaris and Redhat, BUT that script is not compatible with upstart or systemd. (run the script, start the service, etc...) Thus, the redhat provider can't start the script while the init provider on Solaris can do it perfectly well. These days init forces Redhat, Debian and Ubuntu to
