Jira (FACT-964) Unable to find Ruby library on Debian 8 "Jessie"
Title: Message Title Peter Huene commented on FACT-964 Re: Unable to find Ruby library on Debian 8 "Jessie" Does this need to be ported to 3.0.1 or are we expected to be broken only on platforms not yet fully supported by Facter? 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-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Charlie Sharpsteen commented on PUP-4810 Re: Puppet caches parse results when environment_timeout is set to 0 We should also consider backporting this to 3.8.2 if the fix turns out to be as simple as the spike suggests. 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-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Henrik Lindberg Sprint: Language 2015-07-08 Story Points: 2 Scope Change Reason: reported by customers Scope Change Category: Found Release Notes: Bug Fix 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 thi
Jira (PUP-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Henrik Lindberg commented on PUP-4810 Re: Puppet caches parse results when environment_timeout is set to 0 We should fix this by doing two things: Do not enter 0 ttl entries into the cache (like in the tested modified version) Whenever a new environment is requested, evict all cached environments that have expired The quick change in the test is not the complete change that is needed - there are also calls to a service that keeps track of what is in the cache, and those calls are in the wrong place in the original implementation. Since 0 ttl entries are not cached, there should be no calls to the service for those, but there are since the calls are made when the cache entry is created, and not when it is actually added to the cache. 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 (PDB-1720) PR (58): (maint) Change specter/update to specter/transform - ajroetker
Title: Message Title gepetto-bot commented on PDB-1720 Re: PR (58): (maint) Change specter/update to specter/transform - ajroetker Pull request (maint) Change specter/update to specter/transform has been closed. 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-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-4810
Puppet caches parse results when environment_timeout is set to 0
Change By:
Charlie Sharpsteen
When {{environment_timeout}} is set to {{0}}, caching of parsed manifests is essentially a no-op as any object put into the cache is immediately marked as expired. However, Puppet still builds a cache when the timeout is set to 0 which consumes memory. This memory usage can be significant, especially when classifier sync hits the {{resource_types/*}} endpoint on each environment.h2. Reproduction Case* Install {{puppet-agent}} and {{puppetserver}}.* Edit {{/opt/puppetlabs/puppet/puppet.conf}} and set {{environment_timeout}} to 0 in the {{master}} section.* Edit {{/opt/puppetlabs/puppet/auth.conf}} and allow unrestricted access to the {{environments}} and {{resource_types}} endpoints:{code}path /puppet/v3/environmentsauth anymethod findallow *path /puppet/v3/resource_typeauth anymethod searchallow *{code}* Create a large number of classes in the {{production}} environment, and then a large number of copies of that environment (the number created is a bit excessive since the classes are simple, but real-world environments have shown this behavior with only hundreds of classes):{code:bash}mkdir -p /etc/puppetlabs/code/environments/production/modules/test_classes/manifestscat < /etc/puppetlabs/code/environments/production/modules/test_classes/manifests/init.pp<% 10.times do |i| %>class test_class_<%= i %> () {}<% end %>EOFfor i in $(seq 100);do cp -r /etc/puppetlabs/code/environments/production /etc/puppetlabs/code/environments/test_${i}; done{code}* Restart the puppetserver.* Simulate classifier syncs using the following script:{code:bash}#!/bin/bashget_env_list() { curl -s -k \https://localhost:8140/puppet/v3/environments |\/opt/puppetlabs/puppet/bin/ruby -rjson -e \'puts JSON.load($stdin.read())["environments"].keys.sort'}get_env_classes() { start_time=`date +%s` curl -s -k \"https://localhost:8140/puppet/v3/resource_types/*?environment=$1" > /tmp/${1}_classes.json; echo "Sync time: $(expr `date +%s` - $start_time) seconds";}get_all_classes() { for env in $(get_env_list); doecho "Fectching classes for: $env";get_env_classes $env done}while :; do get_all_classes; done{code}h3. OutcomeDuring class sync, each class is persisted to the cache despite {{environment_timeout}} being set to zero. This causes the Puppet Server to run out of memory:!pup_42_unpatched.png|thumbnail! ### h3. Expected OutcomeWhen `environment_timeout` is set to 0, no memory is wasted on caching classes.Applying a quick spike for this change:{code:diff}diff --git a/puppet/environments.rb b/puppet/environments.rbindex fa5a028..0ac12b7 100644--- a/puppet/environments.rb+++ b/puppet/environments.rb@@ -304,7 +304,8 @@ module Puppet::Environments if result = @cache[name] return result.value elsif (result = @loader.get(name))-@cache[name] = entry(result)+e = entry(result)+@cache[name] = e unless e.is_a?(NotCachedEntry) result end end{code}Results in the Puppet Server being able to sustain syncing a large number of classes:!pup_42_patched.png|thumbnail!
Jira (PUP-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Henrik Lindberg Fix Version/s: PUP 4.2.1 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-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-4810
Puppet caches parse results when environment_timeout is set to 0
Change By:
Charlie Sharpsteen
When {{environment_timeout}} is set to {{0}}, caching of parsed manifests is essentially a no-op as any object put into the cache is immediately marked as expired. However, Puppet still builds a cache when the timeout is set to 0 which consumes memory. This memory usage can be significant, especially when classifier sync hits the {{resource_types/*}} endpoint on each environment.h2. Reproduction Case* Install {{puppet-agent}} and {{puppetserver}}.* Edit {{/opt/puppetlabs/puppet/puppet.conf}} and set {{environment_timeout}} to 0 in the {{master}} section.* Edit {{/opt/puppetlabs/puppet/auth.conf}} and allow unrestricted access to the {{environments}} and {{resource_types}} endpoints:{code}path /puppet/v3/environmentsauth anymethod findallow *path /puppet/v3/resource_typeauth anymethod searchallow *{code}* Create a large number of classes in the {{production}} environment, and then a large number of copies of that environment (the number created is a bit excessive since the classes are simple, but real-world environments have shown this behavior with only hundreds of classes):{code:bash}mkdir -p /etc/puppetlabs/code/environments/production/modules/test_classes/manifestscat < /etc/puppetlabs/code/environments/production/modules/test_classes/manifests/init.pp<% 10.times do |i| %>class test_class_<%= i %> () {}<% end %>EOFfor i in $(seq 100);do cp -r /etc/puppetlabs/code/environments/production /etc/puppetlabs/code/environments/test_${i}; done{code}* Restart the puppetserver.* Simulate classifier syncs using the following script:{code:bash}#!/bin/bashget_env_list() { curl -s -k \https://localhost:8140/puppet/v3/environments |\/opt/puppetlabs/puppet/bin/ruby -rjson -e \'puts JSON.load($stdin.read())["environments"].keys.sort'}get_env_classes() { start_time=`date +%s` curl -s -k \"https://localhost:8140/puppet/v3/resource_types/*?environment=$1" > /tmp/${1}_classes.json; echo "Sync time: $(expr `date +%s` - $start_time) seconds";}get_all_classes() { for env in $(get_env_list); doecho "Fectching classes for: $env";get_env_classes $env done}while :; do get_all_classes; done{code}h3. OutcomeDuring class sync, each class is persisted to the cache despite {{environment_timeout}} being set to zero. This causes the Puppet Server to run out of memory:!pup_42_unpatched. tiff png|thumbnail !### Expected OutcomeWhen `environment_timeout` is set to 0, no memory is wasted on caching classes.Applying a quick spike for this change:{code:diff}diff --git a/puppet/environments.rb b/puppet/environments.rbindex fa5a028..0ac12b7 100644--- a/puppet/environments.rb+++ b/puppet/environments.rb@@ -304,7 +304,8 @@ module Puppet::Environments if result = @cache[name] return result.value elsif (result = @loader.get(name))-@cache[name] = entry(result)+e = entry(result)+@cache[name] = e unless e.is_a?(NotCachedEntry) result end end{code}Results in the Puppet Server being able to sustain syncing a large number of classes:!pup_42_patched.png |thumbnail !
Jira (PUP-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Charlie Sharpsteen Attachment: screenshot-1.png 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-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Charlie Sharpsteen Attachment: pup_42_unpatched.png 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-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Charlie Sharpsteen Attachment: screenshot-1.png 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-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Charlie Sharpsteen Attachment: pup_42_unpatched.tiff 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-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-4810
Puppet caches parse results when environment_timeout is set to 0
Change By:
Charlie Sharpsteen
When {{environment_timeout}} is set to {{0}}, caching of parsed manifests is essentially a no-op as any object put into the cache is immediately marked as expired. However, Puppet still builds a cache when the timeout is set to 0 which consumes memory. This memory usage can be significant, especially when classifier sync hits the {{resource_types/*}} endpoint on each environment.h2. Reproduction Case* Install {{puppet-agent}} and {{puppetserver}}.* Edit {{/opt/puppetlabs/puppet/puppet.conf}} and set {{environment_timeout}} to 0 in the {{master}} section.* Edit {{/opt/puppetlabs/puppet/auth.conf}} and allow unrestricted access to the {{environments}} and {{resource_types}} endpoints:{code}path /puppet/v3/environmentsauth anymethod findallow *path /puppet/v3/resource_typeauth anymethod searchallow *{code}* Create a large number of classes in the {{production}} environment, and then a large number of copies of that environment (the number created is a bit excessive since the classes are simple, but real-world environments have shown this behavior with only hundreds of classes):{code:bash}mkdir -p /etc/puppetlabs/code/environments/production/modules/test_classes/manifestscat < /etc/puppetlabs/code/environments/production/modules/test_classes/manifests/init.pp<% 10.times do |i| %>class test_class_<%= i %> () {}<% end %>EOFfor i in $(seq 100);do cp -r /etc/puppetlabs/code/environments/production /etc/puppetlabs/code/environments/test_${i}; done{code}* Restart the puppetserver.* Simulate classifier syncs using the following script:{code:bash}#!/bin/bashget_env_list() { curl -s -k \https://localhost:8140/puppet/v3/environments |\/opt/puppetlabs/puppet/bin/ruby -rjson -e \'puts JSON.load($stdin.read())["environments"].keys.sort'}get_env_classes() { start_time=`date +%s` curl -s -k \"https://localhost:8140/puppet/v3/resource_types/*?environment=$1" > /tmp/${1}_classes.json; echo "Sync time: $(expr `date +%s` - $start_time) seconds";}get_all_classes() { for env in $(get_env_list); doecho "Fectching classes for: $env";get_env_classes $env done}while :; do get_all_classes; done{code}h3. OutcomeDuring class sync, each class is persisted to the cache despite {{environment_timeout}} being set to zero. This causes the Puppet Server to run out of memory:!pup_42_unpatched.tiff!### Expected OutcomeWhen `environment_timeout` is set to 0, no memory is wasted on caching classes.Applying a quick spike for this change:{code:diff}diff --git a/puppet/environments.rb b/puppet/environments.rbindex fa5a028..0ac12b7 100644--- a/puppet/environments.rb+++ b/puppet/environments.rb@@ -304,7 +304,8 @@ module Puppet::Environments if result = @cache[name] return result.value elsif (result = @loader.get(name))-@cache[name] = entry(result)+e = entry(result)+@cache[name] = e unless e.is_a?(NotCachedEntry) result end end{code}Results in the Puppet Server being able to sustain syncing a large number of classes:!pup_42_patched. tiff png !
Jira (PUP-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Charlie Sharpsteen Attachment: pup_42_patched.png 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-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Charlie Sharpsteen Attachment: pup_42_patched.tiff 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-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Issue Type: Bug Affects Versions: PUP 4.2.0, PUP 3.8.1 Assignee: Unassigned Attachments: pup_42_patched.tiff, pup_42_unpatched.tiff Components: Language Created: 2015/07/01 5:43 PM Labels: support customer Priority: Major Reporter: Charlie Sharpsteen When environment_timeout is set to 0, caching of parsed manifests is essentially a no-op as any object put into the cache is immediately marked as expired. However, Puppet still builds a cache when the timeout is set to 0 which consumes memory. This memory usage can be significant, especially when classif
Jira (PUP-4807) enable Pipeline for running puppet (facter, hiera) on PE-only agent platforms
Title: Message Title Justin Stoller commented on PUP-4807 Re: enable Pipeline for running puppet (facter, hiera) on PE-only agent platforms This pipeline was set up a while ago but the tests were disabled so we could continue to promote stable into PE. I've gone ahead and set the jobs to trigger downstream jobs always (even if they fail) so that we can see what platforms are failing and even if they are we can get the passing platforms promoted into PE. 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-4757) Update pre-suites to install puppet-agent on "pe" platforms
Title: Message Title Justin Stoller commented on PUP-4757 Re: Update pre-suites to install puppet-agent on "pe" platforms AFAICT, these are the PE only platforms that we need to support: Redhat 4 Centos 4 SLES 10 SLES 11 SLES 12 Ubuntu 1004 AIX 5 AIX 6 AIX 7 Solaris 10 Solaris 11 The first 5 should have host configs in the Facter, Hiera, and Puppet repos. The remaining will need to be added I assume. A complete list of supported platforms can be found here: https://confluence.puppetlabs.com/display/PROD/Supported+Platforms+for+Shallow+Gravy Of those listed SLES 10, 11, 12 and Ubuntu 1004 are the only platforms we actually can build puppet-agent for currently (linked tickets RE-4096, RE-4098, and RE-4668 about the work for EL 4, Solaris and AIX). The PE only pipeline is here (platforms with known build issues have been excluded so we can continue with testing) https://jenkins.puppetlabs.com/view/PE%20AIO/ Add Comment
Jira (FACT-1084) facter network parsing - string parse
Title: Message Title Kylo Ginsberg commented on FACT-1084 Re: facter network parsing - string parse A `fatal` with an unhandled exception sounds like a need for some defensive programming somewhere. I'd like to get a handle on what the root cause is before assigning it to a later release, lest it be something that has wider applicability than this particular system configuration. 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-4740) Add missing query parameters to Puppet HTTPS API docs
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4740 Add missing query parameters to Puppet HTTPS API docs Change By: Kylo Ginsberg Scrum Team: Puppet Server Client Platform 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-4740) Add missing query parameters to Puppet HTTPS API docs
Title: Message Title Kylo Ginsberg commented on PUP-4740 Re: Add missing query parameters to Puppet HTTPS API docs Yep, makes sense, so I just moved it to the Client Scrum Team. 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-1076) Extract file utility functions to Leatherman
Title: Message Title Michael Smith assigned an issue to Unassigned Facter / FACT-1076 Extract file utility functions to Leatherman Change By: Michael Smith Assignee: Maggie Dreyer 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-4809) Mismatch in Error Message and Actual Behavior
Title: Message Title
Richard Raseley created an issue
Puppet / PUP-4809
Mismatch in Error Message and Actual Behavior
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/07/01 3:32 PM
Priority:
Normal
Reporter:
Richard Raseley
CentOS 7 x86_64
Puppet 4.2.0 (Installed via puppetlabs-release-pc1-el-7 repository)
Apply the following configuration:
yumrepo { 'mariadb' :
ensure => present,
enabled => True,
Jira (HI-417) Hiera YAML does not match standard with regard to multiline strings
Title: Message Title Henrik Lindberg commented on HI-417 Re: Hiera YAML does not match standard with regard to multiline strings If Ruby 1.8.x is used, it is the old Yaml implementation which does not support even Yaml 1.1 (I believe) and it also misbehaves in other ways. In Ruby 1.9 the MRI implementation changed to use Psych which is a wrapper around the native libyaml library. The libyaml library (http://pyyaml.org/wiki/LibYAML) supports Yaml 1.1, and as far as I understand it, there is no support for the special markup for string continuations in 1.1. Hiera is simply using the Yaml support in the Ruby runtime. What you need to do is to escape the newlines that libyaml turns into spaces like this: --- key: "Line1\n\ Line2\n\ Line3" key2: 1 Closing this as a won't fix as this is standard Yaml support in Ruby. Whenever there is a Yaml implementation in Ruby that supports Yaml 1.2 specification then hiera will also get those abilities. Add Comment
Jira (FACT-704) Docker support for virtual and is_virtual broken by systemd slices
Title: Message Title William Hopper commented on FACT-704 Re: Docker support for virtual and is_virtual broken by systemd slices This is actually to be expected, as the fix for this issue is in master but we haven't yet merged into stable, which is what the nightlies are built off of. To verify, I used Vanagon built a new puppet-agent RPM using facter#master (SHA f034727b92992f6f56a76ae1c925e668a7b07161). [root@xhqsuvjlmxl3ewl ~]# docker run -it --rm centos7-puppet-agent-g3d67503 /opt/puppetlabs/bin/facter is_virtual virtual is_virtual => true virtual => docker 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 t
Jira (PDB-1720) PR (58): (maint) Change specter/update to specter/transform - ajroetker
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-1720 PR (58): (maint) Change specter/update to specter/transform - ajroetker Change By: Andrew Roetker Sprint: PuppetDB 2015-07-15 Story Points: 1 Scope Change Reason: Bug that broke PE-extensions Scope Change Category: Found Fix Version/s: PDB 3.1.0 Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1720) PR (58): (maint) Change specter/update to specter/transform - ajroetker
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1720 PR (58): (maint) Change specter/update to specter/transform - ajroetker Issue Type: Task Assignee: Unassigned Created: 2015/07/01 3:21 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Change specter/update to specter/transform Author: Andrew Roetker <> Company: Puppet Labs Github ID: ajroetker Pull Request 58 Discussion Pull Request 58 File Diff Pull Request Description This commit corresponds to the upgrade of specter from 0.5.2 to 0.5.7, where the `update` function was renamed to `transform`. (webhooks-id: 94795ff7c973719830f
Jira (FACT-704) Docker support for virtual and is_virtual broken by systemd slices
Title: Message Title William Hopper assigned an issue to William Hopper Facter / FACT-704 Docker support for virtual and is_virtual broken by systemd slices Change By: William Hopper Assignee: William Hopper 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 (HI-417) Hiera YAML does not match standard with regard to multiline strings
Title: Message Title Robert commented on HI-417 Re: Hiera YAML does not match standard with regard to multiline strings Stock Ubuntu install, so: root@puppet01:/etc/puppet# ruby --version ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux] I take it this is an issue that got resolved at some point in ruby? 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-4808) Enable testing puppet_agent module with full build matrix in jenkins-modules
Title: Message Title Michael Smith commented on PUP-4808 Re: Enable testing puppet_agent module with full build matrix in jenkins-modules I was thinking Redhat 5/6/7, Debian 6/7, and Ubuntu 12.04/14.04/14.10. Those are the ones we list in the module metadata. Eventually we'll probably want to add the PE platforms, but I'm not sure when (Kylo Ginsberg). 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 (HI-417) Hiera YAML does not match standard with regard to multiline strings
Title: Message Title Henrik Lindberg commented on HI-417 Re: Hiera YAML does not match standard with regard to multiline strings Which ruby version are you seeing this with? 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-4808) Enable testing puppet_agent module with full build matrix in jenkins-modules
Title: Message Title Justin Stoller commented on PUP-4808 Re: Enable testing puppet_agent module with full build matrix in jenkins-modules Michael Smith, we usually just test FOSS on the basic platforms (for a smoke test) and then test all the platforms on PE (that's the way the job currently is set up). If I'm understanding correctly, you want me to add all the supported platforms for Deb and EL? Including Jessie? What about Sci, OEL, and CentOS? Fedora??? 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 (HI-417) Hiera YAML does not match standard with regard to multiline strings
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-417
Hiera YAML does not match standard with regard to multiline strings
Change By:
Henrik Lindberg
The YAML standard has two ways to deal with strings that cross multiple lines:* Folded style, which is the default, ignores newlines and treats the string as one single line.* Literal style, which is signified by placing a pipe character after the colon, does not remove the newlines.These can be found on the website for the YAML specifications: http://www.yaml.org/spec/1.2/spec.html#id2760844Hiera is completely ignoring the YAML ability to switch between these two modes.This is forcing users to use fully quoted text with the "\n" special character for newlines.Unfortunately even there the standard is being ignored, because for some unknown reason this results in both the newlines being added *and* whitespace being added to the front of the lines immediately after the new line character. {code} 'TestString': "Line One\nLine Two\nLine Three\n" {code} Results in: {code} Line One Line Two Line Three {code} Where there is a space on the second and third lines that should not be there. Unfortunately I can't get the jira formatting to work, so you'll have to view source of this message to see what I'm talking about.
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 po
Jira (PUP-4808) Enable testing puppet_agent module with full build matrix in jenkins-modules
Title: Message Title Michael Smith commented on PUP-4808 Re: Enable testing puppet_agent module with full build matrix in jenkins-modules Justin Stoller is there any work you need from us on this? 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-4808) Enable testing puppet_agent module with full build matrix in jenkins-modules
Title: Message Title Michael Smith created an issue Puppet / PUP-4808 Enable testing puppet_agent module with full build matrix in jenkins-modules Issue Type: Task Assignee: Unassigned Created: 2015/07/01 2:53 PM Priority: Normal Reporter: Michael Smith Currently we test el6, el7, and ubuntu 14.04. We should extend to the full set of supported Debian, Ubuntu, and EL platforms. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-1086) Validate on el4
Title: Message Title Michael Smith updated an issue Facter / FACT-1086 Validate on el4 Change By: Michael Smith Issue Type: Bug Task 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-1088) Validate on Ubuntu lucid
Title: Message Title Michael Smith updated an issue Facter / FACT-1088 Validate on Ubuntu lucid Change By: Michael Smith Summary: Validace Validate on Ubuntu lucid 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-1088) Validace Ubuntu lucid
Title: Message Title Michael Smith created an issue Facter / FACT-1088 Validace Ubuntu lucid Issue Type: Task Assignee: Unassigned Created: 2015/07/01 2:49 PM Fix Versions: FACT 3.1.0 Priority: Normal Reporter: Michael Smith 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
Jira (FACT-1087) Validate on sles
Title: Message Title Michael Smith created an issue Facter / FACT-1087 Validate on sles Issue Type: Task Assignee: Unassigned Created: 2015/07/01 2:49 PM Fix Versions: FACT 3.1.0 Priority: Normal Reporter: Michael Smith 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 Goog
Jira (FACT-1086) Validate on el4
Title: Message Title Michael Smith created an issue Facter / FACT-1086 Validate on el4 Issue Type: Bug Assignee: Unassigned Created: 2015/07/01 2:48 PM Fix Versions: FACT 3.1.0 Priority: Normal Reporter: Michael Smith 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
Jira (PDB-1710) PR (1509): (DOC-2087) Point to correct install docs for PC1... - jtappa
Title: Message Title gepetto-bot commented on PDB-1710 Re: PR (1509): (DOC-2087) Point to correct install docs for PC1... - jtappa Pull request (DOC-2087) Point to correct install docs for PC1... has been closed. 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-1085) Facter should not redirect stderr to stdout
Title: Message Title
Peter Huene updated an issue
Facter / FACT-1085
Facter should not redirect stderr to stdout
Change By:
Peter Huene
Using this custom fact:{code}Facter.add("pe_razor_server_version") do confine :osfamily => "Debian" setcode doFacter::Core::Execution.exec("dpkg-query -W --showformat='${Version}' pe-razor-server | cut -f1 -d'-'") endend{code}In Facter 2.x, Facter doesn't redirect the command's stderr, so it gets printed directly to the terminal.{noformat}# puppet agent -tInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsdpkg-query: no packages found matching pe-razor-server{noformat}The {{pe_razor_server_version}} does not resolve. **This is the expected behavior.**In Facter 3.x, Facter incorrectly redirects the command's stderr into stdout, resulting in {{pe_razor_server_version}} resolving to "dpkg-query: no packages found matching pe-razor-server" (I'm assuming this outputs on stderr, but if it doesn't, this can easily reproduced with a non-existent first command in the pipe sequence too). This is the first bug.The second bug is that if dpkg-query (or any first command in a pipe sequence) is not found, then {{Facter::Core::Execution.exec}} treats it as a missing command and returns nil. Facter does this check for commands, but in this case the command is /bin/sh, which exists. An additional check is required to the arguments to /bin/sh (i.e. the original command given to {{Facter::Core::Execution::exec}}) and treat it as command missing. Note that we do not want to print the line "dpkg-query: no packages found matching pe-razor-server" to puppet's stderr, like Facter 2.x did. Instead, with Puppet's feature of redirecting Facter debug output, passing {{--debug}} to puppet will show more details, including this message from dpkg-query.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1719) Check protections against (accidental) simultaneous instances
Title: Message Title Rob Browning created an issue PuppetDB / PDB-1719 Check protections against (accidental) simultaneous instances Issue Type: Task Assignee: Unassigned Created: 2015/07/01 2:41 PM Priority: Normal Reporter: Rob Browning What happens (and what do we want to promise) when two puppetdb invocations attempt to use the same directories at the same time? It could be that the failure when attempting to use the same port is sufficient protection, but even if that's so in the steady state, imagine that puppetdb is running on port 8080, someone changes the config to refer to port 8090, and then launches puppetdb again without remembering to stop the old instance. Do we handle that well? Should we? Whatever the result, make sure it's well documented. Add Comment
Jira (PDB-1718) Check/document host filesystem expectations/restrictions
Title: Message Title Rob Browning created an issue PuppetDB / PDB-1718 Check/document host filesystem expectations/restrictions Issue Type: Task Assignee: Unassigned Created: 2015/07/01 2:34 PM Priority: Normal Reporter: Rob Browning Might be a no-op ticket, but if we haven't yet, we may want to document our filesystem expectations, i.e. is it OK to run puppetdb on an NFS filesystem, or does it need to be local, etc. And if we're not sure about NFS (for example), might be worth being conservative and just making that clear. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1701) Reject older revisions of the current command revisions at the wire
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1701 Reject older revisions of the current command revisions at the wire Change By: Wyatt Alt Assignee: Wyatt Alt 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-4740) Add missing query parameters to Puppet HTTPS API docs
Title: Message Title Jeremy Barlow commented on PUP-4740 Re: Add missing query parameters to Puppet HTTPS API docs Hmmm, actually I'm wondering if it might be better for the Client Platform team to take on helping out with this as it could have a better perspective on what extra parameters that the Puppet agent may be using and for what reasons. Kylo Ginsberg, what do you think? 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-4798) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4798 deprecation of 'facter --puppet' removes critically necessary functionality Change By: Steve Barlow Sprint: Client 2015-07-22 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-4798) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4798 deprecation of 'facter --puppet' removes critically necessary functionality Change By: Steve Barlow Story Points: 3 QA Highest Test Level: Acceptance 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-4752) Uppercase letters in parameter variable names
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4752 Uppercase letters in parameter variable names Change By: Henrik Lindberg Fix Version/s: PUP 4.2.1 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-4798) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4798 deprecation of 'facter --puppet' removes critically necessary functionality Change By: Steve Barlow Scrum Team: Client Platform 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-1085) Facter should not redirect stderr to stdout
Title: Message Title Steve Barlow updated an issue Facter / FACT-1085 Facter should not redirect stderr to stdout Change By: Steve Barlow Sprint: Client 2015-07-22 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-1085) Facter should not redirect stderr to stdout
Title: Message Title
Peter Huene updated an issue
Facter / FACT-1085
Facter should not redirect stderr to stdout
Change By:
Peter Huene
Using this custom fact:{code}Facter.add("pe_razor_server_version") do confine :osfamily => "Debian" setcode doFacter::Core::Execution.exec("dpkg-query -W --showformat='${Version}' pe-razor-server | cut -f1 -d'-'") endend{code}In Facter 2.x, Facter doesn't redirect the command's stderr, so it gets printed directly to the terminal.{noformat}# puppet agent -tInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsdpkg-query: no packages found matching pe-razor-server{noformat}The {{pe_razor_server_version}} does not resolve. **This is the expected behavior.**In Facter 3.x, Facter incorrectly redirects the command's stderr into stdout, resulting in {{pe_razor_server_version}} resolving to "dpkg-query: no packages found matching pe-razor-server" (I'm assuming this outputs on stderr, but if it doesn't, this can easily reproduced with a non-existent first command in the pipe sequence too) . This is the first bug.The second bug is that if dpkg-query (or any first command in a pipe sequence) is not found, then {{Facter::Core::Execution.exec}} treats it as a missing command and returns nil. Facter does this check for commands, but in this case the command is /bin/sh, which exists. An additional check is required to the arguments to /bin/sh (i.e. the original command given to {{Facter::Core::Execution::exec}}) and treat it as command missing.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
Jira (HI-417) Hiera YAML does not match standard with regard to multiline strings
Title: Message Title Robert updated an issue Hiera / HI-417 Hiera YAML does not match standard with regard to multiline strings Change By: Robert The YAML standard has two ways to deal with strings that cross multiple lines:* Folded style, which is the default, ignores newlines and treats the string as one single line.* Literal style, which is signified by placing a pipe character after the colon, does not remove the newlines.These can be found on the website for the YAML specifications: http://www.yaml.org/spec/1.2/spec.html#id2760844Hiera is completely ignoring the YAML ability to switch between these two modes.This is forcing users to use fully quoted text with the "\n" special character for newlines.Unfortunately even there the standard is being ignored, because for some unknown reason this results in both the newlines being added *and* whitespace being added to the front of the lines immediately after the new line character. 'TestString': "Line One\nLine Two\nLine Three\n" Results in: Line One Line Two Line Three Where there is a space on the second and third lines that should not be there. Unfortunately I can't get the jira formatting to work, so you'll have to view source of this message to see what I'm talking about. 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-bu
Jira (HI-417) Hiera YAML does not match standard with regard to multiline strings
Title: Message Title Robert updated an issue Hiera / HI-417 Hiera YAML does not match standard with regard to multiline strings Change By: Robert The YAML standard has two ways to deal with strings that cross multiple lines:* Folded style, which is the default, ignores newlines and treats the string as one single line.* Literal style, which is signified by placing a pipe character after the colon, does not remove the newlines.These can be found on the website for the YAML specifications: http://www.yaml.org/spec/1.2/spec.html#id2760844Hiera is completely ignoring the YAML ability to switch between these two modes.This is forcing users to use fully quoted text with the "\n" special character for newlines.Unfortunately even there the standard is being ignored, because for some unknown reason this results in both the newlines being added *and* whitespace being added to the front of the lines immediately after the new line character. ``` 'TestString': "Line One\nLine Two\nLine Three\n" ``` Results in: ``` Line One Line Two Line Three ``` Where there is a space on the second and third lines that should not be there. 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://
Jira (HI-417) Hiera YAML does not match standard with regard to multiline strings
Title: Message Title Robert updated an issue Hiera / HI-417 Hiera YAML does not match standard with regard to multiline strings Change By: Robert The YAML standard has two ways to deal with strings that cross multiple lines:* Folded style, which is the default, ignores newlines and treats the string as one single line.* Literal style, which is signified by placing a pipe character after the colon, does not remove the newlines.These can be found on the website for the YAML specifications: http://www.yaml.org/spec/1.2/spec.html#id2760844Hiera is completely ignoring the YAML ability to switch between these two modes.This is forcing users to use fully quoted text with the "\n" special character for newlines.Unfortunately even there the standard is being ignored, because for some unknown reason this results in both the newlines being added *and* whitespace being added to the front of the lines immediately after the new line character. ``` 'TestString': "Line One\nLine Two\nLine Three\n" ``` Results in: ``` Line One Line Two Line Three ``` Where there is a space on the second and third lines that should not be there. 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://
Jira (HI-417) Hiera YAML does not match standard with regard to multiline strings
Title: Message Title Robert created an issue Hiera / HI-417 Hiera YAML does not match standard with regard to multiline strings Issue Type: Bug Assignee: Unassigned Created: 2015/07/01 2:00 PM Priority: Normal Reporter: Robert The YAML standard has two ways to deal with strings that cross multiple lines: Folded style, which is the default, ignores newlines and treats the string as one single line. Literal style, which is signified by placing a pipe character after the colon, does not remove the newlines. These can be found on the website for the YAML specifications: http://www.yaml.org/spec/1.2/spec.html#id2760844 Hiera is completely ignoring the YAML ability to switch between these two modes. This is forcing users to use fully quoted text with the "\n" special character for newlines. Unfortunately even there the standard is being ignored, because for some unknown reason this results in both the newlines being added and whitespace being added to the front of the lines immediately after the new line character. 'TestString': "Line One\n Line Two\n Line Three\n" Results in: Line One Line Two Line Three Where there is a space on the second and third lines that shou
Jira (PUP-4702) Replace rgen model for the Puppet Type system with immutable classes
Title: Message Title Henrik Lindberg commented on PUP-4702 Re: Replace rgen model for the Puppet Type system with immutable classes Since this also adds enumerability to a couple of an additional types, the language specification needs to be updated. This commit moves the enumerable? method to the PAnyType and implements Enumerable on PEnumType, PTupleType, PStructType and PVariantType. It may even warrant an update of the iterative functions as they may mention that it can iterate over only Integer. 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-1085) Facter should not redirect stderr to stdout
Title: Message Title
Peter Huene updated an issue
Facter / FACT-1085
Facter should not redirect stderr to stdout
Change By:
Peter Huene
Using this custom fact:{code}Facter.add("pe_razor_server_version") do confine :osfamily => "Debian" setcode doFacter::Core::Execution.exec("dpkg-query -W --showformat='${Version}' pe-razor-server | cut -f1 -d'-'") endend{code}In Facter 2.x, Facter doesn't redirect the command's stderr, so it gets printed directly to the terminal.{noformat}# puppet agent -tInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsdpkg-query: no packages found matching pe-razor-server{noformat}The {{pe_razor_server_version does }} does not resolve. This is the expected behavior.In Facter 3.x, Facter incorrectly redirects the command's stderr into stdout, resulting in {{pe_razor_server_version}} resolving to "dpkg-query: no packages found matching pe-razor-server". This is the first bug.The second bug is that if dpkg-query (or any first command in a pipe sequence) is not found, then {{Facter::Core::Execution.exec}} treats it as a missing command and returns nil. Facter does this check for commands, but in this case the command is /bin/sh, which exists. An additional check is required to the arguments to /bin/sh (i.e. the original command given to {{Facter::Core::Execution::exec}}) and treat it as command missing.
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 receiv
Jira (FACT-1085) Facter should not redirect stderr to stdout
Title: Message Title Peter Huene updated an issue Facter / FACT-1085 Facter should not redirect stderr to stdout Change By: Peter Huene Story Points: 2 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-4458) Refactor validation of 4.x parameter signatures
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4458 Refactor validation of 4.x parameter signatures Change By: Henrik Lindberg Comment: Since this also adds enumerability to a couple of an additional types, the language specification needs to be updated.bq. This commit moves the enumerable? method to the PAnyType and implements Enumerable on PEnumType, PTupleType, PStructType and PVariantType.It may even warrant an update of the iterative functions as they may mention that it can iterate over only Integer. 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-1085) Facter should not redirect stderr to stdout
Title: Message Title
Peter Huene updated an issue
Facter / FACT-1085
Facter should not redirect stderr to stdout
Change By:
Peter Huene
Using this custom fact:{code}Facter.add("pe_razor_server_version") do confine :osfamily => "Debian" setcode doFacter::Core::Execution.exec("dpkg-query -W --showformat='${Version}' pe-razor-server | cut -f1 -d'-'") endend{code}In Facter 2.x, Facter doesn't redirect the command's stderr, so it gets printed directly to the terminal.{noformat}# puppet agent -tInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsdpkg-query: no packages found matching pe-razor-server{noformat}The {{pe_razor_server_version}} does not resolve. ** This is the expected behavior. ** In Facter 3.x, Facter incorrectly redirects the command's stderr into stdout, resulting in {{pe_razor_server_version}} resolving to "dpkg-query: no packages found matching pe-razor-server". This is the first bug.The second bug is that if dpkg-query (or any first command in a pipe sequence) is not found, then {{Facter::Core::Execution.exec}} treats it as a missing command and returns nil. Facter does this check for commands, but in this case the command is /bin/sh, which exists. An additional check is required to the arguments to /bin/sh (i.e. the original command given to {{Facter::Core::Execution::exec}}) and treat it as command missing.
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 recei
Jira (FACT-1085) Facter should not redirect stderr to stdout
Title: Message Title
Peter Huene updated an issue
Facter / FACT-1085
Facter should not redirect stderr to stdout
Change By:
Peter Huene
Using this custom fact:{code}Facter.add("pe_razor_server_version") do confine :osfamily => "Debian" setcode doFacter::Core::Execution.exec("dpkg-query -W --showformat='${Version}' pe-razor-server | cut -f1 -d'-'") endend{code} The In Facter 2.x, Facter doesn't redirect the command's stderr value of "dpkg-query: no packages found matching pe-razor-server" is being redirected , so it gets printed directly to the stdout: terminal. {noformat}# puppet agent -tInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsdpkg-query: no packages found matching pe-razor-server{noformat} The {{pe_razor_server_version does}} not resolve. This is the expected behavior.In Facter 3.x, Facter incorrectly redirects the command's stderr into stdout, resulting in {{pe_razor_server_version}} resolving to "dpkg-query: no packages found matching pe-razor-server". This is the first bug.The second bug is that if dpkg-query (or any first command in a pipe sequence) is not found, then {{Facter::Core::Execution.exec}} treats it as a missing command and returns nil. Facter does this check for commands, but in this case the command is /bin/sh, which exists. An additional check is required to the arguments to /bin/sh (i.e. the original command given to {{Facter::Core::Execution::exec}}) and treat it as command missing.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are s
Jira (PUP-4458) Refactor validation of 4.x parameter signatures
Title: Message Title Henrik Lindberg commented on PUP-4458 Re: Refactor validation of 4.x parameter signatures Since this also adds enumerability to a couple of an additional types, the language specification needs to be updated. This commit moves the enumerable? method to the PAnyType and implements Enumerable on PEnumType, PTupleType, PStructType and PVariantType. It may even warrant an update of the iterative functions as they may mention that it can iterate over only Integer. 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-1085) Facter should not redirect stderr to stdout
Title: Message Title Peter Huene updated an issue Facter / FACT-1085 Facter should not redirect stderr to stdout Change By: Peter Huene Affects Version/s: FACT 3.0.1 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-1085) Facter should not redirect stderr to stdout
Title: Message Title Peter Huene updated an issue Facter / FACT-1085 Facter should not redirect stderr to stdout Change By: Peter Huene Fix Version/s: FACT 3.0.2 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-1085) Facter should not redirect stderr to stdout
Title: Message Title
Scott McClellan updated an issue
Facter / FACT-1085
Facter should not redirect stderr to stdout
Change By:
Scott McClellan
Using this custom fact:{code}Facter.add("pe_razor_server_version") do confine :osfamily => "Debian" setcode doFacter::Core::Execution.exec("dpkg-query -W --showformat='${Version}' pe-razor-server | cut -f1 -d'-'") endend{code}The stderr value of "dpkg-query: no packages found matching pe-razor-server" is being redirected to the stdout . :{noformat}# puppet agent -tInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsdpkg-query: no packages found matching pe-razor-server{noformat}
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-1085) Facter should not redirect stderr to stdout
Title: Message Title
Scott McClellan created an issue
Facter / FACT-1085
Facter should not redirect stderr to stdout
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/07/01 1:42 PM
Priority:
Normal
Reporter:
Scott McClellan
Using this custom fact:
Facter.add("pe_razor_server_version") do
confine :osfamily => "Debian"
setcode do
Facter::Core::Execution.exec("dpkg-query -W --showformat='${Version}' pe-razor-server | cut -f1 -d'-'")
Jira (PUP-4684) windows file resource doesn't grant group full permissions
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-4684 windows file resource doesn't grant group full permissions Change By: Rob Reynolds Component/s: Windows 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 (PDB-1670) PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa
Title: Message Title gepetto-bot commented on PDB-1670 Re: PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1596/ 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-4050) Acceptance suite and install.rb use incorrect paths on Windows for codedir
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4050 Acceptance suite and install.rb use incorrect paths on Windows for codedir Change By: Steve Barlow Story Points: 1 2 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-1073) Operatingsystem release facts not properly resolved in Arch Linux
Title: Message Title Shaigy Nixon commented on FACT-1073 Re: Operatingsystem release facts not properly resolved in Arch Linux Since Arch Linux is not supported and the fix is already validated on OSX for FACT-1056 , resolving without validation. 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-4448) Create acceptance tests for non-root external facts
Title: Message Title William Hopper commented on PUP-4448 Re: Create acceptance tests for non-root external facts This ticket should really wait until BKR-168 is resolved and adds `run as` functionality to beaker. 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-1084) facter network parsing - string parse
Title: Message Title Michael Smith updated an issue Facter / FACT-1084 facter network parsing - string parse Change By: Michael Smith Sprint: Client 2015-07-08 Scrum Team: Client Platform Story Points: 2 Scope Change Reason: Regression in Facter 3 Scope Change Category: Found 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
Jira (FACT-1084) facter network parsing - string parse
Title: Message Title Michael Smith updated an issue Facter / FACT-1084 facter network parsing - string parse Change By: Michael Smith Fix Version/s: FACT 3.0.2 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-1084) facter network parsing - string parse
Title: Message Title Michael Smith assigned an issue to Michael Smith Facter / FACT-1084 facter network parsing - string parse Change By: Michael Smith Assignee: Michael Smith 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-4683) repair winrm/winrm-fs gem
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4683 repair winrm/winrm-fs gem Change By: Steve Barlow Sprint: Windows 2015-07-01 , Windows 2015-07-15 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 (PDB-1622) Document HA endpoint and configuration
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1622 Document HA endpoint and configuration Change By: Russell Mull Scope Change Reason: Required before PDB-1526; backlog should have reflected this. Scope Change Category: Adopted 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 (PDB-1315) Add sync information to metrics
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1315 Add sync information to metrics Change By: Russell Mull Scope Change Reason: Related to an ongoing refactor ; made sense to pull it in. 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 (PDB-1623) Document extended logging configuration
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1623 Document extended logging configuration Change By: Russell Mull Scope Change Reason: Required before PDB-1526; backlog should have reflected this. Scope Change Category: Adopted 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-4702) Replace rgen model for the Puppet Type system with immutable classes
Title: Message Title Henrik Lindberg commented on PUP-4702 Re: Replace rgen model for the Puppet Type system with immutable classes For FR, there is not much to FR as this is an optimization. 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-4702) Replace rgen model for the Puppet Type system with immutable classes
Title: Message Title Henrik Lindberg commented on PUP-4702 Re: Replace rgen model for the Puppet Type system with immutable classes merged to master at: 6bc2c04 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-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: facter network parsing - 8.1 string parse 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-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 . . . . . : fe80::a9d5:250
Jira (PUP-4448) Create acceptance tests for non-root external facts
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4448 Create acceptance tests for non-root external facts Change By: Kylo Ginsberg Sprint: Client 2015-07-08 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-1073) Operatingsystem release facts not properly resolved in Arch Linux
Title: Message Title Shaigy Nixon assigned an issue to Shaigy Nixon Facter / FACT-1073 Operatingsystem release facts not properly resolved in Arch Linux Change By: Shaigy Nixon Assignee: qa Shaigy Nixon 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-1056) Operatingsystem major release not resolved in OSX
Title: Message Title
Shaigy Nixon commented on FACT-1056
Re: Operatingsystem major release not resolved in OSX
Validated on puppet-agent SHA 3d67503e963f4f09b26fe2800fb13670b5f748a2: On osx-1010-x86_64:
q3uw05sblidigy5:~ root# uname -a
Darwin q3uw05sblidigy5 14.1.0 Darwin Kernel Version 14.1.0: Thu Feb 26 19:26:47 PST 2015; root:xnu-2782.10.73~1/RELEASE_X86_64 x86_64
q3uw05sblidigy5:~ root# puppet --version
4.2.0
q3uw05sblidigy5:~ root# facter --version
3.0.1 (commit 97fcfb6395f3aba974d7ea103d516621942889f4)
q3uw05sblidigy5:~ root# facter os
{
architecture => "x86_64",
family => "Darwin",
Jira (PUP-3386) Puppet Module Gem Dependency Metadata and Installation
Title: Message Title Ryan Gard updated an issue Puppet / PUP-3386 Puppet Module Gem Dependency Metadata and Installation Change By: Ryan Gard QA Contact: Ryan Gard Zach Reichert 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 (PDB-1670) PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa
Title: Message Title gepetto-bot commented on PDB-1670 Re: PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa kbarber commented: @melissa thanks very much, looking forward to testing your changes again. 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 (PDB-1670) PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa
Title: Message Title gepetto-bot commented on PDB-1670 Re: PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa melissa commented: @kbarber both deb and rpm restarts should be happening in ezbake. I think this PR is done in terms of functionality. I'm working on an ezbake pr as we speak. 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-4795) smf.rb provider for service - manifest does not work for S11.x
Title: Message Title Scott Garman commented on PUP-4795 Re: smf.rb provider for service - manifest does not work for S11.x I've not touched anything in Solaris myself yet. I think Rob Braden or Geoff Nichols would be of more help. 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-4795) smf.rb provider for service - manifest does not work for S11.x
Title: Message Title Jes Ferrier commented on PUP-4795 Re: smf.rb provider for service - manifest does not work for S11.x Quick asides, S11 preferred method of importing a service is to svcadm restart manifest-import service and not the svccfg import used in S10. 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-4795) smf.rb provider for service - manifest does not work for S11.x
Title: Message Title Christopher Price commented on PUP-4795 Re: smf.rb provider for service - manifest does not work for S11.x Scott Garman is this in your wheelhouse? 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-4795) smf.rb provider for service - manifest does not work for S11.x
Title: Message Title Christopher Price updated an issue Puppet / PUP-4795 smf.rb provider for service - manifest does not work for S11.x Change By: Christopher Price Component/s: Puppet Server Component/s: RE Component/s: Client 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-4795) smf.rb provider for service - manifest does not work for S11.x
Title: Message Title Christopher Price updated an issue Puppet / PUP-4795 smf.rb provider for service - manifest does not work for S11.x Change By: Christopher Price Scrum Team: Puppet Server 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-4765) Puppet Agent Module Documentation Errata for Windows is Incomplete
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4765 Puppet Agent Module Documentation Errata for Windows is Incomplete Change By: Ryan Gard QA Status: Reviewed 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-4339) Non-US paths in environment variables gets garbled on Windows
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4339 Non-US paths in environment variables gets garbled on Windows Change By: Ryan Gard QA Status: Reviewed 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-4770) Solaris Zones provider debug and error messages are less informative in Puppet 4
Title: Message Title John Duarte assigned an issue to Unassigned Puppet / PUP-4770 Solaris Zones provider debug and error messages are less informative in Puppet 4 Change By: John Duarte Assignee: qa 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-4653) The filebucket client uses v1 API URLs internally
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4653 The filebucket client uses v1 API URLs internally Change By: Eric Thompson QA Highest Test Level Reason: might need a local-filebucket test QA Risk Severity: High Medium QA Risk Severity Reason: escaped; reported from outside QA Risk Assessment: High Medium 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
Jira (FACT-704) Docker support for virtual and is_virtual broken by systemd slices
Title: Message Title John Duarte commented on FACT-704 Re: Docker support for virtual and is_virtual broken by systemd slices Using puppet-agent puppet-agent-1.1.1.239.g3d67503 from nightlies, July 1, 2015, facter 3 fails to produce the expected result for the `virtual` fact in a docker container on a Centos 7 host. The container returns the `virtual` fact of the host system not that of the container. Steps to reproduce Environment: Host: Centos-7-x86_64 vmware vm Docker: Latest version (1.6.2), installed from get.docker.com Docker Container: Centos 7 Facter: Version 3.0.1 (commit 97fcfb6395f3aba974d7ea103d516621942889f4), installed via nightly build of puppet-agent Install docker on host and start docker service [root@j1vqpt6h9xltrri ~]# curl https://get.docker.com/ | sh [root@j1vqpt6h9xltrri ~]# docker --version Docker version 1.6.2, build ba1f6c3/1.6.2 [root@j1vqpt6h9xltrri ~]# service docker start Redirecting to /bin/systemctl start docker.service Create Centos 7 container with puppet-agent
