Jira (PUP-2479) Missing version tag 2.7.11 on github repo
Title: Message Title Dejan Golja created an issue Puppet / PUP-2479 Missing version tag 2.7.11 on github repo Issue Type: Bug Assignee: Eric Sorenson Components: Community Created: 05/May/14 11:23 PM Priority: Minor Reporter: Dejan Golja Is there a special reason why the tag 2.7.11 is missing in https://github.com/puppetlabs/puppet ? I am doing a puppet master upgrade from 2.7.11 - 3.X.X and using Envpuppet ((http://puppetlabs.com/blog/use-envpuppet-test-multiple-puppet-versions)) for testing and I am missing this tag Add Comment
Jira (PUP-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Felix Frank commented on an issue
Re: unless_uid on user is completely broken wrt ranges
-ish.
I'd still like to see you move this functionality to a a new type in a module, and perhaps even deprecate unless_uid from the core then.
Nevertheless, if you want the type to support ranges, this would still be a good place to sort out how those should be done first.
If I understand Henrik Lindberg correctly, we can interpret the Integer[x,y] syntax using existing functionality, yes? If so, that would indeed seem ideal to me.
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed
Jira (PUP-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Felix Frank commented on an issue
Re: unless_uid on user is completely broken wrt ranges
Meta: This is marked as critical, but it seems rather normal to me, in terms of severity. Objections?
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
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-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Daniele Sluijters commented on an issue
Re: unless_uid on user is completely broken wrt ranges
It's marked as critical because it doesn't work, the implementation is broken and the docs are broken, there are only workarounds. So I don't think that a severity of normal quite covers it.
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
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-2480) Problem when ignored files change timestamp of (recursively) copied directory
Title: Message Title redmine.exporter created an issue Puppet / PUP-2480 Problem when ignored files change timestamp of (recursively) copied directory Issue Type: Bug Assignee: Unassigned Created: 06/May/14 2:15 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Opening a bug as requested. Luke Kanies wrote: On Aug 12, 2009, at 5:28 AM, Sven Mueller wrote: Hi. I'm wondering wether the following is expected behaviour (and if so, wether it can be disabled): I have /etc/puppet/files/httpd/f.q.d.n/conf.d which contains a few conf.d files per host that need to be copied tothe server. The /etc/puppet/files (and all subdirectories of course) is managed with subversion and thus (now) contains a .svn subdirectory. Situation is that on the server, /etc/httpd/conf.d has been updatedand after that, the respective conf.d directory has been added/committedto subversion. Now the situation looks like this: On the server: ~ # ls -la /etc/httpd/conf.d total 96 drwxr-xr-x 2 root root 4096 Aug 5 14:06 . drwxr-xr-x 4 root root 4096 Jul 30 15:31 .. rw-r r - 1 root root 4090 Aug 5 11:58 risk.conf rw-r r
Jira (PUP-2481) Naginator: Allow parameters to be forced to absent
Title: Message Title Sven Mueller created an issue Puppet / PUP-2481 Naginator: Allow parameters to be forced to absent Issue Type: Improvement Affects Versions: 3.4.3 Assignee: Kylo Ginsberg Components: Types and Providers Created: 06/May/14 2:19 AM Priority: Normal Reporter: Sven Mueller While converting some of our active checks to passive ones (without changing their names), we realized that there is no way (at least no documented one) to remove the command parameter from nagios_service definitions from within puppet/naginator. It would be nice if this quote from the “cron” type would also be true for the nagios_* types: “All cron parameters support absent as a value; this will remove any existing values for that field.” Add Comment
Jira (PDB-652) Catalog duplication at 0.0%
Title: Message Title Daniele Sluijters created an issue PuppetDB / PDB-652 Catalog duplication at 0.0% Issue Type: Bug Affects Versions: 2.0.0 Assignee: Unassigned Created: 06/May/14 2:57 AM Priority: Normal Reporter: Daniele Sluijters After upgrading to 2.0.0 RC1 the metrics dashboard reports 0.0% catalog duplication. I'm pretty positive that's an error as we have a lot of similar nodes. Just about every node in datacenter A has a sister-node in datacenter B receiving identical configuration. Add Comment This
Jira (PDB-653) Certain metrics aren't getting updated
Title: Message Title Daniele Sluijters created an issue PuppetDB / PDB-653 Certain metrics aren't getting updated Issue Type: Bug Affects Versions: 2.0.0 Assignee: Unassigned Created: 06/May/14 2:59 AM Priority: Normal Reporter: Daniele Sluijters In RC1 the Collection Queries, DLO Compression, DLO size on disk and Discarded Messages are all stuk on a ?. I would expect at least Collection Queries to show some output as they should be happening with exported resources in our catalogs. I'd also expect API queries done by Puppetboard to influence that number. Add Comment
Jira (PDB-654) There is no 2.0.0-rc1 release in JIRA
Title: Message Title Daniele Sluijters created an issue PuppetDB / PDB-654 There is no 2.0.0-rc1 release in JIRA Issue Type: Improvement Affects Versions: 2.0.0 Assignee: Unassigned Created: 06/May/14 3:01 AM Priority: Normal Reporter: Daniele Sluijters When filing bugs against RC1 I'd like to do that against release version 2.0.0-rc1, however it's missing in the drop down. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-652) Catalog duplication at 0.0%
Title: Message Title Daniele Sluijters commented on an issue Re: Catalog duplication at 0.0% 20 minutes in and a lot of checkins later we're at about 2.1% catalog duplication but resource duplication is at 83.7%. Add Comment PuppetDB / PDB-652 Catalog duplication at 0.0% After upgrading to 2.0.0 RC1 the metrics dashboard reports 0.0% catalog duplication. I'm pretty positive that's an error as we have a lot of similar nodes. Just about every node in datacenter A has a sister-node in datacenter B receiving identical configuration. 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-652) Catalog duplication at 0.0%
Title: Message Title Daniele Sluijters commented on an issue Re: Catalog duplication at 0.0% Looks like the catalog duplication percentage is steadily rising now, nearing 60%. I'm still a bit confused as to why this started with 0%. I know it says 'of catalogs encountered' which could be interpreted as 'only from startup' but I'd prefer if an upgrade of PuppetDB wouldn't reset such key metrics. Add Comment PuppetDB / PDB-652 Catalog duplication at 0.0% After upgrading to 2.0.0 RC1 the metrics dashboard reports 0.0% catalog duplication. I'm pretty positive that's an error as we have a lot of similar nodes. Just about every node in datacenter A has a sister-node in datacenter B receiving identical configuration. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-653) Certain metrics aren't getting updated
Title: Message Title Daniele Sluijters commented on an issue Re: Certain metrics aren't getting updated Just like PDB-652 it took a while but Collection Queries is now showing numbers, the rest of the metrics is still at a ?. Add Comment PuppetDB / PDB-653 Certain metrics aren't getting updated In RC1 the Collection Queries, DLO Compression, DLO size on disk and Discarded Messages are all stuk on a ?. I would expect at least Collection Queries to show some output as they should be happening with exported resources in our catalogs. I'd also expect API queries done by Puppetboard to influence that number. 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-651) PR (962): Allow configurable url prefix - cprice404
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-651 PR (962): Allow configurable url prefix - cprice404 Change By: Kenneth Barber Sprint: 20140423to20140507 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-650) PR (961): Fix a race condition in the import/export round-trip clojure tests - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-650 PR (961): Fix a race condition in the import/export round-trip clojure tests - senior Change By: Kenneth Barber Sprint: 20140423to20140507 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-1415) Mount resource error silently skipped at times when running as daemon
Title: Message Title Marco De Vitis commented on an issue Re: Mount resource error silently skipped at times when running as daemon Yes thanks, I also tested it now on the same machine after upgrading to Puppet 3.5.1, and every automatic run of Puppet correctly returns the error and does not apply the yumrepo resource. Ticket can be closed for me. Add Comment Puppet / PUP-1415 Mount resource error silently skipped at times when running as daemon I have a host where puppet is running as daemon, refreshing every 30 minutes as per default, and a custom class is applied. The class contains: # A file resource to ensure a directory is created. # A package resource to ensure the nfs-utils RPM is installed. # A mount resource to mount a NFS share into the directory created in 1 and add the ... 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 (PDB-652) Catalog duplication at 0.0%
Title: Message Title Kenneth Barber commented on an issue Re: Catalog duplication at 0.0% Daniele Sluijters the behaviour has always been to calculate these numbers from startup. This is because we lack either the ability to store this data historically, or look back at historical catalog data to see the duplication over time (since we only store 1 catalog for each node). The calculation is adjusted at catalog replace time, where we keep counters of the number of catalogs that are identical, and ones that are not to provide you with a percentage. This data is only stored in memory though. So this isn't really a bug per se, perhaps an undesired behaviour but we haven't broken any old behaviour. The actions I see coming from this ticket are really: Find a better way to make sure this stuff is documented, metrics docs would help, and tool tips in the GUI Potentially we could change this behaviour, but that would require a bit of work to get right. Punting this for historical catalogs might be better, but we'd need to make a design decision. Add Comment PuppetDB / PDB-652 Catalog duplication at 0.0% After upgrading to 2.0.0 RC1 the metrics dashboard reports 0.0% catalog duplication. I'm pretty positive that's an error as we have a lot of similar nodes. Just about every node in datacenter A has a sister-node in datacenter B receiving identical configuration.
Jira (PDB-652) Catalog duplication at 0.0%
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-652 Catalog duplication at 0.0% Change By: Kenneth Barber 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 (PDB-652) Catalog duplication at 0.0%
Title: Message Title Daniele Sluijters commented on an issue Re: Catalog duplication at 0.0% Figures that this behaviour has always been there, it's the first time I noticed that :/. It would be nice to have historical data on this, especially to signal on when catalog duplication rates suddenly start dropping (which is what got me worried in the first place). Add Comment PuppetDB / PDB-652 Catalog duplication at 0.0% After upgrading to 2.0.0 RC1 the metrics dashboard reports 0.0% catalog duplication. I'm pretty positive that's an error as we have a lot of similar nodes. Just about every node in datacenter A has a sister-node in datacenter B receiving identical configuration. 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-652) Store historical data of catalog duplication
Title: Message Title Daniele Sluijters updated an issue PuppetDB / PDB-652 Store historical data of catalog duplication Change By: Daniele Sluijters Summary: Catalog Storehistoricaldataofcatalog duplication at0.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 (PDB-650) PR (961): Fix a race condition in the import/export round-trip clojure tests - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (961): Fix a race condition in the import/export round-trip clojure tests - senior Pull request Fix a race condition in the import/export round-trip clojure tests has been closed. Add Comment PuppetDB / PDB-650 PR (961): Fix a race condition in the import/export round-trip clojure tests - senior h2. Fix a race condition in the import/export round-trip clojure tests * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 961 Discussion|https://github.com/puppetlabs/puppetdb/pull/961] * [Pull Request 961 File Diff|https://github.com/puppetlabs/puppetdb/pull/961/files] h2. Pull... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-650) PR (961): Fix a race condition in the import/export round-trip clojure tests - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-650 PR (961): Fix a race condition in the import/export round-trip clojure tests - senior Change By: Kenneth Barber Story Points: 1 Fix Version/s: 2.0.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-2482) Add support for Debian multiarch package installation
Title: Message Title
Per Cederqvist created an issue
Puppet / PUP-2482
Add support for Debian multiarch package installation
Issue Type:
New Feature
Affects Versions:
3.5.1
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
06/May/14 5:26 AM
Priority:
Normal
Reporter:
Per Cederqvist
With Debian 7 (Debian wheezy), Debian introduced multiarch. If you are running on a 64-bit system, you can install 32-bit libraries as well. Using Puppet, you could install the 32-bit version of zlib1g with Puppet code like this:
if $::lsbdistcodename == 'wheezy' {
exec { '/usr/bin/dpkg --add-architecture i386':
unless = '/bin/grep -q i386 /var/lib/dpkg/arch',
}
package { 'zlib1g:i386':
ensure = installed,
}
}
This works, but it would be nice to have native support for multiarch in Puppet. (The code has at least two problems: it does not ensure that the architecture is added before it attempts to install the package, and you must run apt-get update between adding the arch and installing the package.)
I don't know exactly what I want, but maybe something like this:
Jira (PUP-2328) Go/no-go meeting
Title: Message Title Rob Reynolds commented on an issue Re: Go/no-go meeting PUP-1976 failed review. The decision was to set it as a known bug and fix it in the next RC. Add Comment Puppet / PUP-2328 Go/no-go meeting Go/no-go meeting 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-2455) Puppet running as Solaris SMF service needs to run child processes in separate contract
Title: Message Title Dave Taylor commented on an issue Re: Puppet running as Solaris SMF service needs to run child processes in separate contract I think it might need to be more generic than that, as init-based services aren't the only long-running processes that Puppet can run. For example, on later S10 releases running package management commands (pkginfo -l, pkgadd) will start a server process called pkgserv which hangs around for 5 minutes in case any other package management occurs. That process would sit in the same contract as the Puppet agent, so for 5 minutes after an agent run this same issue could occur. [N.b. I logged the original Redmine issue] Add Comment Puppet / PUP-2455 Puppet running as Solaris SMF service needs to run child processes in separate contract If Puppet is running on a Solaris server as an SMF service, and starts a long-running process - e.g. it starts a daemon via an init script - that process is within the same contract as the Puppet agent process. If the Puppet agent is stopped/restarted, SMF waits for the **contract** to finish, not just the agent process. As the daemon doesn't terminate,... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1157) puppet should support data in modules
Title: Message Title Alexander Pnek commented on an issue Re: puppet should support data in modules Has there been any more recent work on this subject, or are there any plans for Puppet 4 in this regard? Add Comment Puppet / PUP-1157 puppet should support data in modules At present there is a way to store data in modules using the puppet backend for hiera but it is optional and kind of broken. The site hierarchy impacts how the puppet backend behaves which makes it impossible for module authors to supply data in their modules they can rely on I propose a new hiera backend that loads a hierarchy of data from the 'data'... 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-652) Store historical data of catalog duplication
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-652 Store historical data of catalog duplication Change By: Kenneth Barber Affects Version/s: 2.0.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 (PDB-655) Update Dujour for PuppetDB 2.0.0
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-655 Update Dujour for PuppetDB 2.0.0 Issue Type: Sub-task Assignee: Unassigned Created: 06/May/14 7:01 AM Fix Versions: 2.0.0 Priority: Normal Reporter: Kenneth Barber Update Dujour so the PuppetDB dashboard recommends the latest revision. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-632) Ensure tests are passing
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-632 Ensure tests are passing Change By: Kenneth Barber Assignee: KennethBarber 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-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Henrik Lindberg commented on an issue
Re: unless_uid on user is completely broken wrt ranges
Felix Frank yes, the functionality is in place, but users must add the 'rgen' gem since the implementation i in the future part. Does not require using the future parser for everything else though. If this is in a module, it should be fine to require users to also have rgen installed since it is opt in and does not disturb anything else. Usage inside the function is also very simple:
the_type = Puppet::Pops::Types::TypeParser.new.parse(type_in_string_form)
The result is an Puppet::Pops::Types::PIntegerType which has methods to:
get the range as a [from, to] array
support iteration (unless one of the values is Infinity)
get the size (smallest possible size is 1, an empty range can not be expressed
Infinity is a special value in Ruby and it can be used in arithmetic.
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user =
Jira (PDB-631) Update documentation indexes for new major release
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-631 Update documentation indexes for new major release Change By: Kenneth Barber Assignee: KennethBarber 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-653) Certain metrics aren't getting updated
Title: Message Title Kenneth Barber commented on an issue Re: Certain metrics aren't getting updated So: DLO compression is transient, it only gets calculated after a reject and after compression The DLO size on disk, should not be transient, however ... it seems to me looking at dlo.clj, that this stuff only gets calculated on a failure. So while the data is correct and isn't just in ram it doesn't get populated until the first failure is seen after startup. I think point #2 is a bug, at least but we should dig into #1 as well as I might have missed something. This has been the behaviour for a while as well, but I'm leaving this ticket as it stands. I think its a valid bug, but not a release blocker. Add Comment PuppetDB / PDB-653 Certain metrics aren't getting updated In RC1 the Collection Queries, DLO Compression, DLO size on disk and Discarded Messages are all stuk on a ?. I would expect at least Collection Queries to show some output as they should be happening with exported resources in our catalogs. I'd also expect API queries done by Puppetboard to influence that number. This
Jira (PUP-2483) Deleting a certificate does not work with the API
Title: Message Title
garrett honeycutt created an issue
Puppet / PUP-2483
Deleting a certificate does not work with the API
Issue Type:
Bug
Affects Versions:
3.5.1
Assignee:
Unassigned
Created:
06/May/14 7:54 AM
Labels:
API
Priority:
Normal
Reporter:
garrett honeycutt
Removing a certificate no longer works through the API.
[root@puppet1 ~]# puppet cert list dc1 + dc1 (SHA256) 06:98:A3:40:F3:D4:7B:57:81:10:D3:DB:2A:C0:55:06:C1:98:8C:34:63:F2:ED:32:75:AA:DA:BE:78:6B:75:7D
auth.conf: https://gist.github.com/ghoneycutt/1ee2bf2ed5c82c47d807#file-auth-conf-L116-L119
curl command issued from CA: pre PUPPETCA=puppet curl -k -X DELETE -H Accept :pson https://$ {PUPPETCA}
:8140/production/certificate_status/dc1 /pre
Error: preServer Error: undefined method `each' for nil:NilClass/pre
I get the same error running under passenger or with webrick (puppet master --nodaemonize -v)
Jira (PUP-2484) `puppet module build` should provide deprecated functionality with warning until puppet v4
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2484 `puppet module build` should provide deprecated functionality with warning until puppet v4 Issue Type: Bug Affects Versions: 3.6.0 RC Assignee: Pieter van de Bruggen Components: Modules Created: 06/May/14 7:54 AM Fix Versions: 3.6.0 RC Priority: Normal Reporter: Rob Reynolds From Hunter Haugen (paraphrased): [The changes with PMT Build have a] backwards-incompatible nature [that] will currently break the packaging of all of our modules. Example:: We only declare dependencies in the Modulefile but not metadata.json. We also don't synchronize the versions in Modulefile and metadata.json because pmt prefers the Modulefile version over metadata.json invisibly. Suggestion: The pmt should merge Modulefile and metadata.json entries, preferring the entries in Modulefile for conflicts. It should warn that support for Modulefile is deprecated and it will only use metadata.json in the future. It would also be helpful if it warned about every entry
Jira (PUP-2483) Deleting a certificate does not work with the API
Title: Message Title
garrett honeycutt updated an issue
Puppet / PUP-2483
Deleting a certificate does not work with the API
Change By:
garrett honeycutt
RemovingacertificatenolongerworksthroughtheAPI. {code} [root@puppet1~]#puppetcertlistdc1+dc1(SHA256)06:98:A3:40:F3:D4:7B:57:81:10:D3:DB:2A:C0:55:06:C1:98:8C:34:63:F2:ED:32:75:AA:DA:BE:78:6B:75:7D {code} auth.conf:https://gist.github.com/ghoneycutt/1ee2bf2ed5c82c47d807#file-auth-conf-L116-L119curlcommandissuedfromCA:{code}PUPPETCA=puppetcurl-k-XDELETE-HAccept:psonhttps://${PUPPETCA}:8140/production/certificate_status/dc1{code}Error:{code}ServerError:undefinedmethod`each'fornil:NilClass{code}Igetthesameerrorrunningunderpassengerorwithwebrick(puppetmaster--nodaemonize-v)
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-2483) Deleting a certificate does not work with the API
Title: Message Title
garrett honeycutt updated an issue
Puppet / PUP-2483
Deleting a certificate does not work with the API
Change By:
garrett honeycutt
RemovingacertificatenolongerworksthroughtheAPI.[root@puppet1~]#puppetcertlistdc1+dc1(SHA256)06:98:A3:40:F3:D4:7B:57:81:10:D3:DB:2A:C0:55:06:C1:98:8C:34:63:F2:ED:32:75:AA:DA:BE:78:6B:75:7Dauth.conf:https://gist.github.com/ghoneycutt/1ee2bf2ed5c82c47d807#file-auth-conf-L116-L119curlcommandissuedfromCA: pre {code} PUPPETCA=puppetcurl-k-XDELETE-HAccept:psonhttps://${PUPPETCA}:8140/production/certificate_status/dc1 /pre {code} Error: pre {code} ServerError:undefinedmethod`each'fornil:NilClass /pre {code} Igetthesameerrorrunningunderpassengerorwithwebrick(puppetmaster--nodaemonize-v)
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-2484) `puppet module build` should provide deprecated functionality with warning until Puppet v4
Title: Message Title
Rob Reynolds updated an issue
Puppet / PUP-2484
`puppet module build` should provide deprecated functionality with warning until Puppet v4
Change By:
Rob Reynolds
WiththerecentchangesinthePMTtool,ifyouhavebothaModulefileandmetadata.jsonfile,theModulefilewillbecompletelyignored,breakingcurrentfunctionality.Theultimategoalistogettothisbehaviorofusingthemetadata.jsonfileonlybutneedstobedeprecatedinamannerthatstillprovidesthecurrentfunctionalitywithawarningandthenremovedinPuppetv4. Thatdeprecatedfunctionalityisoutlinedbelow. From[~hunter](paraphrased fromPUP-1976 ):{quote}[ThechangeswithPMTBuildhavea]backwards-incompatiblenature[that]willcurrentlybreakthepackagingofallofourmodules.Example::WeonlydeclaredependenciesintheModulefilebutnotmetadata.json.Wealsodon'tsynchronizetheversionsinModulefileandmetadata.jsonbecausepmtpreferstheModulefileversionovermetadata.jsoninvisibly.Suggestion:ThepmtshouldmergeModulefileandmetadata.jsonentries,preferringtheentriesinModulefileforconflicts.ItshouldwarnthatsupportforModulefileisdeprecatedanditwillonlyusemetadata.jsoninthefuture.ItwouldalsobehelpfulifitwarnedabouteveryentrythatexistsinModulefilebutisdifferentornon-existentinthemetadata.json{quote}
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
Jira (PUP-2484) `puppet module build` should provide deprecated functionality with warning until Puppet v4
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2484 `puppet module build` should provide deprecated functionality with warning until Puppet v4 Change By: Rob Reynolds Summary: `puppetmodulebuild`shouldprovidedeprecatedfunctionalitywithwarninguntil puppet Puppet v4 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-2484) `puppet module build` should provide deprecated functionality with warning until puppet v4
Title: Message Title
Rob Reynolds updated an issue
Puppet / PUP-2484
`puppet module build` should provide deprecated functionality with warning until puppet v4
Change By:
Rob Reynolds
WiththerecentchangesinthePMTtool,ifyouhavebothaModulefileandmetadata.jsonfile,theModulefilewillbecompletelyignored,breakingcurrentfunctionality.Theultimategoalistogettothisbehaviorofusingthemetadata.jsonfileonlybutneedstobedeprecatedinamannerthatstillprovidesthecurrentfunctionalitywithawarningandthenremovedinPuppetv4. From[~hunter](paraphrased):{quote}[ThechangeswithPMTBuildhavea]backwards-incompatiblenature[that]willcurrentlybreakthepackagingofallofourmodules.Example::WeonlydeclaredependenciesintheModulefilebutnotmetadata.json.Wealsodon'tsynchronizetheversionsinModulefileandmetadata.jsonbecausepmtpreferstheModulefileversionovermetadata.jsoninvisibly.Suggestion:ThepmtshouldmergeModulefileandmetadata.jsonentries,preferringtheentriesinModulefileforconflicts.ItshouldwarnthatsupportforModulefileisdeprecatedanditwillonlyusemetadata.jsoninthefuture.ItwouldalsobehelpfulifitwarnedabouteveryentrythatexistsinModulefilebutisdifferentornon-existentinthemetadata.json{quote}
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-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Rob Reynolds commented on an issue Re: `puppet module build` should use `metadata.json` as input format Created PUP-2484 to address the regression here prior to final release. Moving this to resolved. Add Comment Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format `puppet module build` This action is most impacted by this change though we will maintain compatibility with users still using Modulefile as their input format. Here's how that will work when a user initiates build. - If the user provides a Modulefile at the root of their module, PMT will use it exclusively to build the release and issue a deprecati... 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-2324) Prepare long form release notes and short form release story
Title: Message Title Rob Reynolds commented on an issue Re: Prepare long form release notes and short form release story FYI PUP-1976 has created a regression we may want to document. We plan to fix it in the next RC as PUP-2484. Nicholas Fagerlund Add Comment Puppet / PUP-2324 Prepare long form release notes and short form release story Prepare long form release notes and short form release story 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-2485) STDOUT/STDERR Logging for External Auto Approver
Title: Message Title Matt Wise created an issue Puppet / PUP-2485 STDOUT/STDERR Logging for External Auto Approver Issue Type: Bug Assignee: Unassigned Created: 06/May/14 8:10 AM Priority: Normal Reporter: Matt Wise If you use the new external auto signer code (see ours here: https://github.com/Nextdoor/puppet_rightscale/blob/master/lib/etc/autosign.rb), its nearly impossible to troubleshoot failures of the code because Puppet doesn't capture the STDOUT/STDERR from the command in the event of a failure. I know that we can enable extreme debugging in Puppet and get some of this, but it should be automatic in the event that the auto signer fails. Frankly, it probably should just always log the stdout/stderr messages. In our case, we've resorted to stracing all Unicorn processes when we're debugging the code so that we can get some output. The scenario that bit us in the ass was that the /tmp/autosign.log file was owned by root:root, so our own internal logging code in that module couldn't write to it ... the error was plainly visible in an strace, but that was it. Add Comment
Jira (PUP-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Henrik Lindberg commented on an issue
Re: unless_uid on user is completely broken wrt ranges
See this blog post: http://puppet-on-the-edge.blogspot.se/2014/05/puppet-internals-integer-type-ruby-api.html for more details about using the Integer type from Ruby.
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
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-656) puppetdb throws exception after yum update
Title: Message Title Aaron Zauner created an issue PuppetDB / PDB-656 puppetdb throws exception after yum update Issue Type: Bug Assignee: Unassigned Created: 06/May/14 8:27 AM Environment: CentOS 6.5 Labels: puppetdb Priority: Normal Reporter: Aaron Zauner After doing a simple `yum update` on the puppet server to fix the EPEL issue puppetdb was as well upgraded. PuppetDB won't start and throws an exception because of a missing log4j.properties file (which should be depreciated, as far as I can tell from the git sources). Is this a known issue? I could not find a bug report for this yet. ``` [root@puppet puppetdb]# puppetdb foreground ch.qos.logback.core.joran.spi.JoranException: Could not open [/etc/puppetdb/log4j.properties]. at ch.qos.logback.core.joran.GenericConfigurator.doConfigure (GenericConfigurator.java:80) ch.qos.logback.core.joran.GenericConfigurator.doConfigure (GenericConfigurator.java:68) sun.reflect.NativeMethodAccessorImpl.invoke0 (NativeMethodAccessorImpl.java:-2) sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:57) sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke (Method.java:606) clojure.lang.Reflector.invokeMatchingMethod (Reflector.java:93) clojure.lang.Reflector.invokeInstanceMethod (Reflector.java:28)
Jira (PDB-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Aaron Zauner updated an issue PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update Change By: Aaron Zauner Summary: puppetdb 2.0.0 throwsexceptionafteryumupdate 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-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Aaron Zauner updated an issue PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update Change By: Aaron Zauner Afterdoingasimple`yumupdate`onthepuppetservertofixtheEPELissuepuppetdbwasaswellupgraded.PuppetDBwon'tstartandthrowsanexceptionbecauseofamissinglog4j.propertiesfile(whichshouldbedepreciated,asfarasIcantellfromthegitsources). PuppetlabsDevelrepositoriesactive. I'mcurrentlytryingtofixthisissuebydowngradingtoPuppetDB1.6.
Jira (PDB-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Kenneth Barber commented on an issue Re: puppetdb 2.0.0 throws exception after yum update Lets talk about the immediate problem first ... Change your config in /etc/puppetdb/conf.d/config.ini so that the line for logging now reflects the new logging configuration: logging-config = /etc/puppetdb/logback.xml And then restart. Add Comment PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update After doing a simple `yum update` on the puppet server to fix the EPEL issue puppetdb was as well upgraded. PuppetDB won't start and throws an exception because of a missing log4j.properties file (which should be depreciated, as far as I can tell from the git sources). Puppetlabs Devel repositories active. I'm currently trying to fix this issue by down... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PDB-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update Change By: Kenneth Barber Affects Version/s: 2.0.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-1603) puppet apply failure if puppet is upgraded
Title: Message Title Rob Reynolds commented on an issue Re: puppet apply failure if puppet is upgraded Can you determine if there is another puppet installation on the machine? List the gems would help. Add Comment Puppet / PUP-1603 puppet apply failure if puppet is upgraded I am testing an update from puppet 3.2.4 to 3.4.2 and I am receiving a failure that I have found in a few different places on the internet but that has no bug and no reproducer (for reference, I believe these are related links: https://groups.google.com/forum/#!topic/puppet-users/318TmfkO9Js and https://github.com/purpleidea/puppet-puppet/commit/8b7dae5ca... 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-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Aaron Zauner commented on an issue Re: puppetdb 2.0.0 throws exception after yum update This in fact seems to work. Shouldn't maybe there be a notice to people upgrading to 2.0 about issues like that? Thanks for your help. Add Comment PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update After doing a simple `yum update` on the puppet server to fix the EPEL issue puppetdb was as well upgraded. PuppetDB won't start and throws an exception because of a missing log4j.properties file (which should be depreciated, as far as I can tell from the git sources). Puppetlabs Devel repositories active. I'm currently trying to fix this issue by down... 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-2345) Upgrading from 3.4 to 3.5 causes Puppet to fail with Could not evaluate: uninitialized constant Puppet::FileSystem::File
Title: Message Title Rob Reynolds commented on an issue Re: Upgrading from 3.4 to 3.5 causes Puppet to fail with Could not evaluate: uninitialized constant Puppet::FileSystem::File So possible that having multiple installations of puppet is messing with the loadpath and causing this error. Add Comment Puppet / PUP-2345 Upgrading from 3.4 to 3.5 causes Puppet to fail with Could not evaluate: uninitialized constant Puppet::FileSystem::File I am running a Scientific Linux 6.x system with Foreman and Puppet 3.4. Yesterday I ran `yum update`. Afterwards, Puppet failed. Downgrading Puppet from 3.5 to 3.4 prevents the error, and is what I am doing for a workaround. Steps to reproduce: 1. Notice that the error doesn't happen with Puppet 3.4 [root@puppetmaster ~]# puppet --version 3 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-1597) contain cannot contain a fully qualified class
Title: Message Title Andy Parker assigned an issue to Unassigned Puppet / PUP-1597 contain cannot contain a fully qualified class Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2324) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on an issue Re: Prepare long form release notes and short form release story Okay, thanks for the heads-up Rob Reynolds! I'll add it to the release notes. Add Comment Puppet / PUP-2324 Prepare long form release notes and short form release story Prepare long form release notes and short form release story 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-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Kenneth Barber commented on an issue Re: puppetdb 2.0.0 throws exception after yum update Aaron Zauner so the problem stems from ... if /etc/puppetdb/conf.d/config.ini has been modified, then RPM will no longer just blat new configuration into place. Instead it drops a global.ini.rpmnew (can you check this exists?) with the better proposed configuration. In this manner its cowardly refusing to just replace configuration, because your local edits may be important to you. On debian however, it prompts you instead of just dropping an rpmnew, which gives you the opportunity to diff with your existing version and make a decision if the vendored version is better or not. Some would argue this is better, but either way - RPM/YUM has nothing like that AFAIK. So the reality is, this way of YUM cowardly not updating configuration in this way is pretty standard and any sysadmin should be watching for those things during upgrades. Its unfortunate that we can't be louder at RPM install time, this especially applies to cases where users are upgrading packages automatically without user intervention (or the user seeing any mention of rpmnew files being created). Perhaps there is a better way that I don't know about. Having said that we can change the release notes for PuppetDB 2.0 to warn people ... which at least helps the users who read the release notes before upgrading a major version. Some users won't read them, and they'll raise bugs like this one (or hopefully search first and find this one). Add Comment PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update After doing a simple `yum update` on the puppet server to fix the EPEL issue puppetdb was as well upgraded. PuppetDB won't start and throws an exception because of a missing log4j.properties file (which should be depreciated, as far as I can tell from the git sources). Puppetlabs Devel
Jira (FACT-189) LXC Container support
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Facter / FACT-189 LXC Container support 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-957) Case and Selector expressions using Regexp type does not set match vars
Title: Message Title Joshua Partlow commented on an issue Re: Case and Selector expressions using Regexp type does not set match vars Merged to master in 30e4af2b Add Comment Puppet / PUP-957 Case and Selector expressions using Regexp type does not set match vars Since =~ operator treats the Regexp type as if it were a regular _expression_ and sets the match variables, so should the other conditional expressions that invoke pattern matching (case and selector). This is missing in the new evaluator implementation. (Matching is still done, but without the side effect of setting the match variables). 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-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Aaron Zauner commented on an issue Re: puppetdb 2.0.0 throws exception after yum update Thanks for the explaination. I've completely missed the *.rpmnew files. Add Comment PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update After doing a simple `yum update` on the puppet server to fix the EPEL issue puppetdb was as well upgraded. PuppetDB won't start and throws an exception because of a missing log4j.properties file (which should be depreciated, as far as I can tell from the git sources). Puppetlabs Devel repositories active. I'm currently trying to fix this issue by down... 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-2486) Per-environment cert management, with RBAC
Title: Message Title Zachary Stern created an issue Puppet / PUP-2486 Per-environment cert management, with RBAC Issue Type: New Feature Assignee: Unassigned Created: 06/May/14 9:57 AM Labels: support customer Priority: Normal Reporter: Zachary Stern It would be useful in some scenarios to have per-environment certificates, along with RBAC over who can generate and manage those certificates. In that way, a customer could control which nodes and which environment can be managed by whom. Add Comment
Jira (PUP-2328) Go/no-go meeting
Title: Message Title Rob Reynolds commented on an issue Re: Go/no-go meeting GO! Add Comment Puppet / PUP-2328 Go/no-go meeting Go/no-go meeting 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-2493) Update jenkins stable jobs if necessary
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2493 Update jenkins stable jobs if necessary Issue Type: Sub-task Assignee: Rob Reynolds Created: 06/May/14 10:20 AM Priority: Normal Reporter: Rob Reynolds The jobs on jenkins may require updates (spec, acceptance, etc) when you merge master into stable. Please ensure that there are no changes needed to be made. Dependencies: Merge master into stable Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2489) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2489 Is there a JIRA ticket targeted at the release for every commit? Issue Type: Sub-task Assignee: Rob Reynolds Created: 06/May/14 10:20 AM Priority: Normal Reporter: Rob Reynolds Ensure all tickets referenced in the commit log have a bug targeted at the release git log old tag..new tag look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release Also, make sure the code itself is sane, that you understand why the change was made, etc. etc. ticketmatch.rb script is a ruby script that helps with tasks 3 and 4 (it beats doing it manually, but requires manual steps and hacking the script for the specific release) Add Comment
Jira (PUP-2491) Update version number in source
Title: Message Title
Rob Reynolds created an issue
Puppet / PUP-2491
Update version number in source
Issue Type:
Sub-task
Assignee:
Rob Reynolds
Created:
06/May/14 10:20 AM
Priority:
Normal
Reporter:
Rob Reynolds
Bump VERSION in lib/ {#project}
/version.rb to correct version.
Commit the updated version file.
e.g) commit -m (packaging) Update FACTERVERSION to 1.7.3-rc1.
If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask).
Once this is done, hand the SHA to be built to RelEng to be tagged.
Dependencies:
Is the code ready for release?
Is there a commit for every JIRA ticket targeted at the release?
Jira (PUP-2487) Puppet 3.6.0-TEST 2014-05-20 Release
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2487 Puppet 3.6.0-TEST 2014-05-20 Release Issue Type: Task Assignee: Release Engineering Created: 06/May/14 10:20 AM Priority: Normal Reporter: Rob Reynolds Puppet 3.6.0-TEST 2014-05-20 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the Prepare notes and Tag release/create packages tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for Tag Release/create packages, you should move Smoke test packages to Ready for Engineering or In Progress if you are ready.
Jira (PUP-2492) Merge master into stable
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2492 Merge master into stable Issue Type: Sub-task Assignee: Rob Reynolds Created: 06/May/14 10:20 AM Priority: Normal Reporter: Rob Reynolds git checkout stable git merge master --no-ff --log Dependencies: Is the code ready for release? Is there a commit for every JIRA ticket targeted at the release? Update version number in source Add Comment
Jira (PUP-2495) Prepare long form release notes and short form release story
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2495 Prepare long form release notes and short form release story Issue Type: Sub-task Assignee: Rob Reynolds Created: 06/May/14 10:20 AM Priority: Normal Reporter: Rob Reynolds Collaborating with product for release story Dependencies: Is there a JIRA ticket targeted at the release for every commit? Is there a commit for every JIRA ticket targeted at the release? Add Comment This message
Jira (PUP-2494) Is a new version created in Jira for the next version in the series?
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2494 Is a new version created in Jira for the next version in the series? Issue Type: Sub-task Assignee: Rob Reynolds Created: 06/May/14 10:20 AM Priority: Normal Reporter: Rob Reynolds This happens on Jira - there needs to be a version we can target future issues or issues that didn't make it into the current release. e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) If releasing an RC, ensure you create the RC version e.g 3.6.0 RC (leave RC number off of here). Add Comment
Jira (PUP-2490) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2490 Is there a commit for every JIRA ticket targeted at the release? Issue Type: Sub-task Assignee: Rob Reynolds Created: 06/May/14 10:20 AM Priority: Normal Reporter: Rob Reynolds Ensure all tickets targeted at the release have a corresponding commit git log old tag..new tag This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers ticketmatch.rb script is a ruby script that helps with tasks 3 and 4 (it beats doing it manually, but requires manual steps and hacking the script for the specific release) Add Comment
Jira (PUP-2488) Is the code ready for release?
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2488 Is the code ready for release? Issue Type: Sub-task Assignee: Rob Reynolds Created: 06/May/14 10:20 AM Priority: Normal Reporter: Rob Reynolds All tests (spec, acceptance) should be passing on all platforms for both stable master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. NOTE: This link may not work properly for RC releases. Edit it to remove the -rc#. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%223.6.0-TEST%22
Jira (PUP-2497) Smoke test packages
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2497 Smoke test packages Issue Type: Sub-task Assignee: Rob Reynolds Created: 06/May/14 10:20 AM Priority: Normal Reporter: Rob Reynolds Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through this testing. Lighter testing is acceptable. Add a link to the Packages repository that you receive from the Tag and create packages subtask Ping folks on your team for help with different platforms. When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment. When all platforms picked have been smoke tested, move this ticket to done. Example: Smoke test platforms: pick some platforms such as RHEL 5/6/7
Jira (PUP-2499) Push tag
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2499 Push tag Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 06/May/14 10:20 AM Priority: Normal Reporter: Rob Reynolds The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. Dependencies: Go / No Go meeting (except where it's required to push the tag to build packages - MSIs) Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2502) Docs pushed
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2502 Docs pushed Issue Type: Sub-task Assignee: Rob Reynolds Created: 06/May/14 10:21 AM Priority: Normal Reporter: Rob Reynolds Push the documentation updates to docs.puppetlabs.com. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2504) Close all resolved tickets in Jira
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2504 Close all resolved tickets in Jira Issue Type: Sub-task Assignee: Rob Reynolds Created: 06/May/14 10:21 AM Priority: Normal Reporter: Rob Reynolds Close any tickets that have been resolved for the release. NOTE: This link may not work properly for RC releases. Edit it to remove the -rc#. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%223.6.0-TEST%22 Dependencies: Packages pushed Add Comment This message was sent by
Jira (PUP-2496) Tag the release and create packages
Title: Message Title
Rob Reynolds created an issue
Puppet / PUP-2496
Tag the release and create packages
Issue Type:
Sub-task
Assignee:
Kylo Ginsberg
Created:
06/May/14 10:20 AM
Priority:
Normal
Reporter:
Rob Reynolds
Tag and create packages
Developer provides the SHA - Rob Reynolds - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
NOTE: If this is a final release, make sure you're releasing only the code that already went through rc, so don't let any new code get into the final release
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m 1.7.3-rc1 1.7.3-rc1
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git
Jira (PDB-631) Update documentation indexes for new major release
Title: Message Title Kenneth Barber commented on an issue Re: Update documentation indexes for new major release Prepped the PR, just waiting for release: https://github.com/puppetlabs/puppet-docs/pull/320 Add Comment PuppetDB / PDB-631 Update documentation indexes for new major release The current documentation indexes need to be updated for a final release. The main index needs the release to be moved into the stable section, and the index for this release needs the pre-release meesage removed. 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-2498) Go/no-go meeting
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2498 Go/no-go meeting Issue Type: Sub-task Assignee: Rob Reynolds Created: 06/May/14 10:20 AM Priority: Normal Reporter: Rob Reynolds Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Add Comment This message was sent by Atlassian JIRA
Jira (PUP-2501) Update the downloads page
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2501 Update the downloads page Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 06/May/14 10:20 AM Priority: Normal Reporter: Rob Reynolds Update downloads page Update misc/download-options to reflect the new builds you just pushed and also make sure they're displayed. It's a good idea to make sure this looks like it's supposed to NOTE: this page will hopefully be deprecated soon. The idea is that docs with update their documentation to include latest release version and where to download files. This page will then be changed to redirect to docs.puppetlabs.com and will no longer need updating. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment
Jira (PUP-2503) Send out announcements
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2503 Send out announcements Issue Type: Sub-task Assignee: Eric Sorenson Created: 06/May/14 10:21 AM Priority: Normal Reporter: Rob Reynolds Update the release google document (ask around for location). Send the drafted release notes email. If RC send to puppet-users and puppet-dev. If final send to puppet-announce, puppet-users, and puppet-dev. Make a PSA on IRC #puppet letting those kiddos know about the new release. Something along the lines of PSA: facter 1.7.3-rc1 now available Dependencies: Prepare long form release notes and short form release story Packages pushed
Jira (PUP-2500) Packages pushed
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2500 Packages pushed Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 06/May/14 10:20 AM Priority: Normal Reporter: Rob Reynolds Push packages run `rake pl:jenkins:uber_ship` You will need the keys to the castle (aka the passphrase) for this to work. Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms. Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay. If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file. If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Matthaus Owens for more details. This file also needs to be manually signed. Dependencies:
Jira (PDB-636) Smoke test packages
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-636 Smoke test packages Change By: Kenneth Barber Assignee: KennethBarber 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-651) PR (962): Allow configurable url prefix - cprice404
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-651 PR (962): Allow configurable url prefix - cprice404 Change By: Kenneth Barber Story Points: 0 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 (PDB-640) Update the downloads page
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-640 Update the downloads page Change By: Kenneth Barber Assignee: MelissaStone KennethBarber 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-637) Go/no-go meeting
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-637 Go/no-go meeting Change By: Kenneth Barber Assignee: KennethBarber 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-2240) support unfold/splat of array
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2240 support unfold/splat of array 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 (PDB-551) Make a statement about new API versioning for 2.0.0
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-551 Make a statement about new API versioning for 2.0.0 Change By: Kenneth Barber Fix Version/s: 2.0.0 Fix Version/s: 2.0.x 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-189) LXC Container support
Title: Message Title Ethan Brown commented on an issue Re: LXC Container support Merged to facter-2 in https://github.com/puppetlabs/facter/commit/bee8827177f5ffa7aa3aae35eddefcdb08790826 I have verified that `docker` and `lxc` show up where appropriate in the following environments: Mac OSX (Mavericks) - VirtualBox - boot2docker (Tiny Core Linux) with Docker 0.10 - Ubuntu docker template – properly emits virtual = docker Windows 8 - Hyper-V - boot2docker with Docker 0.10 - Ubuntu docker template – properly emits virtual = docker Windows 8 - Hyper-V - Ubuntu Server 14.04 LTS - Ubuntu LXC template – properly emits virtual = lxc I followed the basic instructions at http://blog.scottlowe.org/2013/11/25/a-brief-introduction-to-linux-containers-with-lxc/ for rigging up LXC. So once this passes through CI, I think we're safe to pass the functional review. Add Comment Facter / FACT-189 LXC Container support The virtual fact for facter should support lxc containers. For more information about lxc: http://lxc.sourceforge.net/ We can detect an running lxc master system, if /cgroup is mounted on the system. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-523) Add 'private' as a keyword to make classes (and defines?) private to a module
Title: Message Title Andy Parker updated an issue Puppet / PUP-523 Add 'private' as a keyword to make classes (and defines?) private to a module Change By: Andy Parker Fix Version/s: 3.7.0 Fix Version/s: 4.x 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-1603) puppet apply failure if puppet is upgraded
Title: Message Title Jason Corley commented on an issue Re: puppet apply failure if puppet is upgraded sure, but since I gave reproducer steps involving using a vagrant box and fresh yum installs the output is what you might expect (mainly, no gems of note): [vagrant@localhost ~]$ rpm -qa ruby\* --pipe=LANG=C sort ruby-1.8.7.352-13.el6.x86_64 ruby-augeas-0.4.1-3.el6.x86_64 ruby-irb-1.8.7.352-13.el6.x86_64 ruby-libs-1.8.7.352-13.el6.x86_64 ruby-rdoc-1.8.7.352-13.el6.x86_64 ruby-rgen-0.6.5-2.el6.noarch ruby-shadow-2.2.0-2.el6.x86_64 rubygem-json-1.5.5-1.el6.x86_64 rubygems-1.3.7-5.el6.noarch [vagrant@localhost ~]$ gem list *** LOCAL GEMS *** json (1.5.5) [vagrant@localhost ~]$ Add Comment Puppet / PUP-1603 puppet apply failure if puppet is upgraded I am testing an update from puppet 3.2.4 to 3.4.2 and I am receiving a failure that I have found in a few different places on the internet but that has no bug and no reproducer (for reference, I believe these are related links: https://groups.google.com/forum/#!topic/puppet-users/318TmfkO9Js and https://github.com/purpleidea/puppet-puppet/commit/8b7dae5ca... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
