Jira (PUP-2289) Puppet will purge the /etc/hosts if it have some invalid lines
Title: Message Title
Daniel Friesen commented on an issue
Re: Puppet will purge the /etc/hosts if it have some invalid lines
Yes, I ran into this issue myself, and I did it without even editing /etc/hosts. ie: Through one mistakes and 2 bugs in puppet I manage to erase the contents of my /etc/hosts puppet using puppet's host type.
I needed to ensure that my ec2 instances had an /etc/hosts entry that ensured that the instance's private ip was associated with the hostname in /etc/hostname.
Since factor couldn't be relied on and I was using puppet apply I used this puppet code:
$fqdn = generate(/bin/hostname)
host { ${fqdn}:
ensure = present,
ip = $ec2_local_ipv4,
host_aliases = [$hostname]
}
Unfortunately due to the fact that the output of /bin/hostname ends with a newline it resulted in puppet adding this to /etc/hosts on the first puppet run (since host didn't bother sanitizing the hostname):
###.###.###.### foo.example.net
foo
Then on the second puppet run because puppet couldn't read the corrupt syntax it inserted into it in the first place, it went and purged the entire hosts file when trying to ensure that the corrupt entry was in the file.
Add Comment
Puppet / PUP-2289
Puppet will purge the /etc/hosts if it have some invalid lines
normally, i use puppet resource host puppet ip=xxx.xxx.xxx.xxx can add/set a domain name resolution into
Jira (PDB-566) PR (125): Ensure db and db users created before validation - rickerc
Title: Message Title gepetto-bot commented on an issue Re: PR (125): Ensure db and db users created before validation - rickerc Pull request Ensure db and db users created before validation has been reopened. Add Comment PuppetDB / PDB-566 PR (125): Ensure db and db users created before validation - rickerc h2. Ensure db and db users created before validation * Author: Chris Ricker * Company: * Github ID: [rickerc|https://github.com/rickerc] * [Pull Request 125 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/125] * [Pull Request 125 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/125/files] h2. Pull Re... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2872) Problem with variable in array for template
Title: Message Title
Vincent created an issue
Puppet / PUP-2872
Problem with variable in array for template
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Kylo Ginsberg
Components:
Client
Created:
01/Jul/14 3:34 AM
Environment:
Centos 6.5, puppet 3.6.2
Priority:
Normal
Reporter:
Vincent
I have the following parameters in my class manifest :
$datadir = '/home/test', $confarray = [datadir = $ {datadir}
,log-file = /var/log/$ {fqdn}], And the following in my conf template : %- @confarray.each do |conf| -% %= conf % %- end -% The output on my conf file is : datadir = log-file = /var/log/my.hostname.com Facter variable $fqdn is correctly translated, but $datadir stays blank. I tried on template : %- @confarray.each do |conf| -% %= conf % %- end -% %= @datadir % the output is : datadir = log-file = /var/log/my.hostname.com /home/test So template knows correctly my variable. I tried in manifest : $confarray = [datadir = %= @datadir %,log-file = /var/log/${fqdn}
],
but
Jira (PDB-566) PR (125): Ensure db and db users created before validation - rickerc
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-566 PR (125): Ensure db and db users created before validation - rickerc Change By: Kenneth Barber Component/s: Module Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-724) PR (130): implement max_threads option for jetty - stefanandres
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-724 PR (130): implement max_threads option for jetty - stefanandres Change By: Kenneth Barber Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-685) PR (128): add parameter 'max_threads' to define value in jetty.ini - mklette
Title: Message Title gepetto-bot commented on an issue Re: PR (128): add parameter 'max_threads' to define value in jetty.ini - mklette kbarber commented: Lets go with #130. Not having baked-in defaults is a better behaviour. Add Comment PuppetDB / PDB-685 PR (128): add parameter 'max_threads' to define value in jetty.ini - mklette h2. add parameter 'max_threads' to define value in jetty.ini * Author: Mathias Klette mathias.kle...@gmx.de * Company: * Github ID: [mklette|https://github.com/mklette] * [Pull Request 128 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/128] * [Pull Request 128 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/128... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-724) PR (130): implement max_threads option for jetty - stefanandres
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-724 PR (130): implement max_threads option for jetty - stefanandres Change By: Kenneth Barber Component/s: Module Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-685) PR (128): add parameter 'max_threads' to define value in jetty.ini - mklette
Title: Message Title gepetto-bot commented on an issue Re: PR (128): add parameter 'max_threads' to define value in jetty.ini - mklette Pull request add parameter 'max_threads' to define value in jetty.ini has been closed. Add Comment PuppetDB / PDB-685 PR (128): add parameter 'max_threads' to define value in jetty.ini - mklette h2. add parameter 'max_threads' to define value in jetty.ini * Author: Mathias Klette mathias.kle...@gmx.de * Company: * Github ID: [mklette|https://github.com/mklette] * [Pull Request 128 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/128] * [Pull Request 128 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/128... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-724) PR (130): implement max_threads option for jetty - stefanandres
Title: Message Title gepetto-bot commented on an issue Re: PR (130): implement max_threads option for jetty - stefanandres stefanandres commented: Okay, I removed the assumption. Add Comment PuppetDB / PDB-724 PR (130): implement max_threads option for jetty - stefanandres h2. implement max_threads option for jetty * Author: Stefan Andres s.and...@syseleven.de * Company: SysEleven GmbH * Github ID: [stefanandres|https://github.com/stefanandres] * [Pull Request 130 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/130] * [Pull Request 130 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pul... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-566) PR (125): Ensure db and db users created before validation - rickerc
Title: Message Title gepetto-bot commented on an issue Re: PR (125): Ensure db and db users created before validation - rickerc Pull request Ensure db and db users created before validation has been closed. Add Comment PuppetDB / PDB-566 PR (125): Ensure db and db users created before validation - rickerc h2. Ensure db and db users created before validation * Author: Chris Ricker * Company: * Github ID: [rickerc|https://github.com/rickerc] * [Pull Request 125 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/125] * [Pull Request 125 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/125/files] h2. Pull Re... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-724) PR (130): implement max_threads option for jetty - stefanandres
Title: Message Title gepetto-bot commented on an issue Re: PR (130): implement max_threads option for jetty - stefanandres Pull request implement max_threads option for jetty has been closed. Add Comment PuppetDB / PDB-724 PR (130): implement max_threads option for jetty - stefanandres h2. implement max_threads option for jetty * Author: Stefan Andres s.and...@syseleven.de * Company: SysEleven GmbH * Github ID: [stefanandres|https://github.com/stefanandres] * [Pull Request 130 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/130] * [Pull Request 130 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pul... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-669) PR (127): Allow more flexible routes configuration - dalen
Title: Message Title gepetto-bot commented on an issue Re: PR (127): Allow more flexible routes configuration - dalen Pull request Allow more flexible routes configuration has been closed. Add Comment PuppetDB / PDB-669 PR (127): Allow more flexible routes configuration - dalen h2. Allow more flexible routes configuration * Author: Erik Daln erik.gustav.da...@gmail.com * Company: Spotify * Github ID: [dalen|https://github.com/dalen] * [Pull Request 127 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/127] * [Pull Request 127 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/127/files] h2... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-724) PR (130): implement max_threads option for jetty - stefanandres
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-724 PR (130): implement max_threads option for jetty - stefanandres Change By: Kenneth Barber Sprint: 20140618to20140702 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-669) PR (127): Allow more flexible routes configuration - dalen
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-669 PR (127): Allow more flexible routes configuration - dalen Change By: Kenneth Barber Sprint: 20140507to20140521 ,20140618to20140702 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-566) PR (125): Ensure db and db users created before validation - rickerc
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-566 PR (125): Ensure db and db users created before validation - rickerc Change By: Kenneth Barber Sprint: 20140326to20140409,20140409to20140423 ,20140618to20140702 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-50) Additional query support for structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-50 Additional query support for structured facts Change By: Kenneth Barber Story Points: 13 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-708) Storage for structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-708 Storage for structured facts Change By: Kenneth Barber Story Points: 21 13 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-713) Modify anonymization tool to support structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-713 Modify anonymization tool to support structured facts Change By: Kenneth Barber Oncestructuredfactsisenabledtheanonymizationtoolwillneedtobemodifiedtosupportthenewformat. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Alexandros Kosiaris created an issue Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output Issue Type: Bug Affects Versions: 3.6.2 Assignee: Alexandros Kosiaris Components: Community Created: 01/Jul/14 4:07 AM Priority: Trivial Reporter: Alexandros Kosiaris Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-712) Modify export and import tool to support structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-712 Modify export and import tool to support structured facts Change By: Kenneth Barber Withstructuredfactstheexportandimporttoolwillneedtobemodifiedtosupportthenewformat. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2706) Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Title: Message Title
Kenneth Barber commented on an issue
Re: Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
FYI this is still happening at a rate of about 1 every ~6 builds: http://jenkins-release.delivery.puppetlabs.net/job/puppetdb-packaging-2014-07-01-03-31-05-b88cb5a03e9b37735a93bc2655cba6c8b89f056c/command=pl_deb%20COW=base-trusty-i386.cow/1/
I think the idea that has been suggested is worth trying I guess, didn't mean to sound that negative about it .
Add Comment
Puppet / PUP-2706
Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
We keep getting this error during Puppet installation for our PuppetDB builds: {code} Setting up ruby-augeas (0.5.0-2) ... Setting up libaugeas-ruby (0.5.0-2) ... Setting up ruby-shadow (2.2.0-1) ... Setting up ruby-json (1.8.0-1build1) ... Setting up hiera (1.3.3-1puppetlabs1) ... Setting up puppet-common (3.6.1-1puppetlabs1) ... chage: the sha...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To
Jira (PDB-704) PuppetDB installing postgresql is not optional
Title: Message Title Kenneth Barber commented on an issue Re: PuppetDB installing postgresql is not optional This was fixed here: https://github.com/puppetlabs/puppetlabs-puppetdb/pull/121 Add Comment PuppetDB / PDB-704 PuppetDB installing postgresql is not optional The puppetlabs-puppetdb module installs PostgreSQL, and this is not optional. This means it is not possible to install postgresql separately with a tuned configuration for your environment, or in a manner that could be reused by other services. Either make the installation of the PuppetDB optiona via a parameter, or remove it completely. By param... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-490) pe_puppetdb module doesn't manage the whole JAVA_ARGS line in /etc/sysconfig/pe-puppetdb
Title: Message Title
Kenneth Barber commented on an issue
Re: pe_puppetdb module doesn't manage the whole JAVA_ARGS line in /etc/sysconfig/pe-puppetdb
Kenn Hussey the downstream ticket has been closed. Whats the status of this fix for puppetlabs-puppetdb?
Add Comment
PuppetDB / PDB-490
pe_puppetdb module doesn't manage the whole JAVA_ARGS line in /etc/sysconfig/pe-puppetdb
By default /etc/sysconfig/pe-puppetdb looks like this: {noformat} ### # Init settings for pe-puppetdb ### # Location of your Java binary (version 6 or higher) JAVA_BIN=/opt/puppet/bin/java # Modify this if you'd like to change the memory allocation, enable JMX, ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Alexandros Kosiaris updated an issue Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output Change By: Alexandros Kosiaris Affects Version/s: 3.6.2 Affects Version/s: 3.2.1 Affects Version/s: 2.7.23 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-731) Is there a bug targeted at the release for every commit?
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-731 Is there a bug targeted at the release for every commit? Issue Type: Sub-task Assignee: Unassigned Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber Ensure that all commits in git between the last and current release have corresponding tickets pointing at this release. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) --
Jira (PDB-736) Packages pushed
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-736 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber Distribute the packages previously built into their public places. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop
Jira (PDB-738) Update the downloads page
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-738 Update the downloads page Issue Type: Sub-task Assignee: Melissa Stone Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber Update the downloads page with the public download locations and new version information. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To
Jira (PUP-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Alexandros Kosiaris commented on an issue Re: puppet master --compile right now unconditionally spews logs to standard output running puppet master --compile spews logs to the stdout. This can not be avoided. Puppet master --compile should honor --logdest or configuration and log there Add Comment Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-737) Push tag
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-737 Push tag Issue Type: Sub-task Assignee: Melissa Stone Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber Push the tag made earlier up to the main public repo for the branch in question. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and
Jira (PDB-729) Update documentation indexes for new major release
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-729 Update documentation indexes for new major release Issue Type: Sub-task Assignee: Unassigned Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber The current documentation indexes need to be updated for a final release. The main index needs the release to be moved into the stable section, and the index for this release needs the pre-release meesage removed. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-735) Go/no-go meeting
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-735 Go/no-go meeting Issue Type: Sub-task Assignee: Unassigned Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber Should include: dev, docs, product, qa, releng Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from
Jira (PDB-732) Is there a commit for every bug targeted at the release?
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-732 Is there a commit for every bug targeted at the release? Issue Type: Sub-task Assignee: Unassigned Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber Ensure that all tickets targetted at this release have corresponding commits in git. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because
Jira (PDB-727) Is checklist current
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-727 Is checklist current Issue Type: Sub-task Assignee: Unassigned Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber Do sub-tickets here match steps in https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process? And do those steps need updating for any recent tooling changes? Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-740) Push changes to pe-puppetdb branch
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-740 Push changes to pe-puppetdb branch Issue Type: Sub-task Assignee: Unassigned Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber These changes will need to be pushed to the relevant branch for pe-puppetdb Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google
Jira (PDB-733) Tag the release and create packages
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-733 Tag the release and create packages Issue Type: Sub-task Assignee: Melissa Stone Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber Developer provides the SHA Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from
Jira (PDB-741) Close all resolved tickets and release version in Jira
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-741 Close all resolved tickets and release version in Jira Issue Type: Sub-task Assignee: Unassigned Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber Ensure all tickets that were previously resolved are marked now as closed. Ensure the version in Jira is released. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You
Jira (PDB-726) PuppetDB 2.1.0 Release
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-726 PuppetDB 2.1.0 Release Issue Type: Task Assignee: Kenneth Barber Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber See https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and
Jira (PDB-730) Ensure tests are passing
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-730 Ensure tests are passing Issue Type: Sub-task Assignee: Unassigned Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber All tests (spec, acceptance) should be passing on all platforms. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs
Jira (PDB-734) Smoke test packages
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-734 Smoke test packages Issue Type: Sub-task Assignee: Unassigned Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber Procedure may vary by project and point in the release cycle. Ask around. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet
Jira (PDB-739) Send out announcements
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-739 Send out announcements Issue Type: Sub-task Assignee: Unassigned Created: 01/Jul/14 4:20 AM Priority: Normal Reporter: Kenneth Barber Send out the release notes in the release format on puppet-users, puppet-dev and puppet-announce. Obtain a bit.ly link to such a thing from marketing and twitter it out, and send a PSA message to IRC channels #puppet and #puppet-dev. Update our hipchat channel with the new link. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Alexandros Kosiaris commented on an issue Re: puppet master --compile right now unconditionally spews logs to standard output https://github.com/puppetlabs/puppet/pull/2637 Add Comment Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-726) PuppetDB 2.1.0 Release
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-726 PuppetDB 2.1.0 Release Change By: Kenneth Barber Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-726) PuppetDB 2.1.0 Release
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-726 PuppetDB 2.1.0 Release Change By: Kenneth Barber Sprint: 20140702to20140716 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-726) PuppetDB 2.1.0 Release
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-726 PuppetDB 2.1.0 Release Change By: Kenneth Barber Fix Version/s: 2.1.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2271) yumrepo attributes cannot be set to '_none_'
Title: Message Title
Sam Kottler commented on an issue
Re: yumrepo attributes cannot be set to '_none_'
This patch has been applied to the Puppet package in EPEL7. I'm considering backporting it to 2.7.x, but it's non-trivial AFAICT.
Add Comment
Puppet / PUP-2271
yumrepo attributes cannot be set to '_none_'
The {{yumrepo}} attribute cannot be set to the value _none_ even though this is a supported value for the yum {{proxy}} parameter. We should fix this. {code} $ puppet apply -e yumrepo {'base': proxy = '_none_'} Notice: Compiled catalog for localhost.localdomain in environment production in 0.03 seconds Error: Parameter proxy failed on Yumrepo[b...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2784) Run puppet specs against windows ruby 2.0 x64
Title: Message Title Rob Reynolds commented on an issue Re: Run puppet specs against windows ruby 2.0 x64 Bundler gems will also need to be updated to at least 1.6.x. I'll add and link a ticket. Add Comment Puppet / PUP-2784 Run puppet specs against windows ruby 2.0 x64 Add a cell to the Puppet-Specs-Windows-master job to test puppet specs against ruby 2.0 x64. Due to https://tickets.puppetlabs.com/browse/QENG-785, you will need to look at the job log, and verify that the specs actually pass. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-715) Create PuppetDB 2.1.0 blog post
Title: Message Title Kenneth Barber commented on an issue Re: Create PuppetDB 2.1.0 blog post https://docs.google.com/a/puppetlabs.com/document/d/1E0ZqmDtb6zu_5Ce_H8Mh8sf9TnKg8L4vksO0atPhYgg/edit# Add Comment PuppetDB / PDB-715 Create PuppetDB 2.1.0 blog post Need a description for new PDB release. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2784) Run puppet specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper commented on an issue Re: Run puppet specs against windows ruby 2.0 x64 Hmm, I'm not sure we want to rely on a specific version being preinstalled. For Windows spec jobs, e.g. https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Stable/job/Puppet-Specs-Windows-stable, we install bunlder in the jenkins job itself: pre cmd /c gem install bundler -v 1.2.4 --no-rdoc --no-ri cmd /c bundle install --without development extra --path vendor\cache /pre This way we're not dependent on whatever version of bundler happens to be installed. Ideally the bundler version would live in the puppet repo, but there is a bit of a bootstrapping issue, and that is a bigger issue than this ticket. Add Comment Puppet / PUP-2784 Run puppet specs against windows ruby 2.0 x64 Add a cell to the Puppet-Specs-Windows-master job to test puppet specs against ruby 2.0 x64. Due to https://tickets.puppetlabs.com/browse/QENG-785, you will need to look at the job log, and verify that the specs actually pass. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) --
Jira (PUP-1035) Default setting for pluginsource problematic for deployments using SRV records
Title: Message Title Jesse Cotton commented on an issue Re: Default setting for pluginsource problematic for deployments using SRV records I am also having this issue. See below: Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: getaddrinfo: Name or service not known Could not retrieve file metadata for puppet://puppet/pluginfacts: getaddrinfo: Name or service not known /usr/lib/ruby/site_ruby/1.8/puppet/util/errors.rb:97:in `fail' /usr/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:178:in `metadata' /usr/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:170:in `each' /usr/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:170:in `metadata' /usr/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:111:in `copy_source_values' /usr/lib/ruby/site_ruby/1.8/puppet/type/file.rb:637:in `retrieve' /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:1063:in `retrieve_resource' /usr/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:223:in `from_resource' /usr/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:19:in `evaluate' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:174:in `apply' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:187:in `eval_resource' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:117:in `call' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:117:in `evaluate' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:327:in `thinmark' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:326:in `thinmark' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:117:in `evaluate' /usr/lib/ruby/site_ruby/1.8/puppet/graph/relationship_graph.rb:118:in `traverse' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:108:in `evaluate' /usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:164:in `apply' /usr/lib/ruby/site_ruby/1.8/puppet/util/log.rb:153:in `with_destination' /usr/lib/ruby/site_ruby/1.8/puppet/transaction/report.rb:108:in `as_logging_destination' /usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:163:in `apply' /usr/lib/ruby/site_ruby/1.8/puppet/configurer/downloader.rb:14:in `evaluate' /usr/lib/ruby/1.8/timeout.rb:67:in `timeout' /usr/lib/ruby/site_ruby/1.8/puppet/configurer/downloader.rb:13:in `evaluate' /usr/lib/ruby/site_ruby/1.8/puppet/configurer/plugin_handler.rb:22:in `download_plugins' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:93:in `get_facts' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:167:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:44:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:20:in `lock' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:44:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:114:in `with_client' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:41:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:79:in `run_in_fork' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:40:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:179:in `call' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:179:in `controlled_run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:38:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:355:in `onetime' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:321:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:364:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:470:in `plugin_hook' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:364:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:478:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:364:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:137:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:91:in `execute' /usr/bin/puppet:4
Jira (PDB-726) PuppetDB 2.1.0 Release - 2014/7/8
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-726 PuppetDB 2.1.0 Release - 2014/7/8 Change By: Kenneth Barber Summary: PuppetDB2.1.0Release -2014/7/8 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-708) Storage for structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-708 Storage for structured facts Change By: Kenneth Barber Sprint: 20140702to20140716 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2872) Problem with variable in array for template
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2872
Problem with variable in array for template
Change By:
Henrik Lindberg
Ihavethefollowingparametersinmyclassmanifest: {code} $datadir='/home/test',$confarray=[datadir=${datadir},log-file=/var/log/${fqdn}], {code} Andthefollowinginmyconftemplate: {code} %-@confarray.eachdo|conf|-%%=conf%%-end-% {code} Theoutputonmyconffileis: {code} datadir=log-file=/var/log/my.hostname.com {code} Factervariable$fqdniscorrectlytranslated,but$datadirstaysblank.Itriedontemplate: {code} %-@confarray.eachdo|conf|-%%=conf%%-end-%%=@datadir% {code} theoutputis: {code} datadir=log-file=/var/log/my.hostname.com/home/test {code} Sotemplateknowscorrectlymyvariable.Itriedinmanifest: {code} $confarray=[datadir=%=@datadir%,log-file=/var/log/${fqdn}], {code} buttheoutputis: {code} datadir=%=@datadir%log-file=/var/log/my.hostname.com {code} Variableisnottranslated,eveninruby.HowcanImanagethis?
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2872) Problem with variable in array for template
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2872 Problem with variable in array for template Change By: Henrik Lindberg Assignee: KyloGinsberg AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2872) Problem with variable in array for template
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2872 Problem with variable in array for template Change By: Henrik Lindberg Component/s: Client Component/s: Server Component/s: DSL Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-49) Store structured facts as JSON server side
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-49 Store structured facts as JSON server side Change By: Kenneth Barber Sprint: 20140702to20140716 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2872) Problem with variable in array for template
Title: Message Title
Henrik Lindberg commented on an issue
Re: Problem with variable in array for template
Can you post a self contained .pp example using an inline template that shows the problem? I suspect there is something going on in your code that is not shown above.
Add Comment
Puppet / PUP-2872
Problem with variable in array for template
I have the following parameters in my class manifest : {code} $datadir = '/home/test', $confarray = [datadir = ${datadir},log-file = /var/log/${fqdn}], {code} And the following in my conf template : {code} %- @confarray.each do |conf| -% %= conf % %- end -% {code} The output on my conf file is : {code} datadir = log-file = /var/log...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2872) Problem with variable in array for template
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2872 Problem with variable in array for template Change By: Henrik Lindberg Assignee: AndyParker Vincent Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-716) HTTP API gets stuck
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-716 HTTP API gets stuck Change By: Ryan Senior Sprint: 20140618to20140702 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-162) Regexp match doesn't work on resource parameters
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-162 Regexp match doesn't work on resource parameters Change By: Ryan Senior Sprint: 20140618to20140702 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-162) Regexp match doesn't work on resource parameters
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-162 Regexp match doesn't work on resource parameters Change By: Ryan Senior Assignee: RyanSenior Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2752) Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format
Title: Message Title Brandon High assigned an issue to Brandon High Puppet / PUP-2752 Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format Change By: Brandon High Assignee: PietervandeBruggen BrandonHigh Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2784) Run puppet specs against windows ruby 2.0 x64
Title: Message Title Rob Reynolds commented on an issue Re: Run puppet specs against windows ruby 2.0 x64 Fair enough... but would you say that for x64 it is definitely required or not required? Plus it would allow us to take advantage of parallel execution (v1.5+) of gem installation, which could shave off a little time (mostly during acceptance though). Add Comment Puppet / PUP-2784 Run puppet specs against windows ruby 2.0 x64 Add a cell to the Puppet-Specs-Windows-master job to test puppet specs against ruby 2.0 x64. Due to https://tickets.puppetlabs.com/browse/QENG-785, you will need to look at the job log, and verify that the specs actually pass. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2784) Run puppet specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper commented on an issue Re: Run puppet specs against windows ruby 2.0 x64 I think not required for x64 support. We can just update the jenkins job to require a newer bundler version for spec jobs. For acceptance, we pull our vendored ruby and run the puppet agent against that. So no bundler involved there. Add Comment Puppet / PUP-2784 Run puppet specs against windows ruby 2.0 x64 Add a cell to the Puppet-Specs-Windows-master job to test puppet specs against ruby 2.0 x64. Due to https://tickets.puppetlabs.com/browse/QENG-785, you will need to look at the job log, and verify that the specs actually pass. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2784) Run puppet specs against windows ruby 2.0 x64
Title: Message Title Rob Reynolds commented on an issue Re: Run puppet specs against windows ruby 2.0 x64 We did find an issue that took up several hours yesterday where we had a misunderstanding of whether we were running against an x64 plat based on using an older bundler on 1.9.3. Would prefer that we validate it works with older bundlers, but also that it works with newer versions. Add Comment Puppet / PUP-2784 Run puppet specs against windows ruby 2.0 x64 Add a cell to the Puppet-Specs-Windows-master job to test puppet specs against ruby 2.0 x64. Due to https://tickets.puppetlabs.com/browse/QENG-785, you will need to look at the job log, and verify that the specs actually pass. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-675) init.d script silently fails if PIDfile is missing
Title: Message Title
Kenneth Barber commented on an issue
Re: init.d script silently fails if PIDfile is missing
Alex Jurkiewicz do you know how exactly the PID file was missing? Was this during an upgrade of a previous PuppetDB package? If so what exact version did you upgrade from?
Add Comment
PuppetDB / PDB-675
init.d script silently fails if PIDfile is missing
Debugging log: init.d restart fails but silently exits 0. Missing pidfile but still running application -- killing application fixes issue. {code}# sh -x /etc/init.d/puppetdb stop + [ -r /etc/default/puppetdb ] + . /etc/default/ + [ -f /usr/lib/jvm/java-7-openjdk-amd64/bin/java ] + JAVA_BIN=/usr/lib/jvm/java-7-openjdk-amd64/bin/java + JAVA_ARGS=-X...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Rob Reynolds commented on an issue Re: Remove win32console gem in ruby 2.0 on windows Fixing some of the other specs and sending a new PR. Add Comment Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Ruby 2.0 on windows supports ANSI escape sequences, so the win32console gem is unnecessary. Also, ruby 2.0 likely support unicode character output correctly (such as the unicode box characters used in module tool output), so the windows-specific code in `lib/puppet/util/colors.rb` to force wide character output can be removed. See https://github.com/l... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2867) Support user home directories (Unix) in file resources
Title: Message Title Rob Reynolds commented on an issue Re: Support user home directories (Unix) in file resources This could cause puppet to be non-deterministic, which I'm slowly coming to terms on based on my want for PUP-855. Add Comment Puppet / PUP-2867 Support user home directories (Unix) in file resources It is currently not possible to use paths in the form of `~user` in file resources, but it would be very useful, so home directories are resolved on the agent. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-742) '[replace catalog]' postgresql errors with index 'catalog_resources_pkey'
Title: Message Title
Mathew Crane updated an issue
PuppetDB / PDB-742
'[replace catalog]' postgresql errors with index 'catalog_resources_pkey'
Change By:
Mathew Crane
Affects Version/s:
2.0.0
Summary:
'[replacecatalog] 'postgresqlerrorswithindex'catalog_resources_pkey'
Duringtestingofpuppetdbinourenvironment,itwasdeterminedthatcertain'exec'statementswouldcausethefollowingerrorwhenattemptingtouploadthecatalogtopuppetdb:{noformat}2014-05-3008:20:15,328ERROR[c.p.p.command][...][replacecatalog]Retryingafterattempt6,dueto:org.postgresql.util.PSQLException:ERROR:indexrowsize4296exceedsmaximum2712forindexcatalog_resources_pkeyHint:Valueslargerthan1/3ofabufferpagecannotbeindexed.ConsiderafunctionindexofanMD5hashofthevalue,orusefulltextindexing.{noformat}PerKenBarber,catalog_resources_pkeyisaacombinationofcatalog_id(biginit),thetypeandthetitle(bothtextfields).Changingourexecstatementstohaveapropertitleinsteadofhavingtheactual(very,verylong)commandasthetitlefixedtheissue.Submittingthisticketforanyadditionaltroubleshootingorimprovementsthatcouldbeimplementedasaresultofthis.https://groups.google.com/d/msg/puppet-users/9L1fsPq-nx8/0CbV3f2Vzb0J
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2752) Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format
Title: Message Title Brandon High commented on an issue Re: Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format I've started working on a fix for this. Add Comment Puppet / PUP-2752 Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format Since Puppet 3.6.0 the module tool is unable to install new modules if an already existing modules version does not conform to the MAJOR.MINOR.PATCH format. I believe this behaviour was introduced with the dependency resolver ( https://github.com/puppetlabs/puppet/commit/6fa68b54ac621d60dbf1b062f8dd66b186d1a87f ) How to reproduce problem: * Place a... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to 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-855) On Windows allow using root path for file type
Title: Message Title Rob Reynolds commented on an issue Re: On Windows allow using root path for file type Due to it's non-deterministic nature, it goes against what puppet considers an accurate location. While you can already get a non-deterministic nature with variables that depend on system environment information, building it into core puppet seems incorrect. Perhaps a module that would add this behavior would be more plausible as someone would be opting into this nature. Add Comment Puppet / PUP-855 On Windows allow using root path for file type This would allow full path in a way that doesn't require specifying the drive to look at. When this is specified, we will use SYSTEMDRIVE. This would allow multiple computers with different system drives to be able to use the same manifests. This could also open the door for more platforms using the same manifest with less use of selectors based on the O... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PDB-742) '[replace catalog]
Title: Message Title Mathew Crane created an issue PuppetDB / PDB-742 '[replace catalog] Issue Type: Bug Assignee: Unassigned Created: 01/Jul/14 11:48 AM Priority: Normal Reporter: Mathew Crane Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1811) in with regexps should set match variables
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1811 in with regexps should set match variables Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1027) Add warning for use of bare words that clash with new keywords
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1027 Add warning for use of bare words that clash with new keywords Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1811) in with regexps should set match variables
Title: Message Title
Andy Parker commented on an issue
Re: in with regexps should set match variables
The changes for this caused a failure in acceptance tests that exercised virtual resource collection. This uncovered that the integration tests we have for resource collection aren't being run against the future parser. In addition the particular case that was in the failed acceptance tests were not covered by the spec/integration test.
Add Comment
Puppet / PUP-1811
in with regexps should set match variables
{noformat} if /.(a)/ in [b, c, baba] { notice($0) notice($1) } {noformat} results in ba and a being output.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-675) init.d script silently fails if PIDfile is missing
Title: Message Title Melissa Stone assigned an issue to Melissa Stone PuppetDB / PDB-675 init.d script silently fails if PIDfile is missing Change By: Melissa Stone Assignee: MelissaStone Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2429) Provide a way to expose trusted facts to PuppetDB (and other terminus consumers)
Title: Message Title
Peter Huene commented on an issue
Re: Provide a way to expose trusted facts to PuppetDB (and other terminus consumers)
It seems the API already makes the trusted information available while processing HTTP requests:
Adding this to Puppet::Node::Facts::Puppetdb#save in puppetdb.rb
trusted = Puppet.lookup(:trusted_information) { Puppet::Context::TrustedInformation.local(request.node) }.to_h
# do something with the hash...
Should do the trick, no?
Add Comment
Puppet / PUP-2429
Provide a way to expose trusted facts to PuppetDB (and other terminus consumers)
PDB-565 covers the need to store trusted facts in PuppetDB, but right now I don't believe we have a suitable API contract for getting this information from Puppet. At least I can't find one, neither the facts terminus nor the catalog terminus supplies this for example. One solution to this is to include the set of trusted facts in the request object su...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1811) in with regexps should set match variables
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-1811 in with regexps should set match variables Change By: Andy Parker Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output Change By: Adrien Thebo Component/s: Server Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Adrien Thebo commented on an issue Re: puppet master --compile right now unconditionally spews logs to standard output Merged in e182038. Add Comment Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output Change By: Adrien Thebo Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1811) in with regexps should set match variables
Title: Message Title
Henrik Lindberg commented on an issue
Re: in with regexps should set match variables
Merged to master: 0346843
Add Comment
Puppet / PUP-1811
in with regexps should set match variables
{noformat} if /.(a)/ in [b, c, baba] { notice($0) notice($1) } {noformat} results in ba and a being output.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2752) Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2752 Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format Change By: Anderson Mills Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2079) puppet module generate can't copy template files without parsing/renaming them
Title: Message Title Adrien Thebo commented on an issue Re: puppet module generate can't copy template files without parsing/renaming them Merged in 21267b7. Add Comment Puppet / PUP-2079 puppet module generate can't copy template files without parsing/renaming them When creating a new module with puppet module generate, any files in the skeleton dir named *.erb are parsed as Ruby erb templates and renamed, removing the file extension. This is a pain if you want to include template files in your skeleton directory. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2752) Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format
Title: Message Title Brandon High updated an issue Puppet / PUP-2752 Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format Change By: Brandon High Sprint: Week2014-6-25to2014-7-9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title Adrien Thebo commented on an issue Re: module skeleton is using deprecated way to configure spec_helper garrett honeycutt now that PUP-2079 is merged does anything need to be updated to allow your PR to be merged? Add Comment Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper [~josh] states that we are using a deprecated method for configuring rspec This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Rob Reynolds commented on an issue Re: Remove win32console gem in ruby 2.0 on windows Actually doesn't appear that this is necessary. Add Comment Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Ruby 2.0 on windows supports ANSI escape sequences, so the win32console gem is unnecessary. Also, ruby 2.0 likely support unicode character output correctly (such as the unicode box characters used in module tool output), so the windows-specific code in `lib/puppet/util/colors.rb` to force wide character output can be removed. See https://github.com/l... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2745) Puppet 3.6.1 issue with Forge API v3
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2745 Puppet 3.6.1 issue with Forge API v3 Change By: Anderson Mills Sprint: Week2014-6-25to2014-7-9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2745) Puppet 3.6.1 issue with Forge API v3
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2745 Puppet 3.6.1 issue with Forge API v3 Change By: Anderson Mills Fix Version/s: 3.5.1 Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2875) Error 400 on SERVER: undefined method `[]' for nil:NilClass
Title: Message Title Daniel Rahamim created an issue Puppet / PUP-2875 Error 400 on SERVER: undefined method `[]' for nil:NilClass Issue Type: Bug Affects Versions: 3.6.2 Assignee: Kylo Ginsberg Components: Client Created: 01/Jul/14 4:07 PM Environment: Ubuntu 64-bit 12.04 Priority: Normal Reporter: Daniel Rahamim When running puppet agent -t I receive: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `[]' for nil:NilClass on node **PUPPETMASTERNAME** Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1283) Update win32-service gem
Title: Message Title Rob Reynolds commented on an issue Re: Update win32-service gem Patch has been submitted upstream. Will put a fix into our code if we don't get a response on this soon. Add Comment Puppet / PUP-1283 Update win32-service gem The win32-service gem was patched upstream to resolve #16080. The fix was merged upstream https://github.com/djberg96/win32-service/pull/8. At a minimum we need to update the gem and remove the patch https://github.com/puppetlabs/puppet-win32-ruby/blob/1.9.3/16080-handle-missing-description.patch. We also need to make sure we can update to the `ffi` b... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-568) Run Facter specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Facter / FACT-568 Run Facter specs against windows ruby 2.0 x64 Change By: Josh Cooper AddacelltotheFacter-Specs-Windows-stable master facter-2 jobstotestfacterspecsagainstruby2.0x64.Duetohttps://tickets.puppetlabs.com/browse/QENG-785,youwillneedtolookatthejoblog,andverifythatthespecsactuallypass. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-568) Run Facter specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Facter / FACT-568 Run Facter specs against windows ruby 2.0 x64 Change By: Josh Cooper AddacelltotheFacter-Specs-Windows- stable master job jobs totestfacterspecsagainstruby2.0x64.Duetohttps://tickets.puppetlabs.com/browse/QENG-785,youwillneedtolookatthejoblog,andverifythatthespecsactuallypass. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Josh Cooper commented on an issue Re: Remove win32console gem in ruby 2.0 on windows Verified ruby 1.9.3 x86: Specs pass, color correctlyshown when running bundle exec rake ci:spec, and when installing a module (the version component is colorized): C:\work\puppetbundle exec puppet module install puppetlabs/registry ... C:/ProgramData/PuppetLabs/puppet/etc/modules └─┬ puppetlabs-registry (v1.0.0) └── puppetlabs-stdlib (v4.2.1) Verified ruby 2.0.0 x64 Color specific specs pass (not all specs pass yet), color correctly shown when running specs, and when listing modules: C:\work\puppet bundle exec puppet module list DL is deprecated, please use Fiddle DL is deprecated, please use Fiddle C:/ProgramData/PuppetLabs/puppet/etc/modules ├── dprince-qpid (v1.0.2) ├── duritong-sysctl (v0.0.4) ├── garethr-erlang (v0.3.0) ├── puppetlabs-apache (v1.0.1) ... Add Comment Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Ruby 2.0 on windows supports ANSI escape sequences, so the win32console gem is unnecessary. Also, ruby 2.0 likely support unicode character output correctly (such as the unicode box characters used in module tool output), so the windows-specific code in `lib/puppet/util/colors.rb` to force wide character output can be removed. See https://github.com/l...
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Josh Cooper commented on an issue Re: Remove win32console gem in ruby 2.0 on windows Merged in b5171fc11 to master to be released in 3.7.0 Add Comment Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Ruby 2.0 on windows supports ANSI escape sequences, so the win32console gem is unnecessary. Also, ruby 2.0 likely support unicode character output correctly (such as the unicode box characters used in module tool output), so the windows-specific code in `lib/puppet/util/colors.rb` to force wide character output can be removed. See https://github.com/l... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-568) Run Facter specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Facter / FACT-568 Run Facter specs against windows ruby 2.0 x64 Change By: Josh Cooper Sprint: Week2014- 7 6 - 9 25 to2014-7- 23 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-568) Run Facter specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper commented on an issue Re: Run Facter specs against windows ruby 2.0 x64 Updated stable, facter-2, and master branches to include the ci-win2012r2 node, bumped jenkins jobs to gem install bundler -v 1.6.2, and manually verified jobs ran successfully (due to QENG-785): https://jenkins.puppetlabs.com/job/Facter-Specs-Windows-stable/544/ https://jenkins.puppetlabs.com/job/Facter-Specs-Windows-2.0/339/ https://jenkins.puppetlabs.com/job/Facter-Specs-Windows-master/727/ Add Comment Facter / FACT-568 Run Facter specs against windows ruby 2.0 x64 Add a cell to the Facter-Specs-Windows-stable facter-2 jobs to test facter specs against ruby 2.0 x64. Due to https://tickets.puppetlabs.com/browse/QENG-785, you will need to look at the job log, and verify that the specs actually pass. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send
Jira (PUP-744) Pool HTTPS connections
Title: Message Title Josh Cooper commented on an issue Re: Pool HTTPS connections I spiked this effort, and code is https://github.com/joshcooper/puppet/tree/http_pooling. I'm not happy with how TCP connects are issued for non-pooled connections, and I don't like how the pool is added to the context system, but you get the idea. I did some basic performance measurements, agent and webrick master on my laptop, and assuming the agent already has its SSL keys and certs. For steady state puppet agents, applying an empty catalog, execution time went from 4.5 seconds to 4.0 seconds. Note the agent makes 5 HTTP requests to the master in the steady state case, so the extra 4 SSL handshakes accounted for about .5 seconds. I also added 100 empty files to the master's pluginsync lib directory. Execution went from 19.7 seconds to 6.0 seconds, so speedup of over 3x. Add Comment Puppet / PUP-744 Pool HTTPS connections Reduce network traffic and latency This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google
Jira (PDB-743) Report submission fails on JSON::ParserError
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-743 Report submission fails on JSON::ParserError The attached files, logs.tar.gz, contain everything under /var/log from the master. Change By: Kurt Wall Attachment: logs.tar.gz Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
