Jira (PUP-2455) Puppet running as Solaris SMF service needs to run child processes in separate contract
Title: Message Title redmine.exporter created an issue Puppet / PUP-2455 Puppet running as Solaris SMF service needs to run child processes in separate contract Issue Type: Bug Assignee: Unassigned Created: 05/May/14 12:48 AM Labels: redmine Priority: Normal Reporter: redmine.exporter 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, the contract doesn't finish within the configured timeout, and so SMF puts the service into maintenance state and sends *kill -9* to all processes still left in the contract. It is possible to force a process to run in a new contract (e.g. using /usr/bin/ctrun) and it would be useful if Puppet could support this on Solaris, so that the agent can be stopped/restarted without affecting services that it manages. Steps to reproduce: 1. Configure and run a puppet agent as an SMF service (using the default contract model of service management). (For example, install configure the OpenCSW Puppet package) 2. Set puppet to manage a daemon that is started by an init script. 3. Try to stop the puppet agent. 4. Observe (from the service log files, server's messages file, and process listings) that the init-controlled daemon has been killed and the puppet agent service placed into maintenance state. In my test scenario, Puppet was starting an exim daemon
Jira (PUP-2455) Puppet running as Solaris SMF service needs to run child processes in separate contract
Title: Message Title Jan rnstedt commented on an issue Re: Puppet running as Solaris SMF service needs to run child processes in separate contract NAME ctrun - execute command in a process contract SYNOPSIS /usr/bin/ctrun [options] command [ argument...] DESCRIPTION The ctrun utility starts a command in a newly created pro- cess contract. ctrun holds the contract and can be instructed to output or respond to events that occur within the contract. For additional information about process contracts, see con- tract(4) and process(4). 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-2455) Puppet running as Solaris SMF service needs to run child processes in separate contract
Title: Message Title Jan rnstedt commented on an issue Re: Puppet running as Solaris SMF service needs to run child processes in separate contract This needs to be included in the start and restart method of this script service/init.rb. 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) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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-2456) environment is not reset in user crontabs
Title: Message Title Klavs Klavsen created an issue Puppet / PUP-2456 environment is not reset in user crontabs Issue Type: Bug Assignee: Unassigned Created: 05/May/14 1:54 AM Priority: Normal Reporter: Klavs Klavsen if I define a cronjob, with an environment setting for PATH, MAILTO etc. - then depending on WHERE in the users crontab it is inserted - this environment setting also affects every entry after this - and there is AFAIK no way to control in which order they are inserted into crontab - so other cronjobs could easily be unwillingly affected My suggestion, would be to reset the environment settings, right after.. So if the environment has MAILTO=.. set.. then set it to what it originally was before this (if no MAILTO is set in the file.. then MAILTO=$username ) It's definetely not perfect though. Add Comment
Jira (PUP-2455) Puppet running as Solaris SMF service needs to run child processes in separate contract
Title: Message Title Jan rnstedt updated an issue Puppet / PUP-2455 Puppet running as Solaris SMF service needs to run child processes in separate contract Change By: Jan rnstedt Labels: redmine solaris 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-2455) Puppet running as Solaris SMF service needs to run child processes in separate contract
Title: Message Title Jan rnstedt commented on an issue Re: Puppet running as Solaris SMF service needs to run child processes in separate contract Otherwise you will end up with additional processes in the puppet agent contract. '''# svcs -p puppet STATE STIME FMRI online Apr_26 svc:/application/puppet:agent Apr_26 18754 puppet Apr_26 19225 vmtoolsd''' 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) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title vinod kumar commented on an issue Re: Invalid parameter provider for custom types/providers I also observed the similar behavior with custom environment path. Following is the alternate to work with: Install puppet module without any environment i.e. puppet module install puppetlabs-vcsrepo This will install the vcsrepo module under $puppet-conf-dir/modules directory. Now, you can access puppet agent with the custom environment like puppet agent --test --environment fail Also enable 'pluginsync = true' in puppet.conf file Hope this will work for every one as it is working for me. Add Comment Puppet / PUP-1515 Invalid parameter provider for custom types/providers In Puppet 3 I am getting an error on all definitions for custom types. It says Error 400 on SERVER: Invalid parameter provider Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're ...
Jira (PUP-1456) Type exec is executed, although required type failed
Title: Message Title Bjoern Lippert commented on an issue Re: Type exec is executed, although required type failed Hello Charlie, exactly, the seen behaviour could be led back to PUP-1106. So in my special case, each exec in the called define get a refresh event due to the define calling routine in the surrounding define (aka. the calling define) has a subscribe to another resource. I guess I've got no other choice than finding a workaround for me. However in my opinion the current behaviour is logically wrong and should be changed. Regards Bjoern Add Comment Puppet / PUP-1456 Type exec is executed, although required type failed An exec-type is executed although a required type (an exec, too) has failed. The strange thing is, that when doing an agent run ,the output of puppet agent --test says Skipping because of failed dependency. The output is correct (as expected), but nevertheless the exec-type gets executed. As I have problems in my productive code, that woul... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you
Jira (PUP-2457) [SCALABILITY] Migrating from 2.X using Mongrel to 3.X
Title: Message Title Johann Pavis created an issue Puppet / PUP-2457 [SCALABILITY] Migrating from 2.X using Mongrel to 3.X Issue Type: Story Assignee: Eric Sorenson Components: DOCS Created: 05/May/14 6:42 AM Priority: Normal Reporter: Johann Pavis Original Estimate: 1 hour Remaining Estimate: 1 hour Hi, I'm using Puppet 2.7. On my masters, I use 4 instances of puppetmasterd and the are accessed through Nginx. I read that version 3 does not support Mongrel anymore. My question is, how can I have the same behavior with version 3 as the behavior I have with version 2.7 ? Best regards Johann
Jira (PUP-488) Test ResourceType[x] (a.k.a resource params access)
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-488
Test ResourceType[x] (a.k.a resource params access)
Change By:
Henrik Lindberg
Anexpressionssuchas:*File['title'][ensure]shouldproducethevalueoftheensureattributeofthereferenceFileinstance. {strike} (Current4ximplementationtreatsthisasanerror,butiseasilychangedtobecomeanattributelookup). {strike}
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-1028) Test future evaluator impl of Node Expresson
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1028 Test future evaluator impl of Node Expresson Change By: Henrik Lindberg TheNodeExpressionsareimplementedandonmaster.Thereareonlyafewtestsspecificforthefutureparser/evaluatorfornodeexpressions. Access Assess iftheavailableacceptancetestsprovideenoughcoverage.Implementmissingtestsasunittests. 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-488) Test ResourceType[x] (a.k.a resource params access)
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-488
Test ResourceType[x] (a.k.a resource params access)
Change By:
Henrik Lindberg
Anexpressionssuchas:*File['title'][ensure]shouldproducethevalueoftheensureattributeofthereferenceFileinstance. {strike} - (Current4ximplementationtreatsthisasanerror,butiseasilychangedtobecomeanattributelookup). {strike} -
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 Henrik Lindberg commented on an issue Re: Case and Selector expressions using Regexp type does not set match vars I will make an implementation as proposed so we have something to review. 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 (PUP-957) Case and Selector expressions using Regexp type does not set match vars
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-957 Case and Selector expressions using Regexp type does not set match vars 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-2458) Tests for providers inheriting from providers of another type
Title: Message Title Dominic Cleal created an issue Puppet / PUP-2458 Tests for providers inheriting from providers of another type Issue Type: Improvement Assignee: Dominic Cleal Components: Types and Providers Created: 05/May/14 7:44 AM Priority: Minor Reporter: Dominic Cleal It's sometimes desirable to create new providers that inherit from providers of a different type. The inifile module does this currently to create more specialised types: https://github.com/puppetlabs/puppetlabs-inifile#implementing-child-providers Puppet::Type.type(:glance_api_config).provide( :ini_setting, # set ini_setting as the parent provider :parent = Puppet::Type.type(:ini_setting).provider(:ruby) ) do The ini_setting type has a standard ruby provider, but here a new glance_api_config type has been created which has an ini_setting provider itself derived from the standard ruby provider from ini_setting (the type). We want to use a similar technique in augeasproviders to have a standard provider containing utility implementations, then let others derive from it to create specialised providers. This also neatly sidesteps many issues with loading library code from Puppet providers. This works today, but I'd like to add tests in core to prove it works and to ensure this functionality remains.
Jira (PUP-1680) incorrect header check using Ruby 2.1.0
Title: Message Title
Kyle Smith commented on an issue
Re: incorrect header check using Ruby 2.1.0
I've found the root cause of this issue, but I'm not sure what the preferred way to tackle it is.
It's a bit of a rat's nest, but here's the idea:
In content.rb:
def chunk_file_from_source(source_or_content)
get_from_source(source_or_content) do |response|
case response.code
when /^2/; uncompress(response) { |uncompressor| response.read_body { |chunk| yield uncompressor.uncompress(chunk) } }
else
# Raise the http error if we didn't get a 'success' of some kind.
message = Error #{response.code} on SERVER: #{(response.body||'').empty? ? response.message : uncompress_body(response)}
raise Net::HTTPError.new(message, response)
end
end
end
chunk_file_from_source calls get_from_source with a block, which calls Puppet::Network::HTTP::Connection#request_get, which is a direct wrapper around Net::HTTP#request_get. Ruby 2.1.1 includes all the automatic Accept-Encoding / decompression magic. When you have a response object (yielded in #request_get), it is not yet decompressed. If you check the headers, you will see Content-Encoding: gzip. Once you call #read_body or #read (as is done above in chunk_file_from_source, the decompression and modification of headers is done. Unfortunately the uncompress method of Connection has already read the headers and assigned a ZlibAdapter to decompress the results.
Here's a demo program that can exercise the failure, with comment:
require 'net/http'
require 'openssl'
# Make sure you web server will attempt to compress this file (e.g. mod_deflate)
uri = URI.parse('https://puppet.example.com:8140/devel/file_content/modules/mymodule/myfile.html')
cert = File.read('/var/lib/puppet/ssl/certs/client.example.com.pem')
key = File.read('/var/lib/puppet/ssl/private_keys/client.example.com.pem')
conn = Net::HTTP.new(uri.host, uri.port)
conn.use_ssl = true
conn.cert = OpenSSL::X509::Certificate.new(cert)
conn.key = OpenSSL::PKey::RSA.new(key)
conn.verify_mode = OpenSSL::SSL::VERIFY_NONE
# Add 'Accept-Encoding' = 'None' to the hash to see the inverse behavior.
conn.request_get(uri.path, 'Accept' = 'raw') do |resp|
pp resp.to_hash # Shows the Content-encoding: gzip header.
# Puppet uses this response value to detemine if it needs
# to decompress data.
# Ruby 2.1.1 responds to #decode_content, which does not actually decode any
# content, but instead tells the caller if the content would be decoded when
# a read method is called.
puts resp#decode_content = #{resp.decode_content}
pp resp.body # Triggers Ruby to perform decompression and modify headers.
pp resp.to_hash # Does not show the Content-encoding: gzip header.
end
Jira (PUP-1814) Double backslashes in single quote strings should be interpreted as single
Title: Message Title
Sebastian Schmidt commented on an issue
Re: Double backslashes in single quote strings should be interpreted as single
Good point, thanks!
Add Comment
Puppet / PUP-1814
Double backslashes in single quote strings should be interpreted as single
Double backslashes in single quoted strings should be interpreted as single backslashes but aren't. The following manifest: {code} notice('foo\\bar') {code} Gives: {code} notice: Scope(Class[main]): foo\\bar {code} This is not the behavior described at [http://docs.puppetlabs.com/guides/language_guide.html#quoting](http://docs.puppetlab...
This message was sent by Atlassian JIRA (v6.1.4#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-1680) incorrect header check using Ruby 2.1.0
Title: Message Title
Kyle Smith commented on an issue
Re: incorrect header check using Ruby 2.1.0
If anyone else is encountering this issue, I've just confirmed a workaround:
You can set http_compression = true in the [main] section of your puppet.conf file. This tells Puppet to append it's own Accept-Encoding: header to the request, thereby causing Ruby to assume Puppet will handle any necessary decoding (which it will).
The core issue is that in Ruby 2.1.1, Ruby itself tacks an Accept-Encoding: header to every request.
Add Comment
Puppet / PUP-1680
incorrect header check using Ruby 2.1.0
I haven't found anything out there so far, so I thought I'd just document it while I'm at it. We ran into some other problem with the changes in net/http Ruby 2.1.0 introduced around the handling of gzip/deflate encoded content. This MIGHT be related. So far we haven't been able to fix it. {code} Error: incorrect header check Error: /Stage[main]/...
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 (FACT-479) Custom facts with facter 1.7.5 on AIX display facts as [fact value]
Title: Message Title Ryan Anderson created an issue Facter / FACT-479 Custom facts with facter 1.7.5 on AIX display facts as [fact value] Issue Type: Bug Affects Versions: 1.7.5 Assignee: Eric Sorenson Components: Community Created: 05/May/14 8:41 AM Environment: operating system Priority: Normal Reporter: Ryan Anderson I have a ruby custom fact that when queried with 'facter -p mysite' on AIX 6.1/7.1 displays as expected (eg TX), but if I do 'facter -p | grep mysite' it shows up like [TX]. It will show up this wrong way when it goes to puppetdb. The facter version is 1.7.5 with puppet 3.4.3, both installed via gems, on AIX with ruby 2.0.0p353. The built-in facts do not have this same issue. The custom ruby fact code is something like: Facter.add(mysite) do setcode do case Facter.value(:ipaddress) when /^10\.1\.91\.|^10\.1\.92\.|^10\.1\.93\./ TX when /^13\.1\.1\.|^13\.1\.2\./ CA end end end
Jira (FACT-233) Fact to add DHCP Server Details
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Facter / FACT-233 Fact to add DHCP Server Details Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (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 (FACT-247) Support netmask fact on AIX
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Facter / FACT-247 Support netmask fact on AIX Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2241) Add logging functions to static loader
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2241 Add logging functions to static loader Change By: Rob Reynolds Sprint: Week2014-4-30to2014-5-7 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 updated an issue Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format Change By: Rob Reynolds Sprint: Week2014-4-30to2014-5-7 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 Hunter Haugen assigned an issue to Hunter Haugen Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format Change By: Hunter Haugen Assignee: HunterHaugen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper Change By: Rob Reynolds Fix Version/s: 3.7.0 Fix Version/s: 3.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-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper Change By: Rob Reynolds 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-2010) have test repos pushed to hosts during acceptance testing
Title: Message Title Adrien Thebo commented on an issue Re: have test repos pushed to hosts during acceptance testing Merged into master in 334acf3. Add Comment Puppet / PUP-2010 have test repos pushed to hosts during acceptance testing Currently, in install_utils.rb, repos are pulled directly from the individual test hosts. This does not work for hosts that live outside our internal network and are unable to reach builds.puppetlabs.lan. By changing around the logic so that the puppet master node pulls the repos and then pushes them to the test hosts we can test packaged builds in ... This message was sent by Atlassian JIRA (v6.1.4#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-2345) Upgrading from 3.4 to 3.5 causes Puppet to fail with Could not evaluate: uninitialized constant Puppet::FileSystem::File
Title: Message Title Richard Davies 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 I had the same issue upgrading from 3.4.3 to 3.5.1 using the puppetlabs rpms on CentOS 6.5. For me it was caused by a puppet-3.4.3 gem installed outside of yum/rpm (as a dependency of puppet-lint or puppet-cleaner) found by: yum update ... --- Package puppet.noarch 0:3.4.3-1.el6 will be updated --- Package puppet.noarch 0:3.5.1-1.el6 will be an update --- Package puppet-server.noarch 0:3.4.3-1.el6 will be updated --- Package puppet-server.noarch 0:3.5.1-1.el6 will be an update ... Updated: puppet.noarch 0:3.5.1-1.el6 puppet-server.noarch 0:3.5.1-1.el6 Complete! puppet apply --no-daemonize --trace /etc/puppet/manifests/site.pp Notice: Compiled catalog for host in environment production in 0.08 seconds Failed to load feature test for libuser: uninitialized constant Puppet::FileSystem::File Error: /File[/etc/puppet]: Could not evaluate: uninitialized constant Puppet::FileSystem::File /usr/lib/ruby/gems/1.8/gems/puppet-3.4.3/lib/puppet/type/file.rb:698:in `stat' /usr/lib/ruby/site_ruby/1.8/puppet/type/file/ensure.rb:166:in `retrieve' ... Updating that gem solved the problem for me, but it might be more reliable to remove it if it isn't needed. 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
Jira (PUP-2241) Add logging functions to static loader
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-2241 Add logging functions to static loader Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1046) puppet module generate should produce a skeleton spec test
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-1046 puppet module generate should produce a skeleton spec test Change By: Rob Reynolds Fix Version/s: 3.6.0 Fix Version/s: 3.6.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 (HI-118) There's no way to set resolution_type when using data bindings
Title: Message Title John Bollinger commented on an issue Re: There's no way to set resolution_type when using data bindings When I thought a bit about this because of a question on puppet-users, I realized that it is not an issue that can be solved by a change to Puppet DSL or to the way Puppet uses Hiera internally. Whether a priority lookup, a hash-merge lookup, or an array lookup is wanted in a particular data-binding situation is not (or at least should not be) a function of the class. Rather, it is an aspect of the data themselves. That is, even if there were a way to express in a class definition that a particular parameter should be bound via a hash-merge lookup (for example), that would just turn the problem around on people who want to use a priority lookup for that parameter. And, wow, I just saw the broader implication: the same argument applies to any use of hiera_array() or hiera_hash(). The intended meaning of the data is part of the data definition, and looking it up via a different function than intended changes that meaning. Hiera (the YAML back end) does not have a mechanism to express this aspect of the data, so the data consumer is left to guess which of three functions is the appropriate one to use for retrieval, without even a means to check after the fact whether they guessed right. Bottom line: hiera_hash() and hiera_array() should both be deprecated in favor of a means to express the intended retrieval type directly in the data. The hiera() function, whether invoked from the DSL or internally by Puppet, should use that means to retrieve the data correctly. Add Comment Hiera / HI-118 There's no way to set resolution_type when using data bindings Because it's the responsibility of the caller to set `resolution_type` in hiera, and there is no explicit caller when using data bindings, there's no way to tell hiera to use the array (append) or hash
Jira (PDB-650) PR (961): Fix a race condition in the import/export round-trip clojure tests - senior
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-650 PR (961): Fix a race condition in the import/export round-trip clojure tests - senior Issue Type: Task Assignee: Unassigned Created: 05/May/14 11:18 AM Labels: github Priority: Normal Reporter: gepetto-bot Fix a race condition in the import/export round-trip clojure tests Author: Ryan Senior senior.r...@gmail.com Company: Github ID: senior Pull Request 961 Discussion Pull Request 961 File Diff Pull Request Description This scenario occurred if command processing for facts is slow. A result with the hard coded certname would be returned with no fact values or environment. This commit fixes the code to only return results when facts are found. This has been targeted at stable but
Jira (FACT-472) Sync facter-2 code with master
Title: Message Title Adrien Thebo updated an issue Facter / FACT-472 Sync facter-2 code with master Change By: Adrien Thebo Summary: Syncfacter-2code into with master 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-472) Sync facter-2 code with master
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-472 Sync facter-2 code with master Change By: Adrien Thebo Assignee: EricSorenson AdrienThebo 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-472) Sync facter-2 code into master
Title: Message Title Adrien Thebo updated an issue Facter / FACT-472 Sync facter-2 code into master Change By: Adrien Thebo Summary: SwizzlebranchesandupdateCI Syncfacter-2codeintomaster 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-472) Sync facter-2 code with master
Title: Message Title Adrien Thebo commented on an issue Re: Sync facter-2 code with master I've created a pull request based on creating a patch of the current state of facter-2 and applying that to master. As noted on the pull request this is a very aggressive approach so I would like for others to vet it closely before we pull the trigger. Add Comment Facter / FACT-472 Sync facter-2 code with master It seems like conversations have converged on: * master - zombie (and isn't updated) * make master carry the content of facter-2 (revert a lot and merge up?) * remove facter-2 And then only do CI on stable and master and cherry-pick/port from zombie as we go. [~adrien] [~peter.huene] please 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 (FACT-189) LXC Container support
Title: Message Title Ethan Brown commented on an issue Re: LXC Container support Failed review inside of boot2docker on OSX. 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) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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 The facts return against Docker 0.10 were `virtual = virtualbox` and `is_virtual = true` It would appear that the cgroup output for Docker has changed and longer matches what was specified in the pull request. For now, decided with Jeff McCune that it makes sense to keep the original LXC facts, but to add something additional that will output docker where appropriate. For reference, inside Docker, `/proc/1/cgroup` looks like this: root@0e3c605ac147:/home/root/facter# cat /proc/1/cgroup 9:perf_event:/ 8:blkio:/ 7:freezer:/ 6:devices:/docker/0e3c605ac1470c776c34a8eff362a0c816bcaac78559a43955173bd786281b7f 5:memory:/ 4:cpuacct:/ 3:cpu:/docker/0e3c605ac1470c776c34a8eff362a0c816bcaac78559a43955173bd786281b7f 2:cpuset:/ 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 (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 pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/419/ 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
Jira (PDB-651) PR (962): Allow configurable url prefix - cprice404
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-651 PR (962): Allow configurable url prefix - cprice404 Issue Type: Task Assignee: Unassigned Created: 05/May/14 1:16 PM Labels: github Priority: Normal Reporter: gepetto-bot Allow configurable url prefix Author: Chris Price Company: Github ID: cprice404 Pull Request 962 Discussion Pull Request 962 File Diff Pull Request Description This PR makes it possible to configure a url prefix (for the web app that we will register with jetty, as well as with the terminus) so that PuppetDB can be mounted at a location other than /. I will need to add some docs, but wanted to get some input on the general direction first.
Jira (PUP-2459) Puppet 3.6.0-TEST 2014-05-10 Release
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2459 Puppet 3.6.0-TEST 2014-05-10 Release Issue Type: Task Assignee: Release Engineering Created: 05/May/14 1:29 PM Priority: Normal Reporter: Rob Reynolds Puppet 3.6.0-TEST 2014-05-10 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-2463) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2463 Is there a commit for every JIRA ticket targeted at the release? Issue Type: Sub-task Assignee: Rob Reynolds Created: 05/May/14 1:29 PM 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-2461) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2461 Is there a JIRA ticket targeted at the release for every commit? Issue Type: Sub-task Assignee: Rob Reynolds Created: 05/May/14 1:29 PM 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-2469) Tag the release and create packages
Title: Message Title
Rob Reynolds created an issue
Puppet / PUP-2469
Tag the release and create packages
Issue Type:
Sub-task
Assignee:
Kylo Ginsberg
Created:
05/May/14 1:29 PM
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 describe`
Jira (PUP-2471) Go/no-go meeting
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2471 Go/no-go meeting Issue Type: Sub-task Assignee: Rob Reynolds Created: 05/May/14 1:29 PM Priority: Normal Reporter: Rob Reynolds Get a yes/no for the release from dev, docs, product, qa, releng. Dependencies: Smoke testing Have all JIRA tickets for the release been resolved? Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2467) Is a new version created in Jira for the next version in the series?
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2467 Is a new version created in Jira for the next version in the series? Issue Type: Sub-task Assignee: Rob Reynolds Created: 05/May/14 1:29 PM 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-2465) Merge master into stable
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2465 Merge master into stable Issue Type: Sub-task Assignee: Rob Reynolds Created: 05/May/14 1:29 PM Priority: Normal Reporter: Rob Reynolds git checkout stable git merge master --no-ff --log Dependencies: Ensure tests are passing Is there a commit for every JIRA ticket targeted at the release? Update version number in source Add Comment
Jira (PUP-2470) Smoke test packages
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2470 Smoke test packages Issue Type: Sub-task Assignee: Rob Reynolds Created: 05/May/14 1:29 PM 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-2464) Update version number in source
Title: Message Title
Rob Reynolds created an issue
Puppet / PUP-2464
Update version number in source
Issue Type:
Sub-task
Assignee:
Rob Reynolds
Created:
05/May/14 1:29 PM
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:
Ensure tests are passing
Is there a commit for every JIRA ticket targeted at the release?
Jira (PUP-2477) Close all resolved tickets in Jira
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2477 Close all resolved tickets in Jira Issue Type: Sub-task Assignee: Rob Reynolds Created: 05/May/14 1:30 PM 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-2462) Have all JIRA tickets for the release been resolved?
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2462 Have all JIRA tickets for the release been resolved? Issue Type: Sub-task Assignee: Rob Reynolds Created: 05/May/14 1:29 PM Priority: Normal Reporter: Rob Reynolds Have all tickets been resolved (passed Functional Review)? If not, please add any missing tickets to the 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 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2474) Update the downloads page
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2474 Update the downloads page Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 05/May/14 1:29 PM 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-2466) Update jenkins stable jobs if necessary
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2466 Update jenkins stable jobs if necessary Issue Type: Sub-task Assignee: Rob Reynolds Created: 05/May/14 1:29 PM 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-2468) Prepare long form release notes and short form release story
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2468 Prepare long form release notes and short form release story Issue Type: Sub-task Assignee: Rob Reynolds Created: 05/May/14 1:29 PM 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 was
Jira (PUP-2472) Push tag
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2472 Push tag Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 05/May/14 1:29 PM 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-2462) Have all JIRA tickets for the release been resolved?
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2462 Have all JIRA tickets for the release been resolved? Change By: Rob Reynolds Haveallticketsbeenresolved(passedFunctionalReview)? Ifnot,pleaseaddanymissingticketstotheboard. NOTE:ThislinkmaynotworkproperlyforRCreleases.Editittoremovethe-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 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-2476) Send out announcements
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2476 Send out announcements Issue Type: Sub-task Assignee: Eric Sorenson Created: 05/May/14 1:30 PM 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-2475) Docs pushed
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2475 Docs pushed Issue Type: Sub-task Assignee: Rob Reynolds Created: 05/May/14 1:30 PM 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-2473) Packages pushed
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2473 Packages pushed Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 05/May/14 1:29 PM 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 (PUP-2460) Ensure tests are passing
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2460 Ensure tests are passing Issue Type: Sub-task Assignee: Rob Reynolds Created: 05/May/14 1:29 PM 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 Add Comment
Jira (PUP-2471) Go/no-go meeting
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2471 Go/no-go meeting Change By: Rob Reynolds Getayes/noforthereleasefromdev,docs,product,qa,releng. Typicallythismeetingwillhappenrightbeforepackagesarepushed.Keepinmindweusuallydonotshipreleasesintheeveningandwedon'tshiponFridayifthereleaseisafinalrelease. Dependencies: *Smoketesting *HaveallJIRAticketsforthereleasebeenresolved? 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 Hunter Haugen commented on an issue Re: `puppet module build` should use `metadata.json` as input format When using ea39a3de5705020d79ae89d6ab513b37fa662ce7 With Modulefile and metadata.json: Maybe success? It appears to work as specified, preferring the contents of the metadata.json and ignoring the Modulefile, but this is backwards incompatible as it previously would merge the two (eg, if there are dependencies declared in Modulefile but not in metadata.json, then the package will have no dependencies whereas before it WOULD have dependencies). This seems to be intended though. With Modulefile but no metadata.json: Success. It works as described. With no Modulefile but with metadata.json: Success. This was not previously supported so is not backwards-incompatible, and works as described. When using current master (90aad3fff7d270ef2683f486cdf999c003510cf0): With Modulefile and metadata.json: Same as above. With Modulefile but no metadata.json: Fail? The dependency list that appears in the repo Modulefile specifies two dependencies, but the package metadata.json appears like this: dependencies: [ #Puppet::ModuleTool::Dependency:0x007fc7c4218f48, #Puppet::ModuleTool::Dependency:0x007fc7c4218ac0 ] Perhaps this is on purpose, if master branch no longer supports Modulefile With no Modulefile but with metadata.json: Same as above. Other notes: I am seeing /Users/hunner/Documents/work/git/puppet/lib/puppet/version.rb:10: warning: already initialized constant PUPPETVERSION, but I see this on 3.5.1 as well. Add Comment
Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Hunter Haugen updated an issue Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format Change By: Hunter Haugen Assignee: HunterHaugen PietervandeBruggen 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-2471) Go/no-go meeting
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2471 Go/no-go meeting Change By: Rob Reynolds Getayes/noforthereleasefromdev,docs,product,qa,releng. Typicallythis This meeting willhappen isinformal,overchat,andusuallyhappens rightbeforepackagesarepushed.Keepinmindwe usually typically donotshipreleasesintheeveningandwedon'tshiponFridayifthereleaseisafinalrelease.Dependencies:*Smoketesting*HaveallJIRAticketsforthereleasebeenresolved? 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 Eric Sorenson - This appears to have failed review. Further this would break quite a few modules out there on the forge given that it ignores the old modulefile if there are both a modulefile and a metadata.json (some folks put different information in both). 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
Jira (FACT-472) Sync facter-2 code with master
Title: Message Title Kylo Ginsberg commented on an issue Re: Sync facter-2 code with master Eric Sorenson Andy Parker Joshua Cooper Peter Huene comments on this ticket and/or the approach in the linked PR? Add Comment Facter / FACT-472 Sync facter-2 code with master It seems like conversations have converged on: * master - zombie (and isn't updated) * make master carry the content of facter-2 (revert a lot and merge up?) * remove facter-2 And then only do CI on stable and master and cherry-pick/port from zombie as we go. [~adrien] [~peter.huene] please 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 Hunter Haugen commented on an issue Re: `puppet module build` should use `metadata.json` as input format I failed the review because based on the backwards-incompatible nature of this change, it 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 that exists in Modulefile but is different or non-existent in the metadata.json 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)
Jira (PDB-651) PR (962): Allow configurable url prefix - cprice404
Title: Message Title gepetto-bot commented on an issue Re: PR (962): Allow configurable url prefix - cprice404 pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/420/ Add Comment PuppetDB / PDB-651 PR (962): Allow configurable url prefix - cprice404 h2. Allow configurable url prefix * Author: Chris Price * Company: * Github ID: [cprice404|https://github.com/cprice404] * [Pull Request 962 Discussion|https://github.com/puppetlabs/puppetdb/pull/962] * [Pull Request 962 File Diff|https://github.com/puppetlabs/puppetdb/pull/962/files] h2. Pull Request Description This PR makes it possible... This message was sent by Atlassian JIRA (v6.1.4#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 (FACT-472) Sync facter-2 code with master
Title: Message Title Peter Huene commented on an issue Re: Sync facter-2 code with master The approach seems reasonable to me. We'll probably want to give everyone a good heads up before the switch since anyone (incorrectly) working out of master will need to probably reset their branch. Add Comment Facter / FACT-472 Sync facter-2 code with master It seems like conversations have converged on: * master - zombie (and isn't updated) * make master carry the content of facter-2 (revert a lot and merge up?) * remove facter-2 And then only do CI on stable and master and cherry-pick/port from zombie as we go. [~adrien] [~peter.huene] please 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 PR verifies on Docker OSX. Verifying under Hyper-V on Windows 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) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-472) Sync facter-2 code with master
Title: Message Title Adrien Thebo commented on an issue Re: Sync facter-2 code with master Doing `git diff facter-2..master|git apply -` doesn't mess with history and doesn't require anyone to reset or rebase, but it still leaves the history rather messy. The only way to clean up the history is to do an actual force push. Add Comment Facter / FACT-472 Sync facter-2 code with master It seems like conversations have converged on: * master - zombie (and isn't updated) * make master carry the content of facter-2 (revert a lot and merge up?) * remove facter-2 And then only do CI on stable and master and cherry-pick/port from zombie as we go. [~adrien] [~peter.huene] please 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-2318) Ruby open classes functionality breaks when used in ERB templates
Title: Message Title Felix Frank assigned an issue to Felix Frank Puppet / PUP-2318 Ruby open classes functionality breaks when used in ERB templates Change By: Felix Frank Assignee: FelixFrank 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-2318) Ruby open classes functionality breaks when used in ERB templates
Title: Message Title
Felix Frank commented on an issue
Re: Ruby open classes functionality breaks when used in ERB templates
I'm not sure about this one, but I do note that unlike the CLI, puppet will bind the template to a Puppet::Parser::TemplateWrapper instance (to enable access to puppet variables via @varname syntax etc.)
This likely leads to your code creating a nested Array class with a to_sudo method instead of adding to the array class.
And yay: I found a solution. Use this syntax
%
class ::Array
def to_sudo
...
Add Comment
Puppet / PUP-2318
Ruby open classes functionality breaks when used in ERB templates
{noformat} % class Array def to_sudo self.map{|i| /some/path/to/prepend/*/#{i} }.join(',') end end command_list1 = %w (command1.sh command2.sh command3.sh).to_sudo command_list2 = %w (command4.sh command5.sh command6.sh).to_sudo % Cmnd_Alias CMD1 = %= command_list1 % Cmnd_Alias CMD2 = %= command_list2 % {noformat} The ERB te...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2318) Ruby open classes functionality breaks when used in ERB templates
Title: Message Title Felix Frank updated an issue Puppet / PUP-2318 Ruby open classes functionality breaks when used in ERB templates Change By: Felix Frank Assignee: FelixFrank MikeReznik 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-2318) Ruby open classes functionality breaks when used in ERB templates
Title: Message Title Felix Frank assigned an issue to Felix Frank Puppet / PUP-2318 Ruby open classes functionality breaks when used in ERB templates Change By: Felix Frank Assignee: FelixFrank 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
Felix Frank commented on an issue
Re: unless_uid on user is completely broken wrt ranges
Hmm, so we'd re-implement the parsing of such values in this parameter's hooks, so that we can later throw it out again when Puppet has inherent support for it?
That seems rather wasteful to me, wouldn't it be preferable to forgo range support altogether until Puppet 4 makes them Just Work?
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.
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
The only thing required to make it work for 3x is to have RGen gem installed (required for future parser and 4.0), the fact that the parsing of the type specs is done with the type system is somewhat secondary.
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
Jira (PUP-1415) Mount resource error silently skipped at times when running as daemon
Title: Message Title Felix Frank assigned an issue to Felix Frank Puppet / PUP-1415 Mount resource error silently skipped at times when running as daemon Change By: Felix Frank Assignee: FelixFrank 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
Felix Frank commented on an issue
Re: Mount resource error silently skipped at times when running as daemon
I didn't feel up to build an NFS test rig, so I simplified like this (I'm on Debian, so no yumrepo either):
class mount_oddness_pup_1415 {
file { /tmp/mountpoint: ensure = directory }
package { openssh-server: ensure = present }
mount { /tmp/mountpoint:
ensure = mounted,
device = /tmp/mountme,
dump = 0,
pass = 0,
options = bind,rw,
require = [ File[/tmp/mountpoint], Package[openssh-server] ];
}
notify { i-am-a-yumrepo:
require = Mount[/tmp/mountpoint];
}
}
But with Puppet 3.5.1, I fail to reproduce the issue. The agent reliably yields the following
Notice: /Stage[main]/Mount_oddness_pup_1415/Mount[/tmp/mountpoint]/ensure: defined 'ensure' as 'mounted'
Error: /Stage[main]/Mount_oddness_pup_1415/Mount[/tmp/mountpoint]: Could not evaluate: Field 'device' is required
Notice: /Stage[main]/Mount_oddness_pup_1415/Notify[i-am-a-yumrepo]: Dependency Mount[/tmp/mountpoint] has failures: true
Warning: /Stage[main]/Mount_oddness_pup_1415/Notify[i-am-a-yumrepo]: Skipping because of failed dependencies
Notice: Finished catalog run in 0.53 seconds
Agent 2.7.23 behaves similar to what you describe:
notice: /Stage[main]/Mount_oddness_pup_1415/Mount[/tmp/mountpoint]/ensure: defined 'ensure' as 'mounted'
err: /Stage[main]/Mount_oddness_pup_1415/Mount[/tmp/mountpoint]: Could not evaluate: Field 'device' is required
notice: /Stage[main]/Mount_oddness_pup_1415/Notify[i-am-a-yumrepo]: Dependency Mount[/tmp/mountpoint] has failures: true
warning: /Stage[main]/Mount_oddness_pup_1415/Notify[i-am-a-yumrepo]: Skipping because of failed dependencies
notice: Finished catalog run in 0.28 seconds
time passes
notice: i-am-a-yumrepo
notice: /Stage[main]/Mount_oddness_pup_1415/Notify[i-am-a-yumrepo]/message: defined 'message' as 'i-am-a-yumrepo'
notice: Finished catalog run in 0.27 seconds
No mention of the mount resource during the second run.
So whatever causes this behavior, it is apparently fixed in the current stable version. In the meantime, you can work around it by fixing your fstab, yes?
I am inclined to close this ticket. Marco De Vitis, do you feel that this is justified?
Jira (PUP-1415) Mount resource error silently skipped at times when running as daemon
Title: Message Title Felix Frank assigned an issue to Felix Frank Puppet / PUP-1415 Mount resource error silently skipped at times when running as daemon Change By: Felix Frank Assignee: FelixFrank 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
Chris Portman commented on an issue
Re: unless_uid on user is completely broken wrt ranges
Wouldn't this whole piece of functionality be subject to the outcomes of the conversation around
PUP-2086
?
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
Jira (PUP-2324) Prepare long form release notes and short form release story
Title: Message Title
Eric Sorenson commented on an issue
Re: Prepare long form release notes and short form release story
Pretty sure this is done, I see 'em at: https://github.com/puppetlabs/puppet-docs/blob/22fe43903139c4f6ef42c9715b1bde949af80b03/source/puppet/3.6/reference/release_notes.markdown
I would just use that first paragraph for the release story: {blockquote} Puppet 3.6.0 is a backward-compatible features and fixes release in the Puppet 3 series. The biggest things in this release are: Improvements to directory environments, and the deprecation of config file environments Support for purging unmanaged ssh_authorized_key resources Support for installing gems for a custom provider as part of a Puppet run A configurable global logging level A configurable hashing algorithm (for FIPS compliance and other purposes) Improvements to the experimental future parser{blockquote}
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
Jira (FACT-189) LXC Container support
Title: Message Title Jeff McCune commented on an issue Re: LXC Container support Is this ticket for LXC support? If so that should be done. If it's for docker support, then that's what needs improving.-Jeff 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) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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 Verified under Hyper-V as well (though it was a bit more painful to get the boot2docker.iso rigged up properly in that environment [and given the disk space necessary to copy down docker layers]). is_virtual = true virtual = docker So yeah, this ticket was initially LXC, but given we don't have a great way to focus on just that part without Docker, I think we're just about good to merge this in as part of that work as well. 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) -- You received this message because you are subscribed to the
