Jira (PUP-2984) MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
Title: Message Title
Rob Reynolds commented on an issue
Re: MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
Ethan Brown
Custom paths used in previous installs aren't remembered anymore. If I used c:\foo for x86, then install x64, then install x86 again, it should have remembered c:\foo from the last x86 install. This is important when there may have been local file modifications inside of the custom path (that wouldn't have been removed during an uninstall)
The original trend that we were going to was to use a different default path, which meant two different places in the registry for x86 versus x64 when it comes to remembered installation directory. The work put in for
PUP-390
reflects this in https://github.com/ferventcoder/puppet_for_the_win/commit/99500d62bc8e703cff2c070a1cab19d9c80dcc22. I think this was done so we could override the default C:\Program Files (x86) when installing x64, however it has the side effect of never remembering the previous installation directory when changing architectures. Perhaps we can find a way to have both.
Add Comment
Puppet / PUP-2984
MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec. It also doesn't remove the older path - this is what remains after install of x86 AFTER x64: {{C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files (x86)\Puppet Labs\Puppet\bin}} and it should be {{C:\Program Files (x...
Jira (PUP-3127) LDAP - introduce LDAP-Certificat Directory
Title: Message Title Andreas Schuster created an issue Puppet / PUP-3127 LDAP - introduce LDAP-Certificat Directory Issue Type: Improvement Affects Versions: 3.2.4 Assignee: Andreas Schuster Components: Server Created: 22/Aug/14 6:29 AM Environment: Solaris 11, SPARC, x86 Fix Versions: 3.7.1 Labels: ldap ldapcert solaris Priority: Normal Reporter: Andreas Schuster Original Estimate: 2 days
Jira (PUP-3127) LDAP - introduce LDAP-Certificat Directory
Title: Message Title Andreas Schuster updated an issue Puppet / PUP-3127 LDAP - introduce LDAP-Certificat Directory Change By: Andreas Schuster Issue Type: Improvement NewFeature 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-3128) Pacman provider does not work on manjaro linux
Title: Message Title Dawn Foster moved an issue Puppet / PUP-3128 Pacman provider does not work on manjaro linux Change By: Dawn Foster Workflow: Engineering Platform Workflow Key: ASK PUP - 54 3128 Project: AskWebsite 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-3128) Pacman provider does not work on manjaro linux
Title: Message Title Dawn Foster commented on an issue Re: Pacman provider does not work on manjaro linux This was incorrectly filed in the ask.puppetlabs.com website project. Moved it to the puppet project for triage. Add Comment Puppet / PUP-3128 Pacman provider does not work on manjaro linux When applying a manifest on a manjaro linux machine you obtain this error: Error: /Package[dnsmasq]: Provider pacman is not functional on this host If someone fixes it before I do, I believe the issue is the line confine :operatingsystem = :archlinux in pacman.rb The output from facter on my machine is: operatingsystem = Linux operatingsyst... 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-3128) Pacman provider does not work on manjaro linux
Title: Message Title Tim Spence commented on an issue Re: Pacman provider does not work on manjaro linux Apologies. See https://github.com/puppetlabs/puppet/pull/3003 and https://github.com/puppetlabs/facter/pull/770 for proposed fix. Add Comment Puppet / PUP-3128 Pacman provider does not work on manjaro linux When applying a manifest on a manjaro linux machine you obtain this error: Error: /Package[dnsmasq]: Provider pacman is not functional on this host If someone fixes it before I do, I believe the issue is the line confine :operatingsystem = :archlinux in pacman.rb The output from facter on my machine is: operatingsystem = Linux operatingsyst... 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-406) Deprecate stringify_fact = true
Title: Message Title Kylo Ginsberg commented on an issue Re: Deprecate stringify_fact = true No FR needed. Docs only and Nick gave it a thumbs-up. Add Comment Puppet / PUP-406 Deprecate stringify_fact = true Erik Dalen's patch that allows turning off the stringification of facts by puppet opens the door to structured facts. In 3.x that settings was to still stringify by default, in 4.0.0 it needs to be changed to *not* stringify by default and to issue a deprecation warning when it is set to stringify. The reason for the deprecation and not complete removal ... 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-586) Deprecate Instrumentation system
Title: Message Title Kylo Ginsberg commented on an issue Re: Deprecate Instrumentation system No FR needed. Docs only and Nick gave it a thumbs-up. Add Comment Puppet / PUP-586 Deprecate Instrumentation system This is a little known, and never used, instrumentation system in puppet. It was added for #9584, but has not been found useful for any of the work that we have done since then. Rather than having this code remain in the codebase and incur a maintenance cost, we should deprecate it and remove it in the next major release of puppet. 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-2631) Running the puppet agent against a nonexistent environment produces an overly verbose error message.
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2631 Running the puppet agent against a nonexistent environment produces an overly verbose error message. Change By: Kurt Wall QA Status: Reviewed 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-2631) Running the puppet agent against a nonexistent environment produces an overly verbose error message.
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-2631 Running the puppet agent against a nonexistent environment produces an overly verbose error message. Change By: Michael Smith Assignee: MichaelSmith 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-3030) Resolve Tempfile handling issues
Title: Message Title Kurt Wall commented on an issue Re: Resolve Tempfile handling issues PAWmvg passed last night (). Are the failures Josh linked fixed? Add Comment Puppet / PUP-3030 Resolve Tempfile handling issues See linked PE ticket; I will add a more precise description of the work needed here once we've gotten a bit further in investigating our options, but just wanted to get a 3.7.0 ticket in place because I do think some change will be needed before then. The gist of the issue is that the `Tempfile` class may not behave well in long-running JRuby processes... 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-3030) Resolve Tempfile handling issues
Title: Message Title Eric Thompson commented on an issue Re: Resolve Tempfile handling issues this appears to be spec level? anyone have concerns with pulling this through? Add Comment Puppet / PUP-3030 Resolve Tempfile handling issues See linked PE ticket; I will add a more precise description of the work needed here once we've gotten a bit further in investigating our options, but just wanted to get a 3.7.0 ticket in place because I do think some change will be needed before then. The gist of the issue is that the `Tempfile` class may not behave well in long-running JRuby processes... 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-3030) Resolve Tempfile handling issues
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3030 Resolve Tempfile handling issues Change By: Eric Thompson QA Contact: EricThompson QA Status: Reviewed 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-3032) Setting to cache `load_library` failures
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3032 Setting to cache `load_library` failures Change By: Eric Thompson QA Contact: EricThompson QA Status: Reviewed 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-3032) Setting to cache `load_library` failures
Title: Message Title Eric Thompson commented on an issue Re: Setting to cache `load_library` failures looks like spec level. anyone concerned with pulling this through to resolved? Add Comment Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... 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-2914) Update packages to use RGen 0.7.0
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2914 Update packages to use RGen 0.7.0 Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed 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-2913) Remove RGen Gem in Puppet-Win32-Ruby libraries
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2913 Remove RGen Gem in Puppet-Win32-Ruby libraries Change By: Eric Thompson QA Status: Reviewed 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-2913) Remove RGen Gem in Puppet-Win32-Ruby libraries
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2913 Remove RGen Gem in Puppet-Win32-Ruby libraries Change By: Eric Thompson QA Contact: EricThompson 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-1044) FileBucket should not keep files in memory
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1044 FileBucket should not keep files in memory Change By: Eric Thompson QA Contact: EricThompson QA Status: Reviewed 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-1044) FileBucket should not keep files in memory
Title: Message Title Eric Thompson commented on an issue Re: FileBucket should not keep files in memory this looks like spec level can cover. anyone have concerns with pulling this through FR to resolved? Add Comment Puppet / PUP-1044 FileBucket should not keep files in memory It should not be necessary to load entire files into memory to checksum them. 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-3040) Change init/upstart instance-based services from blacklist to whitelist
Title: Message Title Reid Vandewiele commented on an issue Re: Change init/upstart instance-based services from blacklist to whitelist It seems to me that blacklist/whitelist is triage, not resolution, regardless of which you pick. A resolution would be to prescribe a means of specifying a particular service instance in the service type. The failed use case is the ability to specify instance-based services as resources, one resource per service instance. Is there an existing ticket to track that kind of resolution? Add Comment Puppet / PUP-3040 Change init/upstart instance-based services from blacklist to whitelist 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-3030) Resolve Tempfile handling issues
Title: Message Title Josh Cooper commented on an issue Re: Resolve Tempfile handling issues Windows acceptance failures are resolved with Henrik Lindberg's latest changes: https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-master-vcloud-and-github/403/ +1 to moving to resolved Add Comment Puppet / PUP-3030 Resolve Tempfile handling issues See linked PE ticket; I will add a more precise description of the work needed here once we've gotten a bit further in investigating our options, but just wanted to get a 3.7.0 ticket in place because I do think some change will be needed before then. The gist of the issue is that the `Tempfile` class may not behave well in long-running JRuby processes... 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
Jira (PUP-2999) Merge clay-davis branch of FOSS puppet into upstream repository.
Title: Message Title Kylo Ginsberg commented on an issue Re: Merge clay-davis branch of FOSS puppet into upstream repository. Clean run with beaker 1.17.5. No need for FR so resolving. Add Comment Puppet / PUP-2999 Merge clay-davis branch of FOSS puppet into upstream repository. We need to be pulling acceptance tests directly from FOSS puppet repository and should not be worrying about synchronizing our branch with minimal changes with upstream. 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-1044) FileBucket should not keep files in memory
Title: Message Title Henrik Lindberg commented on an issue Re: FileBucket should not keep files in memory There is no new / altered functionality. Measuring that it uses less memory is very difficult in practice. It is possible to assert that it uses the new method by turning on verbose output when doing filebucket operations - every time it says it is using a file instead of a string once copy in memory was avoided. (The amount saved drowns in static from the rest of the system unless using huge files). Add Comment Puppet / PUP-1044 FileBucket should not keep files in memory It should not be necessary to load entire files into memory to checksum them. 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-3050) Fix cfacter integration to match recent cfacter changes
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3050 Fix cfacter integration to match recent cfacter changes Change By: Kylo Ginsberg Component/s: DOCS 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-3050) Fix cfacter integration to match recent cfacter changes
Title: Message Title Kylo Ginsberg commented on an issue Re: Fix cfacter integration to match recent cfacter changes Note to docs: cfacter's custom ruby facts support is not going to include support for :timeout. Add Comment Puppet / PUP-3050 Fix cfacter integration to match recent cfacter changes cfacter has changed its gem so that most of the implementation now lies in the C++ source. This means we can entirely remove lib/facts.rb and change the cfacter option implementation to simply call a single method in the gem. 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 (FACT-662) Extend ldom.rb to indicate whether ldom creation is supported
Title: Message Title William Van Hevelingen updated an issue Facter / FACT-662 Extend ldom.rb to indicate whether ldom creation is supported Change By: William Van Hevelingen Issue Type: Improvement Bug 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 (FACT-662) Extend ldom.rb to indicate whether ldom creation is supported
Title: Message Title
William Van Hevelingen commented on an issue
Re: Extend ldom.rb to indicate whether ldom creation is supported
Changing ticket type to Bug.
Facter no longer runs without errors on Solaris 11.2 because of the change. The `-ap` flags were removed for the new syntax.
lib/facter/ldom.rb: virtinfo = Facter::Core::Execution.exec('virtinfo -ap')
Add Comment
Facter / FACT-662
Extend ldom.rb to indicate whether ldom creation is supported
With the changes to virtinfo for Solaris 11.2 it's now possible to add support to facters ldom class to indicate whether a ldom creation is supported or not. On a sparc LDOM (SPARC T5-2) # virtinfo NAME CLASS logical-domain current non-global-zone supported kernel-zone supported On a sparc system that is hosting LDOMs (SPARC T5...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message
Jira (PUP-3129) Deprecate hidden _timestamp fact
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-3129 Deprecate hidden _timestamp fact Issue Type: Bug Assignee: Unassigned Created: 22/Aug/14 1:47 PM Fix Versions: 3.7.0 Priority: Normal Reporter: Kylo Ginsberg 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
Jira (PUP-3129) Deprecate hidden _timestamp fact
Title: Message Title Kylo Ginsberg commented on an issue Re: Deprecate hidden _timestamp fact After conversation with Henrik Lindberg and Nicholas Fagerlund we decided to deprecate the hidden $_timestamp fact. Which is exactly what Erik Dalen suggested in November 2013 on IRC: http://irc-logs.puppetlabs.com/puppetdev/%23puppet-dev-2013-11-21.log.html Add Comment Puppet / PUP-3129 Deprecate hidden _timestamp fact 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-3129) Deprecate hidden _timestamp fact
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3129 Deprecate hidden _timestamp fact Change By: Kylo Ginsberg Assignee: HenrikLindberg 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-3129) Deprecate hidden _timestamp fact
Title: Message Title Kylo Ginsberg commented on an issue Re: Deprecate hidden _timestamp fact For puppet 3.7 we aren't going to issue a deprecation warning, but we will remove _timestamp if immutable facts are enabled. This ticket will track that change. For puppet 4.0 we'll remove _timestamp completely. Add Comment Puppet / PUP-3129 Deprecate hidden _timestamp fact 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-3129) Deprecate hidden _timestamp fact
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3129 Deprecate hidden _timestamp fact Change By: Kylo Ginsberg Story Points: 1 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-3130) Remove hidden $_timestamp fact
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-3130 Remove hidden $_timestamp fact Issue Type: Improvement Assignee: Unassigned Created: 22/Aug/14 1:51 PM Fix Versions: 4.0.0 Priority: Normal Reporter: Kylo Ginsberg 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
Jira (PUP-3129) Deprecate hidden _timestamp fact
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3129 Deprecate hidden _timestamp fact Change By: Kylo Ginsberg Sprint: 2014-09-03 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 (FACT-681) facter doesn't have --custom-dir like cfacter
Title: Message Title Eric Thompson created an issue Facter / FACT-681 facter doesn't have --custom-dir like cfacter Issue Type: Bug Assignee: Eric Sorenson Created: 22/Aug/14 1:58 PM Priority: Minor Reporter: Eric Thompson divergence is bad? divergence can impact QA workflow 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
Jira (PUP-2914) Update packages to use RGen 0.7.0
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-2914 Update packages to use RGen 0.7.0 Change By: Hailee Kenney Assignee: HaileeKenney 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-3032) Setting to cache `load_library` failures
Title: Message Title Joshua Partlow commented on an issue Re: Setting to cache `load_library` failures If we were to check something here, I think it would be to test that an agent run installing gems is still able to act based on those gems having been installed, when the new setting is false or default. I'm not sure exactly what that manifest would look like; Josh Cooper might know. Add Comment Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... 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
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title Joshua Partlow commented on an issue Re: Use a manifest setting in [master] as global manifests Hi Josh Beard, do you see a precedence option as a requirement for 3.7, or just something that would be nice to have? (We are very tight on time Add Comment Puppet / PUP-3069 Use a manifest setting in [master] as global manifests In some puppet installations, especially when an ENC is in use, there are not really any environment specific manifests. Instead the ENC controls all of the classes that are included for a node. However, there is still some global setup that needs to take place outside of the ENC. One example of this is globally setting up a filebucket for all file resour... 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-3069) Use a manifest setting in [master] as global manifests
Title: Message Title Josh Beard commented on an issue Re: Use a manifest setting in [master] as global manifests I don't know about a requirement for 3.7. What would the behavior be? If it's to fallback on a default manifest if an environment-specific one isn't available, I'd think that'd be good, at least for the instances that I've encountered with customers. This would effectively preserve the previous behavior that folks were used (a global manifest and an optional environment-specific one) without requiring one be present for each environment. precedence is a nice to have, in my experience. Add Comment Puppet / PUP-3069 Use a manifest setting in [master] as global manifests In some puppet installations, especially when an ENC is in use, there are not really any environment specific manifests. Instead the ENC controls all of the classes that are included for a node. However, there is still some global setup that needs to take place outside of the ENC. One example of this is globally setting up a filebucket for all file resour... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the
Jira (PUP-2631) Running the puppet agent against a nonexistent environment produces an overly verbose error message.
Title: Message Title Michael Smith commented on an issue Re: Running the puppet agent against a nonexistent environment produces an overly verbose error message. Functional Review Note: certificate signing has to be complete before getting this error. Trying to initiate the first connection without a valid certificate gets a simple error about the production environment not existing. This appears to resolve the issue. The spec looks like a sufficient test of the fix. Add Comment Puppet / PUP-2631 Running the puppet agent against a nonexistent environment produces an overly verbose error message. When the puppet agent is run against a Puppet master using a nonexistent environment, the agent fails and prints an error message with the associated URL from the REST terminus. When the URL contains POST parameters, the resulting error is extremely verbose and produces about 50 or more lines of output. This is harmful from a user perspective because it p... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the
Jira (PUP-2914) Update packages to use RGen 0.7.0
Title: Message Title
Hailee Kenney commented on an issue
Re: Update packages to use RGen 0.7.0
Confirmed the correct behavior at ec67f829383e8fbbeb6ab54e17ab8a4d23cdb32d
Add Comment
Puppet / PUP-2914
Update packages to use RGen 0.7.0
PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on {{= 0.6.5}}. We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package.
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-2914) Update packages to use RGen 0.7.0
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-2914 Update packages to use RGen 0.7.0 Change By: Hailee Kenney Assignee: HaileeKenney 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-2913) Remove RGen Gem in Puppet-Win32-Ruby libraries
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-2913 Remove RGen Gem in Puppet-Win32-Ruby libraries Change By: Michael Smith Assignee: MichaelSmith 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-3129) Deprecate hidden _timestamp fact
Title: Message Title Henrik Lindberg commented on an issue Re: Deprecate hidden _timestamp fact Actually, the $_timestamp will be available in 3.7, but not in the immutable facts hash - this because there the facts have their original data value (not stringified). We cannot handle a Time instance leaking into the language without adding full support for it everywhere (type system, reports, database schema etc.) Add Comment Puppet / PUP-3129 Deprecate hidden _timestamp fact 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-2946) FileUtils implementation broke compare_stream
Title: Message Title
Kurt Wall commented on an issue
Re: FileUtils implementation broke compare_stream
The given commands fail with an error:
# curl -k -X PUT -H 'Content-Type: text/plain; Accept: s' https://centos6-5-base:8140/production/file_bucket_file/md5/c0090df6f1bb5511ac48b2e7e4ff3582//a.txt --data-binary @binfile.bin
Forbidden request: centos6-5-base.localdomain(172.16.205.248) access to /file_bucket_file/md5/c0090df6f1bb5511ac48b2e7e4ff3582/a.txt [save]
Add Comment
Puppet / PUP-2946
FileUtils implementation broke compare_stream
{{FileUtils.compare_stream}} implementation in ruby 1.9.3 was doing something along the lines of {code:ruby} a = b = nil while something a = as.read size b = bs.read size return false if a != b end {code} {{FileUtils.compare_stream}} in 2.0 instead does this: {code:ruby} a = b = while some...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received
Jira (PUP-1044) FileBucket should not keep files in memory
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-1044 FileBucket should not keep files in memory Change By: Eric Thompson Assignee: EricThompson 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-2913) Remove RGen Gem in Puppet-Win32-Ruby libraries
Title: Message Title Michael Smith updated an issue Puppet / PUP-2913 Remove RGen Gem in Puppet-Win32-Ruby libraries Change By: Michael Smith Attachment: Puppet64-bit.png 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-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
Jira (PUP-2913) Remove RGen Gem in Puppet-Win32-Ruby libraries
Title: Message Title Michael Smith updated an issue Puppet / PUP-2913 Remove RGen Gem in Puppet-Win32-Ruby libraries Change By: Michael Smith Attachment: Puppet32-bit.png 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-2913) Remove RGen Gem in Puppet-Win32-Ruby libraries
Title: Message Title
Michael Smith commented on an issue
Re: Remove RGen Gem in Puppet-Win32-Ruby libraries
Functional Review
Verified 1.9.3-x86 with puppet-3.6.2-1066-g5010aba.msi Verified 2.0.0-x64 with puppet-3.6.2-1066-g5010aba-x64pug.msi
Screenshots attached. Ran puppet agent with each and had a successful run.
Also created notice.pp $a = [1,2,3] each($a) |$x| { notice(Hi $x) }
and ran puppet apply --parser future notice.pp with output Notice: Scope(Class[main]): Hi 1 Notice: Scope(Class[main]): Hi 2 Notice: Scope(Class[main]): Hi 3 Notice: Compiled catalog for vagrant-2008r2.localdomain in environment production in 0.44 seconds Notice: Finished catalog run in 0.02 seconds
Add Comment
Puppet / PUP-2913
Remove RGen Gem in Puppet-Win32-Ruby libraries
Now that puppet allows for rgen to be at least 0.7.0 as part of puppet 3.7.0, we can update the vendored gems that ship with puppet on windows.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message
Jira (PUP-2289) Puppet will purge the /etc/hosts if it have some invalid lines
Title: Message Title
Leonardo Rodrigues de Mello commented on an issue
Re: Puppet will purge the /etc/hosts if it have some invalid lines
worked on the first bug on type host... don't have the time to work on the bug on provider host. https://github.com/puppetlabs/puppet/pull/3005
Add Comment
Puppet / PUP-2289
Puppet will purge the /etc/hosts if it have some invalid lines
normally, i use puppet resource host puppet ip=xxx.xxx.xxx.xxx can add/set a domain name resolution into /etc/hosts. like this: {code:none} [root@puppet ~]# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 [root@puppet ~]# puppe...
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-2914) Update packages to use RGen 0.7.0
Title: Message Title
Moses Mendoza commented on an issue
Re: Update packages to use RGen 0.7.0
It doesn't look like the RPM and Deb packaging files were updated to remove the dependency on rgen. Should I open a separate ticket to get that done?
Add Comment
Puppet / PUP-2914
Update packages to use RGen 0.7.0
PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on {{= 0.6.5}}. We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package.
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-2914) Update packages to use RGen 0.7.0
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-2914 Update packages to use RGen 0.7.0 Change By: Moses Mendoza Assignee: KyloGinsberg 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-2946) FileUtils implementation broke compare_stream
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2946 FileUtils implementation broke compare_stream Change By: Kurt Wall Assignee: KurtWall 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-2914) Update packages to use RGen 0.7.0
Title: Message Title
Moses Mendoza commented on an issue
Re: Update packages to use RGen 0.7.0
I have created a PR referencing this ticket. Please let me know if I should create a separate one.
Add Comment
Puppet / PUP-2914
Update packages to use RGen 0.7.0
PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on {{= 0.6.5}}. We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package.
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-3131) Registry not reading back proper value for binary.
Title: Message Title
Ethan Brown commented on an issue
Re: Registry not reading back proper value for binary.
I'm sorry, but I'm not understanding the issue here.
What was the original key value? What manifest was used to try to change it? What was the expected outcome? What was the actual outcome? Can you repro in a test?
Or is there an existing test that you can link to that corresponds to this failure?
Add Comment
Puppet / PUP-3131
Registry not reading back proper value for binary.
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: /...
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-3131) Registry not reading back proper value for binary.
Title: Message Title
Ethan Brown commented on an issue
Re: Registry not reading back proper value for binary.
Also, I believe this would be a modules ticket and not a Puppet ticket, correct? What version of Puppet, the module and Windows / Ruby platform and architecture?
Add Comment
Puppet / PUP-3131
Registry not reading back proper value for binary.
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: /...
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.
