Jira (PUP-1100) create_resources auto importing a manifest with a syntax error produce a bad error message
Title: Message Title
Julien Pivotto commented on an issue
Re: create_resources auto importing a manifest with a syntax error produce a bad error message
See GH-2761
https://github.com/puppetlabs/puppet/pull/2761
Add Comment
Puppet / PUP-1100
create_resources auto importing a manifest with a syntax error produce a bad error message
Given a module with this structure: {noformat} x └── manifests ├── init.pp └── y.pp {noformat} init.pp: {noformat} class x { $r = {one = {foo = bar}} create_resources(x::y, $r) } {noformat} and y.pp which has an obvious syntax error: {code} define x::y { obvious error should be obvious } {code} ...
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-1100) create_resources auto importing a manifest with a syntax error produce a bad error message
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-1100 create_resources auto importing a manifest with a syntax error produce a bad error message Change By: Julien Pivotto Assignee: JulienPivotto 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-1100) create_resources auto importing a manifest with a syntax error produce a bad error message
Title: Message Title Julien Pivotto assigned an issue to Julien Pivotto Puppet / PUP-1100 create_resources auto importing a manifest with a syntax error produce a bad error message Change By: Julien Pivotto Assignee: FelixFrank JulienPivotto 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-1066) yum repos should be ensurable.
Title: Message Title
Timothy Clarke commented on an issue
Re: yum repos should be ensurable.
Having gotten back to the office and now that, I've taken a better look (I was managing the repo's through the file resource with recurse purge), I'd still say 1023 hasn't been completed to what most people would expect.
resources { 'yumrepo' : purge = true }
empties all unmanaged repos in /etc/yum.repos.d, so you still have zero byte *.repo files in that directory and corrupt *.repo files are not corrected in any way eg echo corrupt repo /etc/yum.repos.d/bad.repo results in Error: /Stage[main]/Yumtest/Resources[yumrepo]: Failed to generate additional resources using 'generate': Can't parse line 'corrupt repo' at /etc/yum.repos.d/bad.repo:1 As well as notices creating valid repo's that already existed are managed.
I noticed a bug after doing further testing on this. The reposdir in yum.conf is ignored by the yumrepo resource
Add Comment
Puppet / PUP-1066
yum repos should be ensurable.
This should be done so that we can solve: #949 - yumrepo should support removal of repository #1023 - yumrepo option to purge unmanaged repos
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-705) Initial fact download timeout
Title: Message Title Georg Brunmayr created an issue PuppetDB / PDB-705 Initial fact download timeout Issue Type: Bug Assignee: Unassigned Created: 12/Jun/14 1:41 AM Priority: Major Reporter: Georg Brunmayr In our environment we have situations where the puppet master is under high load and the network to the external locations as well. If a new node is added at that time it happens that the fact download (agent downloads from master) expires: change from absent to file failed: execution expired Unfortunately the agent does never again check if something is missing but just fails on every following run. As a workaround i can copy the fact .rb files manually to the node and everything is fine on the next run. A real solution has to recheck the fact files at least if there was a timeout on the last run and get the missing ones in the next run. Add Comment
Jira (PUP-2770) Initial fact download timeout
Title: Message Title Georg Brunmayr moved an issue Puppet / PUP-2770 Initial fact download timeout Change By: Georg Brunmayr Workflow: Engineering Platform Workflow Key: PDB PUP - 705 2770 Project: PuppetDB Puppet Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2770) Initial fact download timeout
Title: Message Title Georg Brunmayr commented on an issue Re: Initial fact download timeout Agent Config: pluginsync=true autoflush=true environment=production Add Comment Puppet / PUP-2770 Initial fact download timeout In our environment we have situations where the puppet master is under high load and the network to the external locations as well. If a new node is added at that time it happens that the fact download (agent downloads from master) expires: change from absent to file failed: execution expired Unfortunately the agent does never again check if somethin... 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-2770) Initial fact download timeout
Title: Message Title Georg Brunmayr updated an issue Puppet / PUP-2770 Initial fact download timeout Added logfile of that run Change By: Georg Brunmayr Attachment: log.txt 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-548) fact not showing up when run through puppet agent
Title: Message Title Daniele Sluijters updated an issue Facter / FACT-548 fact not showing up when run through puppet agent Change By: Daniele Sluijters Environment: DebianSqueezeandWheezyPuppet3.6.2Facter2.0.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 (FACT-548) fact not showing up when run through puppet agent
Title: Message Title
Daniele Sluijters created an issue
Facter / FACT-548
fact not showing up when run through puppet agent
Issue Type:
Bug
Assignee:
Eric Sorenson
Created:
12/Jun/14 2:32 AM
Priority:
Normal
Reporter:
Daniele Sluijters
I have no clue if this is a Facter bug or a Puppet thing. I have a custom Fact which works when I run it through FACTERLIB=/path/to/fact facter and also shows up when distributed through Puppet and run with facter -p and even works when manually kicking puppet agent -t.
However, when relying simply on the agent the fact doesn't work (and because of that disappears from PuppetDB too).
The fact:
Unable to find source-code formatter for language: ruby. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
Facter.add(:mysql_type) do
confine :kernel = :linux
mysql_output = Facter::Core::Execution.exec('/usr/bin/pt-mysql-summary --defaults-file=/etc/mysql/debian.cnf --sleep 0 2/dev/null')
setcode do
if mysql_output.include?('Percona XtraDB Cluster (GPL)')
'node'
elsif mysql_output.include?('Is a slave, has 0 slaves connected')
'slave'
elsif mysql_output.include?('Is a slave')
'master'
elsif mysql_output.include?('Is not a slave')
'master'
end
end
end
This is probably the most horrible way to parse replication information into something useful but for all intents and purposes seems to work, except that Puppet just doesn't want it.
I've restarted the agents too, no dice.
Jira (HI-46) Hiera should support alternate environments
Title: Message Title Chris Spence commented on an issue Re: Hiera should support alternate environments I rather think that the whole point of the ticket is so you don't have to create another distinct puppet master to be able to traverse a different hierarchy in hiera. Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. 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-2771) service status filed behaves exactly other way than documentation
Title: Message Title
David Edler created an issue
Puppet / PUP-2771
service status filed behaves exactly other way than documentation
Issue Type:
Bug
Affects Versions:
2.7.23
Assignee:
Kylo Ginsberg
Components:
Client
Created:
12/Jun/14 5:29 AM
Priority:
Major
Reporter:
David Edler
The documentation states at http://docs.puppetlabs.com/references/latest/type.html#service-attribute-status
status Specify a status command manually. This command must return 0 if the service is running and a nonzero value otherwise.
But in fact it is exactly the other way round.
For a non running service to be started the status must return 0. If status returns 1 nothing happens.
So this snipped worked for me in the end.
service { 'my-service':
ensure = running,
hasstatus = false,
status = test $(ps fax | grep my-service | wc -l) -eq 0
}
Jira (PUP-2771) service status field behaves exactly other way than documentation
Title: Message Title David Edler updated an issue Puppet / PUP-2771 service status field behaves exactly other way than documentation Change By: David Edler Summary: servicestatus filed field behavesexactlyotherwaythandocumentation 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 (HI-46) Hiera should support alternate environments
Title: Message Title Lee Lowder commented on an issue Re: Hiera should support alternate environments While multiple masters are easy to setup - for both open source and Enterprise users, each master will consume at least one Enterprise license, and potentially 3 licenses if a split install is used. So using multiple masters is one possible workaround for some cases, it is not always a practical or viable one. There is also the cost that comes into effect. While spinning up a new VM is usually relatively cheap, it is not always an insignificant cost in terms of time, effort, hardware and licensing. Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. 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 (PUP-1517) Install puppet in cPAnel servers
Title: Message Title Nathan Flynn commented on an issue Re: Install puppet in cPAnel servers Its nothing to do with Puppet. The problem is cPanel blocks ruby* from YUM and Puppet depends on knowing Ruby is installed via rpm. root@dhcp04 [~]# cat /etc/yum.conf [main] exclude=bind-chroot courier* dovecot* exim* filesystem httpd* mod_ssl* mydns* mysql* nsd* php* proftpd* pure-ftpd* ruby* spamassassin* squirrelmail* The workaround is to remove the ruby* line or try and use ruby gem. Add Comment Puppet / PUP-1517 Install puppet in cPAnel servers I am getting the following errors. While installing puppet client. -- Error: Package: puppet-2.7.23-1.el6.noarch (epel) Requires: ruby(abi) = 1.8 Error: Package: puppet-2.7.23-1.el6.noarch (epel) Requires: /usr/bin/ruby Error: Package: facter-1.6.18-3.el6.x86_64 (epel) Requires: ruby(abi) = 1.8 Error: Package: p... 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-1517) Install puppet in cPAnel servers
Title: Message Title Nathan Flynn assigned an issue to Nathan Flynn Puppet / PUP-1517 Install puppet in cPAnel servers Change By: Nathan Flynn Assignee: NathanFlynn 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 Eric Sorenson updated an issue Puppet / PUP-2429 Provide a way to expose trusted facts to PuppetDB (and other terminus consumers) Change By: Eric Sorenson 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 (FACT-190) couldn't find HOME environment --expanding '~/.facter/facts.d'
Title: Message Title Cassiano Leal commented on an issue Re: couldn't find HOME environment --expanding '~/.facter/facts.d' New PR, after feedback on the previous patch: https://github.com/puppetlabs/facter/pull/691 Add Comment Facter / FACT-190 couldn't find HOME environment --expanding '~/.facter/facts.d' couldn't find HOME environment --expanding '~/.facter/facts.d' facter 1.7.4 fails when HOME is not set. This is an issue if running a script via EXEC that calls facter. Steps to reproduce: 1) login to linux server 2) run the following commands # unset HOME # facter Error: couldn't find HOME environment -- expanding '~/.facter/facts.d' 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-1517) Install puppet in cPAnel servers
Title: Message Title Josh Cooper commented on an issue Re: Install puppet in cPAnel servers Nathan Flynn thanks for finding the issue, going to close this ticket. Add Comment Puppet / PUP-1517 Install puppet in cPAnel servers I am getting the following errors. While installing puppet client. -- Error: Package: puppet-2.7.23-1.el6.noarch (epel) Requires: ruby(abi) = 1.8 Error: Package: puppet-2.7.23-1.el6.noarch (epel) Requires: /usr/bin/ruby Error: Package: facter-1.6.18-3.el6.x86_64 (epel) Requires: ruby(abi) = 1.8 Error: Package: p... 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-2365) Puppet module tool on windows cannot connect to the forge
Title: Message Title Josh Cooper commented on an issue Re: Puppet module tool on windows cannot connect to the forge The new certificate has been deployed, and is issued by GeoTrust Global CA, which is on Microsoft's list of trusted CAs. Nicholas Fagerlund We need to update our windows docs, as windows users may still run into the Unable to verify the SSL certificate, The certificate may not be signed by a valid CA issue due to the way Windows updates root certificates, referred to as Automatic Root Certificate Updates. From http://technet.microsoft.com/en-us/library/cc749331(WS.10).aspx Specifically, if the application is presented with a certificate issued by a certification authority in a PKI that is not directly trusted, the Update Root Certificates feature (if it is not turned off) will contact the Windows Update Web site to see if Microsoft has added the certificate of the root CA to its list of trusted root certificates. If the CA has been added to the Microsoft list of trusted authorities, its certificate will automatically be added to the set of trusted root certificates on the user's computer. In other words, if a Windows box does not have the GeoTrust Global CA cert installed, the module tool will not be able to connect to the forge. This can happen several different ways. Windows host is newly provisioned, e.g. vagrant, Windows has never run Windows Update, the Update Root Certificates feature is turned off, or user has never browsed a website that relies on the GeoTrust Global CA cert. If this issue occurs, the workaround is to: Run windows update Browse https://forge.puppetlabs.com with your browser of choice You should see an event like the following in the Application Event log: Log Name: Application Source:Microsoft-Windows-CAPI2 Date: 6/2/2014 9:19:34 PM Event ID: 4097 Task Category: None Level: Information Keywords: Classic User: N/A Computer: r7pkll36gsngyfi Description: Successful auto update of third-party root certificate:: Subject: CN=GeoTrust Global CA, O=GeoTrust Inc., C=US Sha1 thumbprint: DE28F4A4FFE5B92FA3C503D1A349A7F9962A8212. Alternatively, you can execute the following command: C:\ certutil -v -addstore Root geotrustglobalca.pem where file geotrustglobalca.pem contains the root certificate.
Jira (FACT-548) fact not showing up when run through puppet agent
Title: Message Title
Josh Cooper commented on an issue
Re: fact not showing up when run through puppet agent
Daniele Sluijters I don't know if this is the issue, but the fact is executing the pt-mysql-summary command outside of the setcode block. This will cause the command to be executed on every platform, not just the one you confined it to. If you move the command execution into the setcode block, does the issue go away?
Add Comment
Facter / FACT-548
fact not showing up when run through puppet agent
I have no clue if this is a Facter bug or a Puppet thing. I have a custom Fact which works when I run it through {{FACTERLIB=/path/to/fact facter}} and also shows up when distributed through Puppet and run with {{facter -p}} and even works when manually kicking {{puppet agent -t}}. However, when relying simply on the agent the fact doesn't work (and be...
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,
Jira (HI-46) Hiera should support alternate environments
Title: Message Title Richard Clark commented on an issue Re: Hiera should support alternate environments This is a feature ticket right ? I want this for supporting different backends, and having a separate hiera.yaml underneath the environmentpath would prevent me from having to have multiple masters (my current work around). It is a simplification of my setup, and is in line with the separate environment work being done. Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-1066) yum repos should be ensurable.
Title: Message Title Adrien Thebo commented on an issue Re: yum repos should be ensurable. If a .repo file is corrupted in the manner that you're demonstrating, it cannot be parsed in any situation. If the parser hits invalid data it cannot continue and it's impossible to determine if there are valid repos following the corrupted data, so unparsable files cannot be removed safely. With respect to files that no longer have any yumrepo resources defined, the files may still have content that users created. Comments in yumrepo files are unmanaged and while implementing the ensurable behavior I opted to take the less destructive path and leave those contents alone. When rewriting the inifile code I built in the capacity to remove files that no longer have managed sections in the given file (https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/inifile.rb#L118-L121) but chose to defer the decision in order to ship the ensurable functionality sooner rather than later. If you think that files without defined resources should be removed, please file a new issue for that. In the mean time, if you purge all unmanaged yumrepo sections, the sections themselves will be entirely removed so this ticket itself is complete. In addition if you believe you have found a regression with the `reposdir` section not being respected, please file a new bug documenting that regression with steps to reproduce. Add Comment Puppet / PUP-1066 yum repos should be ensurable. This should be done so that we can solve: #949 - yumrepo should support removal of repository #1023 - yumrepo option to purge unmanaged repos
Jira (PUP-1109) Convert puppet startup script to upstart
Title: Message Title adrian commented on an issue Re: Convert puppet startup script to upstart Upstart is deprecated: http://www.markshuttleworth.com/archives/1316 Add Comment Puppet / PUP-1109 Convert puppet startup script to upstart May be a won't-fix, but converting puppet init.d scripts to upstart has significant benefits on distributions that use upstart. The reason I'm interested in this is relying on the respawn stanza, which would allow us to work around PUP-202. 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 (HI-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title Trevor Vaughan commented on an issue Re: Really need the ability to lookup hashes and arrays from other parts of Hiera. Any love here? This would be really great to have in the main line. Add Comment Hiera / HI-183 Really need the ability to lookup hashes and arrays from other parts of Hiera. So, back in the old Redmine system, there was feature #23323 (http://projects.puppetlabs.com/issues/23323), which needed to be able to look up hashes and arrays from other parts of Hiera. I would like to reinstate that request here since the current solution only partially meets common data management consolidation needs. For instance, consider this... 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-2772) init.d script wrong pidfile
Title: Message Title
adrian commented on an issue
Re: init.d script wrong pidfile
Created pull request with the pidfile changed: https://github.com/puppetlabs/puppet/pull/2762
Add Comment
Puppet / PUP-2772
init.d script wrong pidfile
The init.d script installed with the Ubuntu package (https://github.com/puppetlabs/puppet/blob/master/ext/debian/puppetmaster.init) set the pidfile to /var/run/puppet/${NAME}.pid but the pidfile is actually in /var/lib/puppet/run/${NAME}.pid Seems that the instruction: start-stop-daemon --start --quiet --pidfile /var/lib/puppet/run/${NAME}.pid \ ...
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-2772) init.d script wrong pidfile
Title: Message Title
adrian created an issue
Puppet / PUP-2772
init.d script wrong pidfile
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Release Engineering
Components:
RE
Created:
12/Jun/14 9:36 AM
Environment:
puppetmaster-3.6.2-1puppetlabs1
Priority:
Normal
Reporter:
adrian
The init.d script installed with the Ubuntu package (https://github.com/puppetlabs/puppet/blob/master/ext/debian/puppetmaster.init) set the pidfile to /var/run/puppet/$ {NAME}.pid but the pidfile is actually in /var/lib/puppet/run/${NAME}
.pid
Seems that the instruction: start-stop-daemon --start --quiet --pidfile /var/lib/puppet/run/$ {NAME}
.pid \ --startas $DAEMON – $NAME $DAEMON_OPTS --masterport=$PORT doesn't work correctly.
Jira (PUP-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Puppet 3.6.1 File recurse improperly handles spaces in filenames
Charlie Sharpsteen I think the behavior around ? (and perhaps the square brackets) is long-standing, see PUP-2687, and not a regression. So that can be tackled separately from this issue about the regression wrt spaces (which likely accounts for the other characters you've documented).
For the current issue, since this was introduced by calling source.rb's uri method which consists of
@uri ||= URI.parse(URI.escape(metadata.source))
would this be addressed simply by a new method which skips the escape logic e.g.
@uri ||= URI.parse(metadata.source)
?? I haven't tried this, just tossing an idea out there. Puppet does some odd things wrt escaping, so it might not be that simple, but might be worth a look.
Add Comment
Puppet / PUP-2700
Puppet 3.6.1 File recurse improperly handles spaces in filenames
This one's new on me. We're using file{ : recurse = remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call. Here's a convenient, if ugly, example: In the Fileserv...
Jira (PUP-1109) Convert puppet startup script to upstart
Title: Message Title Timur Alperovich commented on an issue Re: Convert puppet startup script to upstart That's fair – we're still using Ubuntu 12.04 and I think Ubuntu 14.04 is still using upstart. Anyway, closing this issue as a won't fix make sense. Unfortunately, I don't think I can do that :\ Add Comment Puppet / PUP-1109 Convert puppet startup script to upstart May be a won't-fix, but converting puppet init.d scripts to upstart has significant benefits on distributions that use upstart. The reason I'm interested in this is relying on the respawn stanza, which would allow us to work around PUP-202. 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-2746) new parameter allow_virtual
Title: Message Title
Josh Cooper commented on an issue
Re: new parameter allow_virtual
Curtis Ruck Just so you know, we really are trying to do the right thing here. I know it probably doesn't seem that way, but we want to make sure users are aware of breaking changes that will be occurring Puppet 4, and remediate those issues before Puppet 4 lands.
It would of been much nicer if you had added the default allow_virtual=false to maintain existing functionality, since according to semantic versioning you can add features but not break existing environments.
That's fair. We wanted it to default to true in 4.0. If we explicitly set the default to false in 3.x, then we wouldn't be able to issue a deprecation warning.
Thank you for successfully introducing non-backwards compatible changes into your stable releases.
Watch the tone please, that wasn't our intent. We didn't realize that setting allow_virtual as a resource default would require the master and all agents to be upgraded to 3.6.1.
In 3.6.2, you can set --disable-warnings=deprecations. If you want to run a single run with deprecations enabled, you can do:
puppet agent -t --disable_warnings=''
Add Comment
Puppet / PUP-2746
new parameter allow_virtual
So, this whole allow_virtual new parameter has been extremely frustrating. We use puppet to manage package updates, i.e. package{'puppet': ensure=latest}
Jira (PUP-2738) Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2738 Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer Change By: Josh Cooper Assignee: JoshCooper EthanBrown 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-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Puppet 3.6.1 File recurse improperly handles spaces in filenames
Kylo Ginsberg I agree that the issues with ? ] [ are outside the scope of getting the specific regression in 3.6.x fixed. My main reason for noting them was to separate new bugs from old bugs
As for a fix, I noticed that after generating source = source_or_content.uri, the very next thing we do is build an Indirector request using source.to_s. So, a quick fix appears to be wrapping that string in a URI unescape:
--- a/lib/puppet/type/file/content.rb
+++ b/lib/puppet/type/file/content.rb
@@ -208,7 +208,7 @@ module Puppet
def get_from_source(source_or_content, block)
source = source_or_content.uri
- request = Puppet::Indirector::Request.new(:file_content, :find, source.to_s, nil, :environment = resource.catalog.environment)
+ request = Puppet::Indirector::Request.new(:file_content, :find, URI.unescape(source.to_s), nil, :environment = resource.catalog.environment)
request.do_request(:fileserver) do |req|
connection = Puppet::Network::HttpPool.http_instance(req.server, req.port)
This should cancel the extra escaping added by source_or_content.uri.
Add Comment
Puppet / PUP-2700
Puppet 3.6.1 File recurse improperly handles spaces in filenames
This one's new on me. We're using file{ : recurse = remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call. Here's a convenient, if ugly, example: In the Fileserv...
Jira (PUP-2756) Fix faulty acceptance test for future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2756 Fix faulty acceptance test for future parser Change By: Henrik Lindberg Fix Version/s: 4.0.0 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-839) FFI Puppet::Util::Windows::Security module
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-839 FFI Puppet::Util::Windows::Security module Change By: Ethan Brown Assignee: EthanBrown 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-2389) Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby
Title: Message Title Ethan Brown assigned an issue to Josh Cooper Puppet / PUP-2389 Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby Change By: Ethan Brown 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 (FACT-548) fact not showing up when run through puppet agent
Title: Message Title
Daniele Sluijters commented on an issue
Re: fact not showing up when run through puppet agent
Josh Cooper The confine doesn't seem to be the issue. We only have machines that match :kernel = :linux, I tried :kernel = 'Linux' too but no dice.
If the confine where the issue I would've expected facter -p, puppet agent -t and the FACTERLIB=. facter to have failed too, but they work just fine. It's just the agent as-a-daemon that seems to be having issues with it.
Add Comment
Facter / FACT-548
fact not showing up when run through puppet agent
I have no clue if this is a Facter bug or a Puppet thing. I have a custom Fact which works when I run it through {{FACTERLIB=/path/to/fact facter}} and also shows up when distributed through Puppet and run with {{facter -p}} and even works when manually kicking {{puppet agent -t}}. However, when relying simply on the agent the fact doesn't work (and be...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving
Jira (FACT-549) serialnumber fact for AIX
Title: Message Title Jay Wallace created an issue Facter / FACT-549 serialnumber fact for AIX Issue Type: New Feature Affects Versions: 1.7.5 Assignee: Eric Sorenson Components: PE Created: 12/Jun/14 10:46 AM Environment: AIX 7.1 Labels: customer Priority: Normal Reporter: Jay Wallace Currently facter does not return the serialnumber fact for AIX boxes by default. This can be obtained via: uname -u
Jira (PUP-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Puppet 3.6.1 File recurse improperly handles spaces in filenames
That would do the trick too, though I'm not crazy about a gratuitous URI.escape - URI.unescape pair of operations, both from the perspective of efficiency, and from the perspective of readability (i.e. someone reading the code would wonder why is there an unescape here?). That's why I suggested a new method that only does the URI-fication needed (apparently) by the PR that introduced this regression.
Add Comment
Puppet / PUP-2700
Puppet 3.6.1 File recurse improperly handles spaces in filenames
This one's new on me. We're using file{ : recurse = remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call. Here's a convenient, if ugly, example: In the Fileserv...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and
Jira (PUP-2773) Schedule type needs more granularity
Title: Message Title
Jay Wallace created an issue
Puppet / PUP-2773
Schedule type needs more granularity
Issue Type:
New Feature
Affects Versions:
3.4.3
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
12/Jun/14 10:58 AM
Labels:
customer
Priority:
Normal
Reporter:
Jay Wallace
The schedule type currently is not specific enough. For example a user is only able to schedule a resource to be applied the first Tuesday of the month.
schedule { 'maint':
range = 2 - 4,
weekday = 'Tuesday',
period = 'Monthly',
repeat = 1,
}
If a user wants to schedule the resource to be applied on the second Tuesday of the month, the type falls short in this regard.
You are only able to specify the weekday and how many times it runs within it's period. Unfortunately this falls short of some users expectations.
Jira (FACT-234) Add Facts showing the UUID of partitions
Title: Message Title Adrien Thebo updated an issue Facter / FACT-234 Add Facts showing the UUID of partitions Change By: Adrien Thebo Addfacts'blockdevice_dev_uuid'thatshowthepartitionsUUID.Itignoresswapandiso9660(CD/DVDdevices). PR:https://github.com/puppetlabs/facter/pull/560 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-234) Add Facts showing the UUID of partitions
Title: Message Title Adrien Thebo commented on an issue Re: Add Facts showing the UUID of partitions Merged into facter-2 in d62f3bc; this should be released in 2.1.0. Add Comment Facter / FACT-234 Add Facts showing the UUID of partitions Add facts 'blockdevice_dev_uuid' that show the partitions UUID. It ignores swap and iso9660 (CD/DVD devices). 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 (HI-46) Hiera should support alternate environments
Title: Message Title Ben Ford commented on an issue Re: Hiera should support alternate environments Is there anything about environments that couldn't be easily scripted out to multiple Puppet masters? The fact that I could script a workaround doesn't mean that I should have to. Assuming that hiera.yaml is interpreted for each environment is a very common mistake. If we choose not to support the commonly expected functionality, we should have a damn good reason why not. Having a workaround for it is not a good reason. Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. 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 (HI-7) Hiera stable acceptance tests use dynamically provisioned vcloud templates.
Title: Message Title Kurt Wall updated an issue Hiera / HI-7 Hiera stable acceptance tests use dynamically provisioned vcloud templates. Change By: Kurt Wall Assignee: JoshuaPartlow 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 (HI-7) Hiera stable acceptance tests use dynamically provisioned vcloud templates.
Title: Message Title Kurt Wall commented on an issue Re: Hiera stable acceptance tests use dynamically provisioned vcloud templates. Josh Cooper AFAICT, all Hiera acceptance jobs now use vcloud templates. Add Comment Hiera / HI-7 Hiera stable acceptance tests use dynamically provisioned vcloud templates. Scott Schneider has already merged in changes to master which allow the Hiera Acceptance (master) Jenkins job to run against current puppet acceptance with dynamically provisioned vcloud templates. These templates do not exhibit the sporadic networking issues which have plagued the older templates. We need to get these changes merged down into stable an... 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 (HI-8) Hiera stable acceptance testing for Windows using VCloud
Title: Message Title Kurt Wall commented on an issue Re: Hiera stable acceptance testing for Windows using VCloud This work is complete. Add Comment Hiera / HI-8 Hiera stable acceptance testing for Windows using VCloud 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 (HI-9) Hiera stable acceptance testing for Solaris with Vcloud
Title: Message Title Kurt Wall commented on an issue Re: Hiera stable acceptance testing for Solaris with Vcloud This work has been completed. Add Comment Hiera / HI-9 Hiera stable acceptance testing for Solaris with Vcloud 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 (HI-8) Hiera stable acceptance testing for Windows using VCloud
Title: Message Title Kurt Wall updated an issue Hiera / HI-8 Hiera stable acceptance testing for Windows using VCloud Change By: Kurt Wall Assignee: KurtWall MichelleJohansen 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 (HI-9) Hiera stable acceptance testing for Solaris with Vcloud
Title: Message Title Kurt Wall updated an issue Hiera / HI-9 Hiera stable acceptance testing for Solaris with Vcloud Change By: Kurt Wall Assignee: KurtWall MichelleJohansen 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-408) Puppet package acceptance is sufficient for a smoke test
Title: Message Title Kurt Wall commented on an issue Re: Puppet package acceptance is sufficient for a smoke test Josh Cooper and Moses Mendoza Do we get nightly MSI builds? The on-demand build won't be sufficient here. We can live without per-commit MSIs, but nightly MSIs would be nice. Now that HI-7, HI-8, and HI-9 are complete, we are testing Windows on vcloud-based VMs. We need the actual package. Add Comment Puppet / PUP-408 Puppet package acceptance is sufficient for a smoke test The current version of the package acceptance test jobs for Puppet does not sufficiently cover what we have been checking for smoke tests. Looking at the list of tests from PP-364, the points we are missing are: * The ability to test the msi packages on vcloud windows templates * A Beaker that uses the service scripts for starting and stopping pupp... 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
Jira (PDB-706) PDB Query Inconsistencies Phase 2
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-706 PDB Query Inconsistencies Phase 2 Issue Type: Epic Assignee: Unassigned Created: 12/Jun/14 12:43 PM Priority: Normal Reporter: Kenneth Barber 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-41) Establish better patterns for handling API versioning
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-41 Establish better patterns for handling API versioning 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-2174) Returned data from PMT actions should be better specified
Title: Message Title Pieter van de Bruggen updated an issue Puppet / PUP-2174 Returned data from PMT actions should be better specified Change By: Pieter van de Bruggen Component/s: PMT 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-2335) PMT should allow you to check all modules for updates.
Title: Message Title Pieter van de Bruggen updated an issue Puppet / PUP-2335 PMT should allow you to check all modules for updates. Change By: Pieter van de Bruggen Component/s: PMT 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-2040) Allow excluding content from Puppet module tool built packages
Title: Message Title Pieter van de Bruggen updated an issue Puppet / PUP-2040 Allow excluding content from Puppet module tool built packages Change By: Pieter van de Bruggen Component/s: PMT 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-1130) PMT cannot install tarballs for modules that don't exist on the Forge
Title: Message Title Pieter van de Bruggen updated an issue Puppet / PUP-1130 PMT cannot install tarballs for modules that don't exist on the Forge Change By: Pieter van de Bruggen Component/s: PMT 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-1130) PMT cannot install tarballs for modules that don't exist on the Forge
Title: Message Title Pieter van de Bruggen commented on an issue Re: PMT cannot install tarballs for modules that don't exist on the Forge This should be fixed in Puppet 3.6 and PE 3.2. Add Comment Puppet / PUP-1130 PMT cannot install tarballs for modules that don't exist on the Forge At present, unless you specify the `--ignore-dependencies` flag, the module tool behaves as follows when told to install a tarball: * Verify that the name ends in `.tar.gz` * Copy the tarball into the staging area * Decompose the filename into author, module short name, and version components * Ask the Forge for the dependency information for th... 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-2701) Add acceptance tests for PMT build metadata.json support
Title: Message Title Pieter van de Bruggen updated an issue Puppet / PUP-2701 Add acceptance tests for PMT build metadata.json support Change By: Pieter van de Bruggen Component/s: PMT 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-2720) Add acceptance test for PMT changes command
Title: Message Title Pieter van de Bruggen updated an issue Puppet / PUP-2720 Add acceptance test for PMT changes command Change By: Pieter van de Bruggen Component/s: PMT 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-1186) puppet module tool on windows will (sometimes) create a PaxHeader directory
Title: Message Title Pieter van de Bruggen updated an issue Puppet / PUP-1186 puppet module tool on windows will (sometimes) create a PaxHeader directory Change By: Pieter van de Bruggen Component/s: PMT 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-164) select-nodes subquery operator
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-164 select-nodes subquery operator 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-514) Add optional type to parameters
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-514 Add optional type to parameters 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 (PDB-164) select-nodes subquery operator
Title: Message Title Kenneth Barber commented on an issue Re: select-nodes subquery operator Fixed in PDB-657 and PDB-658 . We need docs to include the new subquery operators though. Add Comment PuppetDB / PDB-164 select-nodes subquery operator I would like to be able to do node subqueries in the resource facts endpoints (and in the future in the reports endpoint of course). 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-2756) Fix faulty acceptance test for future parser
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2756 Fix faulty acceptance test for future parser Change By: Joshua Partlow Assignee: JoshuaPartlow 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 (HI-8) Hiera stable acceptance testing for Windows using VCloud
Title: Message Title Josh Cooper commented on an issue Re: Hiera stable acceptance testing for Windows using VCloud Kurt Wall do you know if the current hiera windows acceptance failures are code issues or CI issues? Add Comment Hiera / HI-8 Hiera stable acceptance testing for Windows using VCloud 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 (HI-8) Hiera stable acceptance testing for Windows using VCloud
Title: Message Title Josh Cooper commented on an issue Re: Hiera stable acceptance testing for Windows using VCloud Looks like acceptance tests succeed, but jenkins job fails to find build artifact: https://jenkins.puppetlabs.com/job/Hiera-Acceptance-Windows-stable/facter=master,puppet=stable,slave=acc-coord/4/console systest completed successfully, thanks. Recording test results No test report files were found. Configuration error? Build step 'Publish JUnit test result report' changed build result to FAILURE [BFA] Scanning build for known causes... Add Comment Hiera / HI-8 Hiera stable acceptance testing for Windows using VCloud This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2631) Running the puppet agent against a nonexistent environment produces an overly verbose error message.
Title: Message Title Kylo Ginsberg commented on an issue Re: Running the puppet agent against a nonexistent environment produces an overly verbose error message. Still a live issue? I know there was some fixup around warning messages. If so, can you mark Ready for Engineering and add a story points estimate? Add Comment Puppet / PUP-2631 Running the puppet agent against a nonexistent environment produces an overly verbose error message. When the puppet agent is run against a Puppet master using a nonexistent environment, the agent fails and prints an error message with the associated URL from the REST terminus. When the URL contains POST parameters, the resulting error is extremely verbose and produces about 50 or more lines of output. This is harmful from a user perspective because it p... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-2631) Running the puppet agent against a nonexistent environment produces an overly verbose error message.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2631 Running the puppet agent against a nonexistent environment produces an overly verbose error message. Change By: Kylo Ginsberg Component/s: Modules Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1044) FileBucket should not keep files in memory
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1044 FileBucket should not keep files in memory Change By: Kylo Ginsberg Component/s: NetworkingServices 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 Kylo Ginsberg updated an issue Puppet / PUP-2429 Provide a way to expose trusted facts to PuppetDB (and other terminus consumers) Change By: Kylo Ginsberg Component/s: NetworkingServices 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-2756) Fix faulty acceptance test for future parser
Title: Message Title Henrik Lindberg commented on an issue Re: Fix faulty acceptance test for future parser Merged to master: 30a1320 Add Comment Puppet / PUP-2756 Fix faulty acceptance test for future parser This test: https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/apply/conditionals/should_evaluate_undef.rb Is faulty for future parser since undef is no longer equal to an empty string. This blocks getting a clean acceptance test run. 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-2714) Future parser returns nil when parsing a source that contains no statements
Title: Message Title Andy Parker updated an issue Puppet / PUP-2714 Future parser returns nil when parsing a source that contains no statements Change By: Andy Parker Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2682) Trailing commas should be allowed in node definitions
Title: Message Title Andy Parker updated an issue Puppet / PUP-2682 Trailing commas should be allowed in node definitions Change By: Andy Parker Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2747) support multiple profilers
Title: Message Title Andy Parker updated an issue Puppet / PUP-2747 support multiple profilers Change By: Andy Parker 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 (HI-8) Hiera stable acceptance testing for Windows using VCloud
Title: Message Title Kurt Wall commented on an issue Re: Hiera stable acceptance testing for Windows using VCloud What is the correct directory for junit output? Add Comment Hiera / HI-8 Hiera stable acceptance testing for Windows using VCloud 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-2747) support multiple profilers
Title: Message Title Andy Parker updated an issue Puppet / PUP-2747 support multiple profilers Change By: Andy Parker 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-2747) support multiple profilers
Title: Message Title Andy Parker updated an issue Puppet / PUP-2747 support multiple profilers Change By: Andy Parker Issue Type: Task NewFeature Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2747) support multiple profilers
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2747 support multiple profilers 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 (HI-8) Hiera stable acceptance testing for Windows using VCloud
Title: Message Title Kurt Wall commented on an issue Re: Hiera stable acceptance testing for Windows using VCloud Josh Cooper What is the correct path for junit output? beaker/junit/*.xml isn't it. Add Comment Hiera / HI-8 Hiera stable acceptance testing for Windows using VCloud 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-2747) support multiple profilers
Title: Message Title Andy Parker updated an issue Puppet / PUP-2747 support multiple profilers Change By: Andy Parker Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2747) support multiple profilers
Title: Message Title Andy Parker updated an issue Puppet / PUP-2747 support multiple profilers Change By: Andy Parker Sprint: Week2014-6-11to2014-6-18 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 (HI-8) Hiera stable acceptance testing for Windows using VCloud
Title: Message Title Kylo Ginsberg commented on an issue Re: Hiera stable acceptance testing for Windows using VCloud Kurt Wall beaker creates a junit directory where it is run. For puppet and facter this means it will be in acceptance/junit, but hiera's acceptance tests are in a differently named directory, acceptance_tests, so for these it will be acceptance_tests/junit. For extra credit, you might rename acceptance_tests to acceptance so that it's consistent with the other projects. I do love snowflakes. Add Comment Hiera / HI-8 Hiera stable acceptance testing for Windows using VCloud 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 (HI-8) Hiera stable acceptance testing for Windows using VCloud
Title: Message Title Justin Stoller commented on an issue Re: Hiera stable acceptance testing for Windows using VCloud For extra credit, you might rename acceptance_tests to acceptance so that it's consistent with the other projects. I do love snowflakes. +1 Add Comment Hiera / HI-8 Hiera stable acceptance testing for Windows using VCloud 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-2747) support multiple profilers
Title: Message Title Andy Parker commented on an issue Re: support multiple profilers Merged in after some small fixes. Merged into master in commit 20e928. Christopher Price, I'm sorry, my poor little heart just couldn't take a class named Manager Add Comment Puppet / PUP-2747 support multiple profilers The current implementation of the profiling system uses a single setter method to assign/remove the active profiler. This means that it's not safe to manipulate the active profiler in new code unless you know for sure that it will not be manipulated by any other parts of the code that will be executed during the run. It also means that you can only have... 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-2755) Move iterative functions to 4x function API
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-2755 Move iterative functions to 4x function API Change By: Henrik Lindberg Assignee: AndyParker 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-2755) Move iterative functions to 4x function API
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2755 Move iterative functions to 4x function API Change By: Henrik Lindberg Sprint: Week2014-6-11to2014-6-18 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-2774) class can `require` itself without raising an error
Title: Message Title David Gwilliam created an issue Puppet / PUP-2774 class can `require` itself without raising an error Issue Type: Bug Assignee: Unassigned Created: 12/Jun/14 4:59 PM Priority: Normal Reporter: David Gwilliam of course eventually dependency cycles are found, but it would be convenient if we were able to communicate this earlier in development Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-550) Specs are broken on windows do to unvendoring CFPropertyList
Title: Message Title Josh Cooper created an issue Facter / FACT-550 Specs are broken on windows do to unvendoring CFPropertyList Issue Type: Bug Affects Versions: 2.0.1 Assignee: Eric Sorenson Created: 12/Jun/14 5:14 PM Fix Versions: 2.1 Priority: Normal Reporter: Josh Cooper See QENG-785 for why it's broken. Add Comment
Jira (FACT-550) Specs are broken on windows do to unvendoring CFPropertyList
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Facter / FACT-550 Specs are broken on windows do to unvendoring CFPropertyList Change By: Josh Cooper Assignee: EricSorenson 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 (FACT-550) Specs are broken on windows do to unvendoring CFPropertyList
Title: Message Title Josh Cooper updated an issue Facter / FACT-550 Specs are broken on windows do to unvendoring CFPropertyList Change By: Josh Cooper Sprint: Week2014-6-11to2014-6-18 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-550) Specs are broken on windows due to unvendoring CFPropertyList
Title: Message Title Josh Cooper updated an issue Facter / FACT-550 Specs are broken on windows due to unvendoring CFPropertyList Change By: Josh Cooper Summary: Specsarebrokenonwindows do due tounvendoringCFPropertyList 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-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-2426 Puppet's v2 environment listing does not display config_version and environment_timeout as well. Change By: Henrik Lindberg 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-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-2426 Puppet's v2 environment listing does not display config_version and environment_timeout as well. Change By: Henrik Lindberg 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-2631) Running the puppet agent against a nonexistent environment produces an overly verbose error message.
Title: Message Title Adrien Thebo commented on an issue Re: Running the puppet agent against a nonexistent environment produces an overly verbose error message. Just repro'd, ticket updated. Add Comment Puppet / PUP-2631 Running the puppet agent against a nonexistent environment produces an overly verbose error message. When the puppet agent is run against a Puppet master using a nonexistent environment, the agent fails and prints an error message with the associated URL from the REST terminus. When the URL contains POST parameters, the resulting error is extremely verbose and produces about 50 or more lines of output. This is harmful from a user perspective because it p... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2631) Running the puppet agent against a nonexistent environment produces an overly verbose error message.
Title: Message Title
Adrien Thebo updated an issue
Puppet / PUP-2631
Running the puppet agent against a nonexistent environment produces an overly verbose error message.
Change By:
Adrien Thebo
WhenthepuppetagentisrunagainstaPuppetmasterusinganonexistentenvironment,theagentfailsandprintsanerrormessagewiththeassociatedURLfromtheRESTterminus.WhentheURLcontainsPOSTparameters,theresultingerrorisextremelyverboseandproducesabout50ormorelinesofoutput.Thisisharmfulfromauserperspectivebecauseitproducesalargeamountofoutputthatdoesn'tcontributetotheexplanationoftheerror.ThiswasintroducedaspartofPUP-2214. Stepstoreproduce:Setupamasterwiththispuppet.conf:{code}[master]environmentpath=$confdir/environments{code}Runanagentagainstagarbageenvironmentname,andstepwellback.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2631) Running the puppet agent against a nonexistent environment produces an overly verbose error message.
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2631 Running the puppet agent against a nonexistent environment produces an overly verbose error message. Change By: Adrien Thebo 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 (FACT-550) Specs are broken on windows due to unvendoring CFPropertyList
Title: Message Title Josh Cooper commented on an issue Re: Specs are broken on windows due to unvendoring CFPropertyList Merged into facter-2 in aaea681 to be released in 2.1 Add Comment Facter / FACT-550 Specs are broken on windows due to unvendoring CFPropertyList See QENG-785 for why it's broken. 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-2740) Puppet apply core dump on RedHat 6.5
Title: Message Title Daniel Dreier commented on an issue Re: Puppet apply core dump on RedHat 6.5 I can't reproduce this, most likely because I don't have your dta module. I started a RHEL 6.5 EC2 instance on a c3.large with ruby 1.8.7 and puppet 3.6.1: [root@ip-172-31-19-25 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.5 (Santiago) [root@ip-172-31-19-25 ~]# ruby --version ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] [root@ip-172-31-19-25 ~]# puppet --version 3.6.1 [root@ip-172-31-19-25 ~]# puppet apply --modulepath=/etc/puppet/modules -e include dta::puppetmaster Error: Could not find class dta::puppetmaster for ip-172-31-19-25.us-west-2.compute.internal on node ip-172-31-19-25.us-west-2.compute.internal Error: Could not find class dta::puppetmaster for ip-172-31-19-25.us-west-2.compute.internal on node ip-172-31-19-25.us-west-2.compute.internal [root@ip-172-31-19-25 ~]# Can you make that module available? I don't think anybody will be able to help investigate the issue without it, because there's no way to know what's actually trying to run that's causing a segfault. Add Comment Puppet / PUP-2740 Puppet apply core dump on RedHat 6.5 puppet apply --modulepath=/etc/puppet/modules -e include dta::puppetmaster /usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb:414: [BUG] Segmentation fault ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] Aborted (core dumped)
Jira (PUP-2774) class can `require` itself without raising an error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2774 class can `require` itself without raising an error Change By: Henrik Lindberg Issue Type: Bug Improvement 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-2774) class can `require` itself without raising an error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2774 class can `require` itself without raising an error Change By: Henrik Lindberg 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 (PUP-2774) class can `require` itself without raising an error
Title: Message Title Henrik Lindberg commented on an issue Re: class can `require` itself without raising an error The require function could check if it adds a direct circular requirement and immediately error out. Add Comment Puppet / PUP-2774 class can `require` itself without raising an error of course eventually dependency cycles are found, but it would be convenient if we were able to communicate this earlier in development 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.
