Jira (PDB-3300) Add command for deleting node data
Title: Message Title Travis Fields commented on PDB-3300 Re: Add command for deleting node data Any update on this ticket? It's been a bit long 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.176102.1487778838000.52444.1565646120584%40Atlassian.JIRA.
Jira (FACT-1354) Facter ec2_userdata handles binary data incorrectly
Title: Message Title Travis Fields commented on FACT-1354 Re: Facter ec2_userdata handles binary data incorrectly That is great for Facter 4 however. This is broken now and the only way to get around is disable ALL EC2 group facts or to ensure we don't use GZIP but would block us from having larger UserData scripts due to EC2 limits. What is the near term fix on this? 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 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 (FACT-1354) Facter ec2_userdata handles binary data incorrectly
Title: Message Title Travis Fields commented on FACT-1354 Re: Facter ec2_userdata handles binary data incorrectly Why is this still a thing? 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 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 (FACT-1354) Facter ec2_userdata handles binary data incorrectly
Title: Message Title Travis Fields commented on FACT-1354 Re: Facter ec2_userdata handles binary data incorrectly Perhaps base64 encode the string first and than decode out the other side 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 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 (BOLT-998) GC_Interval hiera value is now expected to be string
Title: Message Title Travis Fields created an issue Puppet Task Runner / BOLT-998 GC_Interval hiera value is now expected to be string Issue Type: Bug Assignee: Unassigned Created: 2018/11/29 9:53 AM Labels: 2018.1.5 Priority: Normal Reporter: Travis Fields During an upgrade from 2017 to 2018.1.5 we discovered that the hiera value we had set previous, as per recommendation from Support to 0 now has to be "0" puppet_enterprise::profile::puppetdb::gc_interval: 0 Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Class[Puppet_enterprise::Profile::Puppetdb]: parameter 'gc_interval' expects a match for Pattern[/^[0-9]+$/], got Integer on node puppet-compile-master-va2-prd-7.pm.company.com
Jira (FACT-1354) Facter ec2_userdata handles binary data incorrectly
Title: Message Title Travis Fields commented on FACT-1354 Re: Facter ec2_userdata handles binary data incorrectly Any movement on this ticket, it is biting us a bit now. Would prefer to not go down the revert to PSON or fact blocking route. 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 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 (PDB-3871) PE Console fact_x !~ \w+ broken
Title: Message Title Travis Fields updated an issue PuppetDB / PDB-3871 PE Console fact_x !~ \w+ broken Change By: Travis Fields Attachment: Screen Shot 2018-03-08 at 2.27.39 PM.png 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 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 (PDB-3871) PE Console fact_x !~ \w+ broken
Title: Message Title Travis Fields commented on PDB-3871 Re: PE Console fact_x !~ \w+ broken The screen shots are from the exact same cluster, minus the Puppet Infrastructure of course. 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 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 (PDB-3871) PE Console fact_x !~ \w+ broken
Title: Message Title Travis Fields updated an issue PuppetDB / PDB-3871 PE Console fact_x !~ \w+ broken Change By: Travis Fields Attachment: Screen Shot 2018-03-08 at 2.25.03 PM.png 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 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 (PDB-3871) PE Console fact_x !~ \w+ broken
Title: Message Title Travis Fields created an issue PuppetDB / PDB-3871 PE Console fact_x !~ \w+ broken Issue Type: Bug Assignee: Unassigned Components: PuppetDB Created: 2018/03/08 2:26 PM Environment: RHEL 7 boxes Labels: console pe Priority: Normal Reporter: Travis Fields When using the console to try and filter out items that don't have a value for a given fact or an empty string in previous version 2016.4.3 we were able to simple place into the console ` !~ \w+` and it would return this result, presuming that missing the fact also met this criteria, however with 2017.3.4 this does not seem to be the case. Add Comment
Jira (FACT-1164) facter crashes with sqlserver_instances
Title: Message Title Travis Fields created an issue Facter / FACT-1164 facter crashes with sqlserver_instances Issue Type: Bug Assignee: Unassigned Created: 2015/08/18 11:12 AM Priority: Major Reporter: Travis Fields When running facter 3 against sqlserver it will crash after parsing the fact and cause the terminal to become unresponsive. Conversely if the user runs `puppet facts` it all reports without error. Unknown side affects with users running 2015.2 and sqlserver module Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4925) Puppet Agent - Failure to Upgrade Agent on Windows 2003 R2
Title: Message Title Travis Fields updated an issue Puppet / PUP-4925 Puppet Agent - Failure to Upgrade Agent on Windows 2003 R2 Change By: Travis Fields Attachment: ScreenShot2015-07-24at4.28.10PM.png Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4925) Puppet Agent - Failure to Upgrade Agent on Windows 2003 R2
Title: Message Title Travis Fields assigned an issue to Eric Williamson Puppet / PUP-4925 Puppet Agent - Failure to Upgrade Agent on Windows 2003 R2 Change By: Travis Fields Assignee: TravisFields EricWilliamson Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 (FACT-1084) facter network parsing - 8.1
Title: Message Title Travis Fields created an issue Facter / FACT-1084 facter network parsing - 8.1 Issue Type: Bug Assignee: Unassigned Created: 2015/07/01 12:43 PM Environment: Windows 8.1 Hyper-V Installed Virtual Internal Switch Enabled Puppet 4.2.0 Facter 3.0.1 Priority: Normal Reporter: Travis Fields Ethernet adapter vEthernet (intSwitch): Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . :
Jira (FACT-1084) facter network parsing - string parse
Title: Message Title Travis Fields updated an issue Facter / FACT-1084 facter network parsing - string parse Change By: Travis Fields Summary: facternetworkparsing- 8.1 stringparse 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 (FACT-1082) com initialization prior to ruby com initialization
Title: Message Title Travis Fields created an issue Facter / FACT-1082 com initialization prior to ruby com initialization Issue Type: Bug Assignee: Unassigned Created: 2015/06/30 4:13 PM Priority: Major Reporter: Travis Fields [4:01 PM] Ethan J. Brown: it looks like Facter initializes COM in the wmi class (inside Leatherman) at https://github.com/puppetlabs/leatherman/blob/master/windows/src/wmi.cc#L34 [4:01 PM] Ethan J. Brown: CoInitializeEx(0, COINIT_MULTITHREADED) Ruby initializes COM at https://github.com/ruby/ruby/blob/c19d37375074987b36413af6bf83df7262ce227d/ext/win32ole/win32ole.c#L... [4:02 PM] Ethan J. Brown: hr = OleInitialize(NULL);
Jira (FACT-1082) COM initialization prior to ruby COM initialization
Title: Message Title Travis Fields updated an issue Facter / FACT-1082 COM initialization prior to ruby COM initialization Change By: Travis Fields Summary: com COM initializationpriortoruby com COM initialization 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 (FACT-1082) COM initialization prior to ruby COM initialization
Title: Message Title
Travis Fields updated an issue
Facter / FACT-1082
COM initialization prior to ruby COM initialization
Change By:
Travis Fields
OLECOMinitializedpriortoRubycausingissuewithlaterCOMcalls. [SQLSERVERInstancesFact|https://github.com/puppetlabs/puppetlabs-sqlserver/blob/master/lib/facter/sqlserver_instances.rb] [sqlserverolecalls|https://github.com/puppetlabs/puppetlabs-sqlserver/blob/master/lib/puppet_x/sqlserver/features.rb#L21] {noformat}[4:01PM]EthanJ.Brown:itlookslikeFacterinitializesCOMinthewmiclass(insideLeatherman)athttps://github.com/puppetlabs/leatherman/blob/master/windows/src/wmi.cc#L34[4:01PM]EthanJ.Brown:CoInitializeEx(0,COINIT_MULTITHREADED) RubyinitializesCOMathttps://github.com/ruby/ruby/blob/c19d37375074987b36413af6bf83df7262ce227d/ext/win32ole/win32ole.c#L...[4:02PM]EthanJ.Brown:hr=OleInitialize(NULL); soifyoucallPuppet-Facter,everythingisOK[4:02PM]MichaelSmith:ohsinglevsmultithreaded?[4:02PM]EthanJ.Brown:howeverifyoucallinthereversetoresolveacustomfact thenbarf[4:03PM]EthanJ.Brown:OleInitializecallsCoInitializeExinternallytoinitializetheCOMlibraryonthecurrentapartment.BecauseOLEoperationsarenotthread-safe,OleInitializespecifiestheconcurrencymodelassingle-threadapartment. Oncetheconcurrencymodelforanapartmentisset,itcannotbechanged.AcalltoOleInitializeonanapartmentthatwaspreviouslyinitializedasmultithreadedwillfailandreturnRPC_E_CHANGED_MODE. https://msdn.microsoft.com/en-us/library/windows/desktop/ms690134(v=vs.85).aspx[4:04PM]MichaelSmith:yeah,soweacceptthatitmight'vebeeninitializedwithsingle-threaded,butrubyerrorsout soIguesswehavetoinitializeapartmentthreaded?ugh Wecoulddosoonlywhenloadedinruby... Wait,I'mstillnotsurehowthathappens.[4:06PM]TravisFields:itiswhencfacteriscalledpriortoruby,ifpuppetiscalledfirstthefactthatisreturnediscorrectwithnoerrors[4:06PM]EthanJ.Brown:theoutputfromTravisisathttps://gist.github.com/cyberious/52410266b650afd94b59[4:06PM]PeterHuene:facterinitializesCOMthentriestoresolveacustomfactthatusesruby'sCOMsupport sincerubydoesn'thandleRPC_E_CHANGED_MODEitseems,boom[4:07PM]EthanJ.Brown:correct[4:07PM]MichaelSmith:ok,sowejusthavetoalwaysusesingle-threaded. Well,wedon'tmulti-threadqueriestoCOMyet,soshouldn'tcauseanyissuestochange.{noformat}
Add Comment
Jira (FACT-1082) COM initialization prior to ruby COM initialization
Title: Message Title
Travis Fields updated an issue
Facter / FACT-1082
COM initialization prior to ruby COM initialization
Change By:
Travis Fields
OLECOMinitializedpriortoRubycausingissuewithlaterCOMcalls. {noformat}[4:01PM]EthanJ.Brown:itlookslikeFacterinitializesCOMinthewmiclass(insideLeatherman)athttps://github.com/puppetlabs/leatherman/blob/master/windows/src/wmi.cc#L34[4:01PM]EthanJ.Brown:CoInitializeEx(0,COINIT_MULTITHREADED) RubyinitializesCOMathttps://github.com/ruby/ruby/blob/c19d37375074987b36413af6bf83df7262ce227d/ext/win32ole/win32ole.c#L...[4:02PM]EthanJ.Brown:hr=OleInitialize(NULL); soifyoucallPuppet-Facter,everythingisOK[4:02PM]MichaelSmith:ohsinglevsmultithreaded?[4:02PM]EthanJ.Brown:howeverifyoucallinthereversetoresolveacustomfact thenbarf[4:03PM]EthanJ.Brown:OleInitializecallsCoInitializeExinternallytoinitializetheCOMlibraryonthecurrentapartment.BecauseOLEoperationsarenotthread-safe,OleInitializespecifiestheconcurrencymodelassingle-threadapartment. Oncetheconcurrencymodelforanapartmentisset,itcannotbechanged.AcalltoOleInitializeonanapartmentthatwaspreviouslyinitializedasmultithreadedwillfailandreturnRPC_E_CHANGED_MODE. https://msdn.microsoft.com/en-us/library/windows/desktop/ms690134(v=vs.85).aspx[4:04PM]MichaelSmith:yeah,soweacceptthatitmight'vebeeninitializedwithsingle-threaded,butrubyerrorsout soIguesswehavetoinitializeapartmentthreaded?ugh Wecoulddosoonlywhenloadedinruby... Wait,I'mstillnotsurehowthathappens.[4:06PM]TravisFields:itiswhencfacteriscalledpriortoruby,ifpuppetiscalledfirstthefactthatisreturnediscorrectwithnoerrors[4:06PM]EthanJ.Brown:theoutputfromTravisisathttps://gist.github.com/cyberious/52410266b650afd94b59[4:06PM]PeterHuene:facterinitializesCOMthentriestoresolveacustomfactthatusesruby'sCOMsupport sincerubydoesn'thandleRPC_E_CHANGED_MODEitseems,boom[4:07PM]EthanJ.Brown:correct[4:07PM]MichaelSmith:ok,sowejusthavetoalwaysusesingle-threaded. Well,wedon'tmulti-threadqueriestoCOMyet,soshouldn'tcauseanyissuestochange.{noformat}
Add Comment
This message was
Jira (PUP-4479) Extend upgrade module to windows
Title: Message Title Travis Fields assigned an issue to Rob Reynolds Puppet / PUP-4479 Extend upgrade module to windows Change By: Travis Fields Assignee: RobReynolds 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-4479) Extend upgrade module to windows
Title: Message Title Travis Fields assigned an issue to Rob Reynolds Puppet / PUP-4479 Extend upgrade module to windows Change By: Travis Fields Assignee: RobReynolds 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-4479) Extend upgrade module to windows
Title: Message Title Travis Fields assigned an issue to Rob Reynolds Puppet / PUP-4479 Extend upgrade module to windows Change By: Travis Fields Assignee: RobReynolds 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-4479) Extend upgrade module to windows
Title: Message Title Travis Fields commented on PUP-4479 Re: Extend upgrade module to windows Kylo Ginsberg can we assume that we are going to be upgrading to the versions that exist in https://downloads.puppetlabs.com/windows for the puppet-agent latest version? 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-4479) Extend upgrade module to windows
Title: Message Title Travis Fields commented on PUP-4479 Re: Extend upgrade module to windows Thanks, Rob Reynolds we already specified this, but need a default location. going to allow source of puppet:// as a possible location. 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-4479) Extend upgrade module to windows
Title: Message Title Travis Fields commented on PUP-4479 Re: Extend upgrade module to windows So per conversation thread, 2003SP2 is oldest version to support and we are requiring the user to have PowerShell installed, as there are server core installs that do not come with PowerShell installed by default. 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-4479) Extend upgrade module to windows
Title: Message Title Travis Fields commented on PUP-4479 Re: Extend upgrade module to windows Rob Reynolds what service pack did powershell get included into 2003 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-4177) Document Windows testing and development using our puppet console
Title: Message Title Travis Fields assigned an issue to Travis Fields Puppet / PUP-4177 Document Windows testing and development using our puppet console Change By: Travis Fields Assignee: TravisFields Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-400) Manage hidden windows packages
Title: Message Title Travis Fields commented on PUP-400 Re: Manage hidden windows packages Can we just remove these lines? https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/windows/msi_package.rb#L35-L36 https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/windows/exe_package.rb#L23-L24 Or do we want to package provider a property for hidden = false or true? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-400) Manage hidden windows packages
Title: Message Title Travis Fields commented on PUP-400 Re: Manage hidden windows packages Created a PR that might and await the feedback loop if we decide to go a different route. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4177) Document Windows testing and development using our puppet console
Title: Message Title Travis Fields created an issue Puppet / PUP-4177 Document Windows testing and development using our puppet console Issue Type: Task Assignee: Travis Fields Components: Windows Created: 2015/03/10 12:15 PM Priority: Major Reporter: Travis Fields Provide documentation and gotcha's discovered during investigation of PUP-3782 Add Comment
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title
Travis Fields commented on PUP-3782
Re: modules on windows cannot run rake tasks to run unit tests
Here is a quick effort but requires puppet to first be installed.
include chocolatey_sw
Package{ provider = chocolatey }
package{ ['git','ruby']: }
package{ 'ruby2.devkit': } #not sure if really needed
pget{ 'rubySSLCert':
source = 'https://raw.githubusercontent.com/rubygems/rubygems/master/lib/rubygems/ssl_certs/AddTrustExternalCARoot-2048.pem',
target = 'C;\tools\ruby215\lib\ruby\2.1.0\rubygems\ssl_certs',
}
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Travis Fields commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests Hi Corey Osman and I noticed one thing, when I pinned the rspec version back to 2.x it went through although with failures. This was on a fresh install of PE 3.7.2 but you can see it was executing puppet 3.7.4 from the gem dependency. output Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Travis Fields updated an issue Puppet / PUP-3782 modules on windows cannot run rake tasks to run unit tests Change By: Travis Fields Sprint: MODS2015- 03 02 - 18 04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Travis Fields updated an issue Puppet / PUP-3782 modules on windows cannot run rake tasks to run unit tests Change By: Travis Fields Sprint: MODS2015-03-18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Travis Fields updated an issue Puppet / PUP-3782 modules on windows cannot run rake tasks to run unit tests Change By: Travis Fields Scrum Team: Windows Modules Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Travis Fields updated an issue Puppet / PUP-3782 modules on windows cannot run rake tasks to run unit tests Change By: Travis Fields Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (FACT-752) External powershell Facts are executed on unix hosts
Title: Message Title Travis Fields commented on FACT-752 Re: External powershell Facts are executed on unix hosts What if the user has PASH installed? Do we want to hard code these not executing? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3597) Thrown Exception when trying to use lookup var with FutureParser and strict variables
Title: Message Title Travis Fields created an issue Puppet / PUP-3597 Thrown Exception when trying to use lookup var with FutureParser and strict variables Issue Type: Bug Assignee: Unassigned Created: 30/Oct/14 5:43 PM Priority: Major Reporter: Travis Fields Using lookupvar within a function is throwing an evaluation error and not properly throwing Puppet::Error Error: Evaluation Error: Error while evaluating a Function Call, uncaught throw :undefined_variable at /Users/travisfields/repos/puppetlabs/stdlib/network_test.pp:2:4 on node traviss-mbp.delivery.puppetlabs.net /Library/Ruby/Site/puppet/parser/scope.rb:405:in `throw' /Library/Ruby/Site/puppet/parser/scope.rb:405:in `variable_not_found' /Library/Ruby/Site/puppet/parser/scope.rb:397:in `lookupvar'
Jira (PUP-3597) Thrown Symbol when trying to use lookup var with FutureParser and strict variables
Title: Message Title
Travis Fields commented on an issue
Re: Thrown Symbol when trying to use lookup var with FutureParser and strict variables
[5:45 PM] Adrien Thebo: @travisf mostly, Puppet isn't using exception - it's throwing a symbol and doesn't catch it
Add Comment
Puppet / PUP-3597
Thrown Symbol when trying to use lookup var with FutureParser and strict variables
Using lookupvar within a function is throwing an evaluation error and not properly throwing Puppet::Error Example usage [STDLIB has_interface_with|https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/lib/puppet/parser/functions/has_interface_with.rb#L48] {code} Error: Evaluation Error: Error while evaluating a Function Call, uncaught throw :un...
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
Jira (PUP-3597) Thrown Exception when trying to use lookup var with FutureParser and strict variables
Title: Message Title
Travis Fields updated an issue
Puppet / PUP-3597
Thrown Exception when trying to use lookup var with FutureParser and strict variables
Change By:
Travis Fields
UsinglookupvarwithinafunctionisthrowinganevaluationerrorandnotproperlythrowingPuppet::Error Exampleusage[STDLIBhas_interface_with|https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/lib/puppet/parser/functions/has_interface_with.rb#L48] {code}Error:EvaluationError:ErrorwhileevaluatingaFunctionCall,uncaughtthrow:undefined_variableat/Users/travisfields/repos/puppetlabs/stdlib/network_test.pp:2:4onnodetraviss-mbp.delivery.puppetlabs.net/Library/Ruby/Site/puppet/parser/scope.rb:405:in`throw'/Library/Ruby/Site/puppet/parser/scope.rb:405:in`variable_not_found'/Library/Ruby/Site/puppet/parser/scope.rb:397:in`lookupvar'/Users/travisfields/.puppet/modules/stdlib/lib/puppet/parser/functions/has_interface_with.rb:38:in`blockinmodule:Functions'/Library/Ruby/Site/puppet/parser/functions.rb:164:in`block(2levels)innewfunction'/Library/Ruby/Site/puppet/util/profiler/around_profiler.rb:58:in`profile'/Library/Ruby/Site/puppet/util/profiler.rb:51:in`profile'/Library/Ruby/Site/puppet/parser/functions.rb:157:in`blockinnewfunction'/Users/travisfields/.puppet/modules/stdlib/lib/puppet/parser/functions/has_ip_network.rb:20:in`blockinmodule:Functions'/Library/Ruby/Site/puppet/parser/functions.rb:164:in`block(2levels)innewfunction'/Library/Ruby/Site/puppet/util/profiler/around_profiler.rb:58:in`profile'/Library/Ruby/Site/puppet/util/profiler.rb:51:in`profile'/Library/Ruby/Site/puppet/parser/functions.rb:157:in`blockinnewfunction'/Library/Ruby/Site/puppet/pops/evaluator/runtime3_support.rb:248:in`call_function'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:785:in`eval_CallNamedFunctionExpression'/Library/Ruby/Site/puppet/pops/visitor.rb:43:in`blockinvisit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`each'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`visit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:66:in`visit_this_1'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:77:in`evaluate'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:857:in`blockineval_IfExpression'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:1090:in`with_guarded_scope'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:856:in`eval_IfExpression'/Library/Ruby/Site/puppet/pops/visitor.rb:43:in`blockinvisit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`each'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`visit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:66:in`visit_this_1'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:77:in`evaluate'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:521:in`blockineval_BlockExpression'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:521:in`each'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:521:in`eval_BlockExpression'/Library/Ruby/Site/puppet/pops/visitor.rb:43:in`blockinvisit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`each'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`visit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:66:in`visit_this_1'{code}
Jira (PUP-3597) Thrown Symbol when trying to use lookup var with FutureParser and strict variables
Title: Message Title Travis Fields updated an issue Puppet / PUP-3597 Thrown Symbol when trying to use lookup var with FutureParser and strict variables Change By: Travis Fields Summary: Thrown Exception Symbol whentryingtouselookupvarwithFutureParserandstrictvariables 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/d/optout.
Jira (PUP-3597) Thrown Symbol when trying to use lookup var with FutureParser and strict variables
Title: Message Title
Travis Fields updated an issue
Puppet / PUP-3597
Thrown Symbol when trying to use lookup var with FutureParser and strict variables
Change By:
Travis Fields
UsinglookupvarwithinafunctionisthrowinganevaluationerrorandnotproperlythrowingPuppet::ErrorExampleusage[STDLIBhas_interface_with|https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/lib/puppet/parser/functions/has_interface_with.rb#L48] Errororiginatesat[Scope.lookupvar|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/parser/scope.rb#L404-L406] {code}Error:EvaluationError:ErrorwhileevaluatingaFunctionCall,uncaughtthrow:undefined_variableat/Users/travisfields/repos/puppetlabs/stdlib/network_test.pp:2:4onnodetraviss-mbp.delivery.puppetlabs.net/Library/Ruby/Site/puppet/parser/scope.rb:405:in`throw'/Library/Ruby/Site/puppet/parser/scope.rb:405:in`variable_not_found'/Library/Ruby/Site/puppet/parser/scope.rb:397:in`lookupvar'/Users/travisfields/.puppet/modules/stdlib/lib/puppet/parser/functions/has_interface_with.rb:38:in`blockinmodule:Functions'/Library/Ruby/Site/puppet/parser/functions.rb:164:in`block(2levels)innewfunction'/Library/Ruby/Site/puppet/util/profiler/around_profiler.rb:58:in`profile'/Library/Ruby/Site/puppet/util/profiler.rb:51:in`profile'/Library/Ruby/Site/puppet/parser/functions.rb:157:in`blockinnewfunction'/Users/travisfields/.puppet/modules/stdlib/lib/puppet/parser/functions/has_ip_network.rb:20:in`blockinmodule:Functions'/Library/Ruby/Site/puppet/parser/functions.rb:164:in`block(2levels)innewfunction'/Library/Ruby/Site/puppet/util/profiler/around_profiler.rb:58:in`profile'/Library/Ruby/Site/puppet/util/profiler.rb:51:in`profile'/Library/Ruby/Site/puppet/parser/functions.rb:157:in`blockinnewfunction'/Library/Ruby/Site/puppet/pops/evaluator/runtime3_support.rb:248:in`call_function'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:785:in`eval_CallNamedFunctionExpression'/Library/Ruby/Site/puppet/pops/visitor.rb:43:in`blockinvisit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`each'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`visit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:66:in`visit_this_1'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:77:in`evaluate'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:857:in`blockineval_IfExpression'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:1090:in`with_guarded_scope'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:856:in`eval_IfExpression'/Library/Ruby/Site/puppet/pops/visitor.rb:43:in`blockinvisit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`each'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`visit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:66:in`visit_this_1'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:77:in`evaluate'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:521:in`blockineval_BlockExpression'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:521:in`each'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:521:in`eval_BlockExpression'/Library/Ruby/Site/puppet/pops/visitor.rb:43:in`blockinvisit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`each'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`visit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:66:in`visit_this_1'{code}
Jira (PUP-3597) Thrown Symbol when trying to use lookup var with FutureParser and strict variables
Title: Message Title
Travis Fields updated an issue
Puppet / PUP-3597
Thrown Symbol when trying to use lookup var with FutureParser and strict variables
Change By:
Travis Fields
UsinglookupvarwithinafunctionisthrowinganevaluationerrorandnotproperlythrowingPuppet::ErrorExampleusage[STDLIBhas_interface_with|https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/lib/puppet/parser/functions/has_interface_with.rb#L48]Errororiginatesat[Scope. lookupvar variable_not_found |https://github.com/puppetlabs/puppet/blob/master/lib/puppet/parser/scope.rb#L404-L406]{code}Error:EvaluationError:ErrorwhileevaluatingaFunctionCall,uncaughtthrow:undefined_variableat/Users/travisfields/repos/puppetlabs/stdlib/network_test.pp:2:4onnodetraviss-mbp.delivery.puppetlabs.net/Library/Ruby/Site/puppet/parser/scope.rb:405:in`throw'/Library/Ruby/Site/puppet/parser/scope.rb:405:in`variable_not_found'/Library/Ruby/Site/puppet/parser/scope.rb:397:in`lookupvar'/Users/travisfields/.puppet/modules/stdlib/lib/puppet/parser/functions/has_interface_with.rb:38:in`blockinmodule:Functions'/Library/Ruby/Site/puppet/parser/functions.rb:164:in`block(2levels)innewfunction'/Library/Ruby/Site/puppet/util/profiler/around_profiler.rb:58:in`profile'/Library/Ruby/Site/puppet/util/profiler.rb:51:in`profile'/Library/Ruby/Site/puppet/parser/functions.rb:157:in`blockinnewfunction'/Users/travisfields/.puppet/modules/stdlib/lib/puppet/parser/functions/has_ip_network.rb:20:in`blockinmodule:Functions'/Library/Ruby/Site/puppet/parser/functions.rb:164:in`block(2levels)innewfunction'/Library/Ruby/Site/puppet/util/profiler/around_profiler.rb:58:in`profile'/Library/Ruby/Site/puppet/util/profiler.rb:51:in`profile'/Library/Ruby/Site/puppet/parser/functions.rb:157:in`blockinnewfunction'/Library/Ruby/Site/puppet/pops/evaluator/runtime3_support.rb:248:in`call_function'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:785:in`eval_CallNamedFunctionExpression'/Library/Ruby/Site/puppet/pops/visitor.rb:43:in`blockinvisit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`each'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`visit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:66:in`visit_this_1'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:77:in`evaluate'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:857:in`blockineval_IfExpression'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:1090:in`with_guarded_scope'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:856:in`eval_IfExpression'/Library/Ruby/Site/puppet/pops/visitor.rb:43:in`blockinvisit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`each'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`visit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:66:in`visit_this_1'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:77:in`evaluate'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:521:in`blockineval_BlockExpression'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:521:in`each'/Library/Ruby/Site/puppet/pops/evaluator/evaluator_impl.rb:521:in`eval_BlockExpression'/Library/Ruby/Site/puppet/pops/visitor.rb:43:in`blockinvisit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`each'/Library/Ruby/Site/puppet/pops/visitor.rb:39:in`visit_this'/Library/Ruby/Site/puppet/pops/visitor.rb:66:in`visit_this_1'{code}
Jira (PUP-3561) Puppet::Util::Windows::Execute leaks Win32::Process exception when it fails
Title: Message Title Travis Fields created an issue Puppet / PUP-3561 Puppet::Util::Windows::Execute leaks Win32::Process exception when it fails Issue Type: Bug Assignee: Unassigned Created: 28/Oct/14 5:18 PM Priority: Normal Reporter: Travis Fields When using validate_cmd on a windows box against Puppet 3.7+ it will leak the exception thrown by Win32::Process instead of throwing the Puppet::ExecutionFailure error we throw for other systems. https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/process.rb#L12 https://github.com/puppetlabs/puppetlabs-stdlib/pull/348/files has example of when this is done Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3561) Puppet::Util::Windows::Process.execute leaks Win32::Process exception when it fails
Title: Message Title Travis Fields updated an issue Puppet / PUP-3561 Puppet::Util::Windows::Process.execute leaks Win32::Process exception when it fails Change By: Travis Fields Summary: Puppet::Util::Windows:: Execute Process.execute leaksWin32::Processexceptionwhenitfails 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/d/optout.
Jira (PUP-3561) Puppet::Util::Windows::Process.execute leaks Win32::Process exception when it fails
Title: Message Title Travis Fields commented on an issue Re: Puppet::Util::Windows::Process.execute leaks Win32::Process exception when it fails Added link to possible PR using same exception using Puppet::Util::Windows::Error Add Comment Puppet / PUP-3561 Puppet::Util::Windows::Process.execute leaks Win32::Process exception when it fails When using validate_cmd on a windows box against Puppet 3.7+ it will leak the exception thrown by Win32::Process instead of throwing the Puppet::ExecutionFailure error we throw for other systems. https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/process.rb#L12 https://github.com/puppetlabs/puppetlabs-stdlib/pull/348/files has ex... 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-3442) Receiving errors when trying to install modules via PMT due to SSL issue.
Title: Message Title
Travis Fields commented on an issue
Re: Receiving errors when trying to install modules via PMT due to SSL issue.
SLES 12 having same issue now.
Notice: Downloading from https://forgeapi.puppetlabs.com ... Error: Could not connect via HTTPS to https://forgeapi.puppetlabs.com Unable to verify the SSL certificate The certificate may not be signed by a valid CA The CA bundle included with OpenSSL may not be valid or up to date j7ayjmn8wcppzfg:~ #
Add Comment
Puppet / PUP-3442
Receiving errors when trying to install modules via PMT due to SSL issue.
{panel} Notice: Downloading from https://forgeapi.puppetlabs.com ... Error: Could not connect via HTTPS to https://forgeapi.puppetlabs.com Unable to verify the SSL certificate The certificate may not be signed by a valid CA The CA bundle included with OpenSSL may not be valid or up to date {panel} Fresh install of Puppet 3.7.1 from downlo...
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
Jira (PUP-3442) Receiving errors when trying to install modules via PMT due to SSL issue.
Title: Message Title Travis Fields moved an issue Puppet / PUP-3442 Receiving errors when trying to install modules via PMT due to SSL issue. Change By: Travis Fields Workflow: QualityEngineering Platform Workflow Key: QENG PUP - 1367 3442 Project: QualityEngineering Puppet 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/d/optout.
Jira (PUP-3442) Receiving errors when trying to install modules via PMT due to SSL issue.
Title: Message Title Travis Fields updated an issue Puppet / PUP-3442 Receiving errors when trying to install modules via PMT due to SSL issue. Change By: Travis Fields Assignee: QE 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/d/optout.
Jira (PUP-3442) Receiving errors when trying to install modules via PMT due to SSL issue.
Title: Message Title Travis Fields updated an issue Puppet / PUP-3442 Receiving errors when trying to install modules via PMT due to SSL issue. Change By: Travis Fields code Notice:Downloadingfromhttps://forgeapi.puppetlabs.com...Error:CouldnotconnectviaHTTPStohttps://forgeapi.puppetlabs.comUnabletoverifytheSSLcertificateThecertificatemaynotbesignedbyavalidCATheCAbundleincludedwithOpenSSLmaynotbevalidoruptodate OnlyworksaftergoingtositeviaIE, /codeFreshinstallof Puppet3.7.1 fromdownloads.puppetlabs.com/windows/RunningagainstWindows2012Server 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/d/optout.
Jira (PUP-3442) Receiving errors when trying to install modules via PMT due to SSL issue.
Title: Message Title
Travis Fields updated an issue
Puppet / PUP-3442
Receiving errors when trying to install modules via PMT due to SSL issue.
Change By:
Travis Fields
code {panel} Notice:Downloadingfromhttps://forgeapi.puppetlabs.com...Error:CouldnotconnectviaHTTPStohttps://forgeapi.puppetlabs.comUnabletoverifytheSSLcertificateThecertificatemaynotbesignedbyavalidCATheCAbundleincludedwithOpenSSLmaynotbevalidoruptodate /code {panel} FreshinstallofPuppet3.7.1fromdownloads.puppetlabs.com/windows/RunningagainstWindows2012Server
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/d/optout.
Jira (PUP-3442) Receiving errors when trying to install modules via PMT due to SSL issue.
Title: Message Title Travis Fields commented on an issue Re: Receiving errors when trying to install modules via PMT due to SSL issue. I have further tested that by simply issuing any web request that follows the same authentication path on windows system such as Invoke-WebRequest from within Powershell to Https://forge.puppetlabs.com the future request then again become valid. PS C:\Users\Administrator puppet module install cyberious/windows_java Notice: Preparing to install into C:/ProgramData/PuppetLabs/puppet/etc/modules ... Notice: Created target directory C:/ProgramData/PuppetLabs/puppet/etc/modules Notice: Downloading from https://forgeapi.puppetlabs.com ... Error: Could not connect via HTTPS to https://forgeapi.puppetlabs.com Unable to verify the SSL certificate The certificate may not be signed by a valid CA The CA bundle included with OpenSSL may not be valid or up to date PS C:\Users\Administrator Invoke-WebRequest https://forgeapi.puppetlabs.com
Jira (PUP-3131) Registry not reading back proper value for binary.
Title: Message Title
Travis Fields created an issue
Puppet / PUP-3131
Registry not reading back proper value for binary.
Issue Type:
Bug
Assignee:
Unassigned
Created:
22/Aug/14 4:01 PM
Priority:
Major
Reporter:
Travis Fields
Query truncates after 14 characters Notice: /Stage[main]/Main/Registry_value[HKLM\SOFTWARE\Puppet Labs\Puppet\SubKey1\ValueBinary2]/data: data changed 'de b e ef ca' to 'de ad be ef ca f2'
also case sensitive. registry_value { 'HKLM\SOFTWARE\Puppet Labs\Puppet\SubKey1\ValueBinary2': type = binary, data ="" DE AD BE EF CA }
Notice: /Stage[main]/Main/Registry_value[HKLM\SOFTWARE\Puppet Labs\Puppet\SubKey1\ValueBinary2]/data: data changed 'de b e ef ca' to 'de ad be ef ca'
– Never loaded last bit despite it was present Notice: /Stage[main]/Main/Registry_value[HKLM\SOFTWARE\Puppet Labs\Puppet\SubKey1\ValueBinary2]/data: data changed 'de b e ef' to 'de ad be ef ca f2'
Add Comment
