Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Ken Johnson commented on PUP-9041 Re: AIX nim provider can't be used on a NIM master Branan Riley Fortunately there's no limit on the number of NIM masters you can operate on a given host like there is with VIOS partitions, so we can definitely spin some non-prod instances up. How many would be desired and how soon/how high of priority is getting them available. Seems like probably a bit of an edge case, but one which would be quite important to anyone running into it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.267945.153332494.71039.1566583740497%40Atlassian.JIRA.
Jira (PUP-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Ken Johnson commented on an issue Re: Pre/Post-run commands don't work under Windows Joshua Cooper That makes sense. Add Comment Puppet / PUP-1431 Pre/Post-run commands don't work under Windows If a postrun or prerun command is specified in puppet.conf on a Windows host it will fail to execute with a message like the following: Debug: Executing 'C:\Windows\System32\cmd.exe /c type NUL C:\from_postrun.txt' Error: Could not run command from postrun_command: CreateProcess() failed: The system cannot find the file specified.Example postr... 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/d/optout.
Jira (PUP-1362) Rubyize yumhelper.py to remove dependency on python
Title: Message Title Ken Johnson updated an issue Puppet / PUP-1362 Rubyize yumhelper.py to remove dependency on python Change By: Ken Johnson Labels: customer redmine 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-165) MCollective rpc puppetral agent sometimes breaks with encoding errors when querying packages
Title: Message Title Ken Johnson created an issue MCollective / MCO-165 MCollective rpc puppetral agent sometimes breaks with encoding errors when querying packages Issue Type: Bug Assignee: Unassigned Created: 17/Jan/14 2:46 PM Environment: Ubuntu 12.04 LTS, Debian 6.7, PE 3.1.0 Labels: customer Priority: Normal Reporter: Ken Johnson This was first reported as an error with Live Management, a user reported that they were seeing a discrepancy between the number of nodes reporting a given package installed depending on if they searched with the `Live Management-Advanced Tasks-package-status` tool or the `Live Management-Browse Resources-package` tool. I asked them to try running the command line equivalents of these two tasks (`mco package status wget` and `mco rpc puppetral find type=package title=wget`), and they observed that the output of the puppetral method included several errors like the following: pm2.domain.tld Unknown Request Status invalid byte sequence in US-ASCII This behavior does not seem to be 100% consistent with the puppetral agent. The user saw it affecting 16/29 of their nodes, and I was able to observe it only some of the time on my test instance. It also does not appear to affect the MCollective package agent. I'm thinking it's another manifestation of the issues around
Jira (MCO-165) MCollective rpc puppetral agent sometimes breaks with encoding errors when querying packages
Title: Message Title Ken Johnson updated an issue MCollective / MCO-165 MCollective rpc puppetral agent sometimes breaks with encoding errors when querying packages Change By: Ken Johnson ThiswasfirstreportedasanerrorwithLiveManagement,auserreportedthattheywereseeingadiscrepancybetweenthenumberofnodesreportingagivenpackageinstalleddependingoniftheysearchedwiththe`LiveManagement-AdvancedTasks-package-status`toolorthe`LiveManagement-BrowseResources-package`tool.Iaskedthemtotryrunningthecommandlineequivalentsofthesetwotasks(`mcopackagestatuswget`and`mcorpcpuppetralfindtype=packagetitle=wget`),andtheyobservedthattheoutputofthepuppetralmethodincludedseveralerrorslikethefollowing:pm2.domain.tldUnknownRequestStatusinvalidbytesequenceinUS-ASCIIThisbehaviordoesnotseemtobe100%consistentwiththepuppetralagent.Theusersawitaffecting16/29oftheirnodes,andIwasabletoobserveitonlysomeofthetimeonmytestinstance.ItalsodoesnotappeartoaffecttheMCollectivepackageagent.I'mthinkingit'sanothermanifestationoftheissuesaroundencodingwithRuby1.9.x.Inadditiontodealingwiththeencodingproblem,IthinkthisprobablyalsopointstoaneedtohaveLiveManagementbetterhandleerrorconditions.LiveManagementgavenoindicationofanerroroccurring,itonlyreportedthat13/29nodeshadapackageinstalled,prettymisleadingfromtheuser'sperspective. 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
Jira (MCO-165) MCollective rpc puppetral agent sometimes breaks with encoding errors when querying packages
Title: Message Title Ken Johnson updated an issue MCollective / MCO-165 MCollective rpc puppetral agent sometimes breaks with encoding errors when querying packages Change By: Ken Johnson ThiswasfirstreportedasanerrorwithLiveManagement,auserreportedthattheywereseeingadiscrepancybetweenthenumberofnodesreportingagivenpackageinstalleddependingoniftheysearchedwiththe`LiveManagement-AdvancedTasks-package-status`toolorthe`LiveManagement-BrowseResources-package`tool.Iaskedthemtotryrunningthecommandlineequivalentsofthesetwotasks(`mcopackagestatuswget`and`mcorpcpuppetralfindtype=packagetitle=wget`),andtheyobservedthattheoutputofthepuppetralmethodincludedseveralerrorslikethefollowing:pm2.domain.tldUnknownRequestStatusinvalidbytesequenceinUS-ASCIIThisbehaviordoesnotseemtobe100%consistentwiththepuppetralagent.Theusersawitaffecting16/29oftheirnodes,andIwasabletoobserveitonlysomeofthetimeonmytestinstance.ItalsodoesnotappeartoaffecttheMCollectivepackageagent.I'mthinkingit'sanothermanifestationoftheissuesaroundencodingwithRuby1.9.x. Inadditiontodealingwiththeencodingproblem,IthinkthisprobablyalsopointstoaneedtohaveLiveManagementbetterhandleerrorconditions.LiveManagementgavenoindicationofanerroroccurring,itonlyreportedthat13/29nodeshadapackageinstalled,prettymisleadingfromtheuser'sperspective. 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
Jira (PUP-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Ken Johnson commented on an issue Re: Pre/Post-run commands don't work under Windows With that in mind, shouldn't this be breaking under *nix as well? I found that postrun commands worked fine on my installations on some Linux machines. Add Comment Puppet / PUP-1431 Pre/Post-run commands don't work under Windows If a postrun or prerun command is specified in puppet.conf on a Windows host it will fail to execute with a message like the following: Debug: Executing 'C:\Windows\System32\cmd.exe /c type NUL C:\from_postrun.txt' Error: Could not run command from postrun_command: CreateProcess() failed: The system cannot find the file specified.Example postr... 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-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Ken Johnson created an issue Puppet / PUP-1431 Pre/Post-run commands don't work under Windows Issue Type: Bug Affects Versions: 3.2.4 Assignee: Unassigned Created: 13/Jan/14 1:10 PM Environment: PE 3.0.1 agent, Windows Server 2003 and 2008 x64 Labels: customer Priority: Normal Reporter: Ken Johnson If a postrun or prerun command is specified in puppet.conf on a Windows host it will fail to execute with a message like the following: Debug: Executing 'C:\Windows\System32\cmd.exe /c type NUL C:\from_postrun.txt' Error: Could not run command from postrun_command: CreateProcess() failed: The system cannot find the file specified. Example postrun_command setting: postrun_command=C:\Windows\System32\cmd.exe /c type NUL C:\from_postrun.txt This was reported by a user running Windows Server 2003 and I was able to replicate in 2008 as well. I investigated the cause and it seems like there is something about how
