[Puppet - Bug #23085] The RPM specfile doesn't properly stop old puppetd processes after upgrade

2013-12-03 Thread tickets

Issue #23085 has been updated by Melissa Stone.


Released in Puppet 3.4.0-rc1


Bug #23085: The RPM specfile doesn't properly stop old puppetd processes after 
upgrade
https://projects.puppetlabs.com/issues/23085#change-100600

* Author: Sam Kottler
* Status: Closed
* Priority: Normal
* Assignee: Sam Kottler
* Category: Red Hat
* Target version: 3.4.0
* Affected Puppet version: 
* Keywords: 
* Branch: https://github.com/puppetlabs/puppet/pull/2035

Since the binary path changed between 2.6 and later versions, restarting the 
puppet daemon as part of %post doesn't work properly since the init script 
points to the new path(s).


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
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/groups/opt_out.


[Puppet - Bug #23085] The RPM specfile doesn't properly stop old puppetd processes after upgrade

2013-12-03 Thread tickets

Issue #23085 has been updated by Melissa Stone.


Released in Puppet 3.4.0-rc1


Bug #23085: The RPM specfile doesn't properly stop old puppetd processes after 
upgrade
https://projects.puppetlabs.com/issues/23085#change-100685

* Author: Sam Kottler
* Status: Closed
* Priority: Normal
* Assignee: Sam Kottler
* Category: Red Hat
* Target version: 3.4.0
* Affected Puppet version: 
* Keywords: 
* Branch: https://github.com/puppetlabs/puppet/pull/2035

Since the binary path changed between 2.6 and later versions, restarting the 
puppet daemon as part of %post doesn't work properly since the init script 
points to the new path(s).


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
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/groups/opt_out.


[Puppet - Bug #23085] The RPM specfile doesn't properly stop old puppetd processes after upgrade

2013-12-03 Thread tickets

Issue #23085 has been updated by Melissa Stone.


Released in Puppet 3.4.0-rc1


Bug #23085: The RPM specfile doesn't properly stop old puppetd processes after 
upgrade
https://projects.puppetlabs.com/issues/23085#change-100818

* Author: Sam Kottler
* Status: Closed
* Priority: Normal
* Assignee: Sam Kottler
* Category: Red Hat
* Target version: 3.4.0
* Affected Puppet version: 
* Keywords: 
* Branch: https://github.com/puppetlabs/puppet/pull/2035

Since the binary path changed between 2.6 and later versions, restarting the 
puppet daemon as part of %post doesn't work properly since the init script 
points to the new path(s).


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
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/groups/opt_out.


[Puppet - Bug #23085] The RPM specfile doesn't properly stop old puppetd processes after upgrade

2013-12-03 Thread tickets

Issue #23085 has been updated by Melissa Stone.


Released in Puppet 3.4.0-rc1


Bug #23085: The RPM specfile doesn't properly stop old puppetd processes after 
upgrade
https://projects.puppetlabs.com/issues/23085#change-100861

* Author: Sam Kottler
* Status: Closed
* Priority: Normal
* Assignee: Sam Kottler
* Category: Red Hat
* Target version: 3.4.0
* Affected Puppet version: 
* Keywords: 
* Branch: https://github.com/puppetlabs/puppet/pull/2035

Since the binary path changed between 2.6 and later versions, restarting the 
puppet daemon as part of %post doesn't work properly since the init script 
points to the new path(s).


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
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/groups/opt_out.


[Puppet - Bug #23085] The RPM specfile doesn't properly stop old puppetd processes after upgrade

2013-12-03 Thread tickets

Issue #23085 has been updated by Melissa Stone.


Released in Puppet 3.4.0-rc1


Bug #23085: The RPM specfile doesn't properly stop old puppetd processes after 
upgrade
https://projects.puppetlabs.com/issues/23085#change-100955

* Author: Sam Kottler
* Status: Closed
* Priority: Normal
* Assignee: Sam Kottler
* Category: Red Hat
* Target version: 3.4.0
* Affected Puppet version: 
* Keywords: 
* Branch: https://github.com/puppetlabs/puppet/pull/2035

Since the binary path changed between 2.6 and later versions, restarting the 
puppet daemon as part of %post doesn't work properly since the init script 
points to the new path(s).


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
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/groups/opt_out.