Jira (PUP-2150) Specifying proxy = 'absent' or baseurl = 'absent' on any yumrepo resource breaks Puppet 3.5.0.
Title: Message Title
Anthony Somerset commented on an issue
Re: Specifying proxy = 'absent' or baseurl = 'absent' on any yumrepo resource breaks Puppet 3.5.0.
my understanding at least from the example42 yum module is that values were being set as absent to prevent those lines appearing in the created repo file so we could be flexible in defining a mirrorlist OR a baseurl for a given repo at the most basic level
Add Comment
Puppet / PUP-2150
Specifying proxy = 'absent' or baseurl = 'absent' on any yumrepo resource breaks Puppet 3.5.0.
I am on CentOS 6.5 using open-source Puppet 3.5.0. We were previously using Puppet 3.4.3. We are using the epel module from the forge, which specifies a value of 'absent' for all of the yumrepos it manages by default. This does not work in Puppet 3.5.0, causing this error: {noformat} Error: Parameter proxy failed on Yumrepo[epel-testing]: Must be a...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PUP-1495) Puppet on Debian systems failing to apply file changes
Title: Message Title
Anthony Somerset updated an issue
Puppet / PUP-1495
Puppet on Debian systems failing to apply file changes
Change By:
Anthony Somerset
i'mnotexactlysurewhichversionthisstartedinbutitwasafter3.3.xandstillexistsin3.4.2wheneverafilechangeisdetectedthepuppetrunitwillshowthediffbutbeunabletoapplyit.itseemstotimeout.withoutdebug/verbosethiserrordropsintotheterminalwindow:err:/Stage[main]/Ssh/File[/etc/ssh/sshd_config]:Couldnotevaluate:Puppet::Util::Logrequiresamessagehoweverifirundebugandverboseflagsiget: rror Error :Couldnotbackup/etc/ssh/sshd_config:Timeout::ErrorError:Couldnotbackup/etc/ssh/sshd_config:Timeout::ErrorError:/Stage[main]/Ssh/File[/etc/ssh/sshd_config]/content:changefrom{md5}8caefdd9e251b7cc1baa37874149a870to{md5}2ee23a0ec404874c9e8e8462194fbf29failed:Couldnotbackup/etc/ssh/sshd_config:Timeout::Errorinotethatpluginsynccontinuestowork,creatingnewfilespullingfrompuppet(eithertemplateorstraightfile)butanyfilechangeorfiledeletefailsifidisablepassengerandloadthepuppetmasterdirectly,theneverythingworkscorrectlyifidisablefilebackupsthenitworksfinealsosothetimeoutoccursonthefilebackup
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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.
Jira (PUP-1495) Puppet on Debian systems failing to apply file changes
Title: Message Title
Anthony Somerset created an issue
Puppet / PUP-1495
Puppet on Debian systems failing to apply file changes
Issue Type:
Bug
Affects Versions:
3.4.2
Assignee:
Eric Sorenson
Created:
22/Jan/14 11:15 PM
Environment:
Debian 64 Bit - Wheezy master (with foreman) through passenger, mix of wheezy or squeeze clients
Priority:
Normal
Reporter:
Anthony Somerset
i'm not exactly sure which version this started in but it was after 3.3.x and still exists in 3.4.2
whenever a file change is detected the puppet run it will show the diff but be unable to apply it. it seems to timeout. without debug/verbose this error drops into the terminal window:
err: /Stage[main]/Ssh/File[/etc/ssh/sshd_config]: Could not evaluate: Puppet::Util::Log requires a message
however if i run debug and verbose flags i get:
rror: Could not back up /etc/ssh/sshd_config: Timeout::Error Error: Could not back up /etc/ssh/sshd_config: Timeout::Error Error: /Stage[main]/Ssh/File[/etc/ssh/sshd_config]/content: change from {md5}8caefdd9e251b7cc1baa37874149a870 to {md5}
2ee23a0ec404874c9e8e8462194fbf29 failed: Could not back up /etc/ssh/sshd_config: Timeout::Error
i note that pluginsync continues to work, creating new files pulling from
Jira (MCO-139) fails to run on debian/ubuntu with ruby 1.9
Title: Message Title Anthony Somerset commented on an issue Re: fails to run on debian/ubuntu with ruby 1.9 as per the original redmine ticket - this has been fixed in master branch already however no stable release has been made so its fundamentally broken out of the box still and has been for several months Add Comment MCollective / MCO-139 fails to run on debian/ubuntu with ruby 1.9 Current debian packags install mcollective in /usr/lib/ruby1.8. This works fine as long as /usr/bin/ruby is ruby 1.8. Starting with debian-wheezy and ubuntu-quantal (both due soon), the default ruby version is 1.9. When installing the packages from apt.puppetlabs.com on these systems, mcollective fails to start, which corrupts dpkg consistency: Unpa... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (MCO-139) fails to run on debian/ubuntu with ruby 1.9
Title: Message Title Anthony Somerset updated an issue MCollective / MCO-139 fails to run on debian/ubuntu with ruby 1.9 Change By: Anthony Somerset Component/s: Platform Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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.
Jira (MCO-139) fails to run on debian/ubuntu with ruby 1.9
Title: Message Title Anthony Somerset created an issue MCollective / MCO-139 fails to run on debian/ubuntu with ruby 1.9 Issue Type: Bug Assignee: Unassigned Created: 16/Dec/13 10:59 PM Environment: Debian Wheezy or Ubuntu 13.04 or later Labels: debian ubuntu apt Priority: Major Reporter: Anthony Somerset Current debian packags install mcollective in /usr/lib/ruby1.8. This works fine as long as /usr/bin/ruby is ruby 1.8. Starting with debian-wheezy and ubuntu-quantal (both due soon), the default ruby version is 1.9. When installing the packages from apt.puppetlabs.com on these systems, mcollective fails to start, which corrupts dpkg consistency: Unpacking mcollective-common (from .../mcollective-common_2.2.0-2_all.deb) ... Selecting previously unselected package mcollective. Unpacking mcollective (from .../mcollective_2.2.0-2_all.deb) ... Setting up mcollective-common (2.2.0-2) ... Setting up mcollective (2.2.0-2) ... Starting daemon: mcollective /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file mcollective (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/sbin/mcollectived:3:in `main' invoke-rc.d: initscript mcollective, action start failed. dpkg: error processing mcollective (--configure): subprocess installed post-installation script returned error exit
