Jira (PUP-3238) puppet reports end of file reached if server closes HTTP connection
Title: Message Title Adam Winberg commented on an issue Re: puppet reports end of file reached if server closes HTTP connection I understand the difficulties in providing a 'better' error message, so updated docs is good enough for me. Here's the trace: Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Error: Could not retrieve catalog from remote server: end of file reached /usr/lib/ruby/1.8/net/protocol.rb:135:in `sysread' /usr/lib/ruby/1.8/net/protocol.rb:135:in `rbuf_fill' /usr/lib/ruby/1.8/timeout.rb:67:in `timeout' /usr/lib/ruby/1.8/timeout.rb:101:in `timeout' /usr/lib/ruby/1.8/net/protocol.rb:134:in `rbuf_fill' /usr/lib/ruby/1.8/net/protocol.rb:116:in `readuntil' /usr/lib/ruby/1.8/net/protocol.rb:126:in `readline' /usr/lib/ruby/1.8/net/http.rb:2028:in `read_status_line' /usr/lib/ruby/1.8/net/http.rb:2017:in `read_new' /usr/lib/ruby/1.8/net/http.rb:1051:in `request' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/connection.rb:208:in `execute_request' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/connection.rb:176:in `request_with_redirects' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/connection.rb:219:in `with_connection' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/pool.rb:31:in `with_connection' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/connection.rb:218:in `with_connection' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/connection.rb:173:in `request_with_redirects' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/connection.rb:170:in `upto' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/connection.rb:170:in `request_with_redirects' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/connection.rb:87:in `post' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:83:in `send' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:83:in `http_request' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:66:in `http_post' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:94:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:190:in `do_request' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/request.rb:264:in `do_request' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:190:in `do_request' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:90:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:201:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:289:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:327:in `thinmark' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:326:in `thinmark' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:288:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:61:in `retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:104:in `prepare_and_retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:201:in `run_internal' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:132:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/context.rb:64:in `override' /usr/lib/ruby/site_ruby/1.8/puppet.rb:244:in `override' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:131:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:47:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:20:in `lock' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:47:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:117:in `with_client' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:44:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:82:in `run_in_fork' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:43:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:179:in `call' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:179:in `controlled_run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:41:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:356:in `onetime'
Jira (PUP-3243) There's no way the 'bsd' service provider will work on OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Puppet / PUP-3243 There's no way the 'bsd' service provider will work on OpenBSD Issue Type: Bug Assignee: Kylo Ginsberg Components: Types and Providers Created: 15/Sep/14 1:12 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse OpenBSD has it's own service provider and the 'bsd' service provider will certainly not work on OpenBSD. Therefore remove 'OpenBSD' from the 'confine' list. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-870) PR (140): (maint) Fix a linting issue (align =) - roidelapluie
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-870 PR (140): (maint) Fix a linting issue (align =) - roidelapluie Issue Type: Task Assignee: Unassigned Created: 15/Sep/14 4:40 AM Labels: github module Priority: Normal Reporter: gepetto-bot (maint) Fix a linting issue (align =) Author: Julien Pivotto Company: Inuits Github ID: roidelapluie Pull Request 140 Discussion Pull Request 140 File Diff Pull Request Description (webhooks-id: 6c82efa2be397510733916c9de18b328)
Jira (PUP-3241) A non productive construct may only be placed last in a block/sequence
Title: Message Title
Henrik Lindberg commented on an issue
Re: A non productive construct may only be placed last in a block/sequence
This is because you have a space between Class and the opening left bracket. Do this instead:
Class['::icinga::idoutils'] - Class['::icinga::web']
With the spaces, the interpretation is like this:
if( ... ) {
Class
['::icinga::idoutils'] - Class
['::icinga::web']
}
Which means, create a reference to all classes, then create a relationship between a string in an array and all classes, then create a literal array with a string.
The change in the future parser is intentional, so closing this as a Won't Fix.
Add Comment
Puppet / PUP-3241
A non productive construct may only be placed last in a block/sequence
Hi, I'm trying to migrate from 3.4 to 3.7.0. Most errors I've been running into have been fairly easy to solve. However, I keep running into one that seems to have no obvious solution, making me believe I may be running into a bug. I'm using the future parser. The error is: {quote}Error: Could not retrieve catalog from remote server: Error 400 on S...
Jira (PUP-3240) Remove ignoreimport setting
Title: Message Title Henrik Lindberg commented on an issue Re: Remove ignoreimport setting +1 to the deprecate in docs only. Add Comment Puppet / PUP-3240 Remove ignoreimport setting The `import` keyword is deprecated and slated for removal in 4.0. We should kill [the ignoreimport setting|https://docs.puppetlabs.com/references/latest/configuration.html#ignoreimport] while we're at it. As far as deprecating it goes, I figure it can be a docs-only deprecation. I'll add it to the list of deprecated 3.x features. This message was 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-2719) Windows mount provider (smb/cifs)
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2719 Windows mount provider (smb/cifs) Change By: Rob Reynolds Attachment: networkdrive.ps1 Attachment: netuse.cmd 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-3244) ENC returned environment ignored when using directory environments
Title: Message Title Chris Spence created an issue Puppet / PUP-3244 ENC returned environment ignored when using directory environments Issue Type: Bug Affects Versions: 3.7.0 Assignee: Unassigned Created: 15/Sep/14 8:04 AM Priority: Normal Reporter: Chris Spence Where a puppet agent is configured to use the default environment (production) and one relies on an ENC to assign the environment correctly (puppet 3.x where the ENC should win), when using directory environments to match an environment that doesn't exist, the default configured environment wins and the node is given a catalog from 'production' rather than failing (which is the behaviour I think I am expecting). Add Comment
Jira (PUP-620) (PR 2429) Add install_options to gem provider
Title: Message Title
Jason Ashby commented on an issue
Re: (PR 2429) Add install_options to gem provider
This doesn't seem to work very well for me for installing a gem. I'm on puppet 3.6.1, CentOS 6.5. I have the following:
package { 'fpm':
ensure = 'latest',
provider = 'gem',
install_options = ['--http-proxy http://webproxy.example.com:8080'],
}
$ sudo puppet agent -t
...snip...
Info: Applying configuration version '1410792649'
Error: Could not update: Execution of '/usr/bin/gem install --no-rdoc --no-ri fpm --http-proxy http://webproxy.example.com:8080' returned 1: ERROR: Could not find a valid gem 'fpm' (= 0) in any repository
ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)
Errno::ETIMEDOUT: Connection timed out - connect(2) (http://rubygems.org/latest_specs.4.8.gz)
Wrapped exception:
Execution of '/usr/bin/gem install --no-rdoc --no-ri fpm --http-proxy http://webproxy.example.com:8080' returned 1: ERROR: Could not find a valid gem 'fpm' (= 0) in any repository
ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)
Errno::ETIMEDOUT: Connection timed out - connect(2) (http://rubygems.org/latest_specs.4.8.gz)
Error: /Stage[main]/Fpm/Package[fpm]/ensure: change from absent to latest failed: Could not update: Execution of '/usr/bin/gem install --no-rdoc --no-ri fpm --http-proxy http://webproxy.example.com:8080' returned 1: ERROR: Could not find a valid gem 'fpm' (= 0) in any repository
ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)
Errno::ETIMEDOUT: Connection timed out - connect(2) (http://rubygems.org/latest_specs.4.8.gz)
However, running the 'gem install' it directly from the shell on the host works fine. I believe its something with the quotes being inserted into the command?
$ sudo /usr/bin/gem install --no-rdoc --no-ri fpm --http-proxy http://webproxy.example.com:8080
Fetching: json-1.8.1.gem (100%)
Building native extensions. This could take a while...
...
...
Fetching: cabin-0.6.1.gem (100%)
Fetching: backports-3.6.0.gem (100%)
Fetching: arr-pm-0.0.9.gem (100%)
Fetching: clamp-0.6.3.gem (100%)
Fetching: ffi-1.9.3.gem (100%)
Building native extensions. This could take a while...
...
.
Fetching: childprocess-0.5.3.gem (100%)
Fetching: fpm-1.2.0.gem (100%)
Successfully installed json-1.8.1
Successfully installed cabin-0.6.1
Successfully installed backports-3.6.0
Successfully installed arr-pm-0.0.9
Successfully installed clamp-0.6.3
Successfully installed ffi-1.9.3
Successfully installed childprocess-0.5.3
Successfully installed fpm-1.2.0
8 gems installed
Running it directly from the shell EXACTLY as puppet displayed it (with quotes) gives a different error than puppet spits out:
$ /usr/bin/gem install --no-rdoc --no-ri fpm --http-proxy http://webproxy.example.com:8080
ERROR: While executing gem ... (OptionParser::InvalidOption)
invalid
Jira (PUP-3238) puppet reports end of file reached if server closes HTTP connection
Title: Message Title Kylo Ginsberg commented on an issue Re: puppet reports end of file reached if server closes HTTP connection Josh Cooper according to the documentation for the post (et al) methods here: http://ruby-doc.org/stdlib-2.1.2/libdoc/net/http/rdoc/Net/HTTP.html This method never raises exception. So it does appear to mask errors on writes. Add Comment Puppet / PUP-3238 puppet reports end of file reached if server closes HTTP connection I have two dirname.rb functions in my code, one from stdlib and one in a different module I installed at an earlier stage. This has never been a problem, puppet has somehow chosen one of them and not complained about it. After upgrading to 3.7.0 on the clients, the puppetruns crashes with Error: Could not retrieve catalog from remote server: end of file... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google
Jira (PDB-869) PR (1081): (docs) Fixed contributor link - russell
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-869 PR (1081): (docs) Fixed contributor link - russell Change By: Kenneth Barber Sprint: 20140910to20140924 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-864) PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-864 PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes Change By: Kenneth Barber Sprint: 20140910to20140924 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-867) PR (1080): Changed our acceptance test setup to pin on facter 2.1.0 - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-867 PR (1080): Changed our acceptance test setup to pin on facter 2.1.0 - senior Change By: Kenneth Barber Sprint: 20140910to20140924 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-866) PR (139): Remove puppet_module_install in favor of copy_module_to - cyberious
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-866 PR (139): Remove puppet_module_install in favor of copy_module_to - cyberious Change By: Kenneth Barber Sprint: 20140910to20140924 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-870) PR (140): (maint) Fix a linting issue (align =) - roidelapluie
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-870 PR (140): (maint) Fix a linting issue (align =) - roidelapluie Change By: Kenneth Barber Sprint: 20140910to20140924 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-867) PR (1080): Changed our acceptance test setup to pin on facter 2.1.0 - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-867 PR (1080): Changed our acceptance test setup to pin on facter 2.1.0 - senior Change By: Kenneth Barber Story Points: 0 Fix Version/s: 3.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-854) PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug kbarber commented: @shrug is this still okay to merge, can we review its validity again? Its pretty old by now . Add Comment PuppetDB / PDB-854 PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug h2. (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 1072 Discussion|https://github.com/puppetlabs/puppetdb/pull/1072] * [Pull Request 1072 File Diff|https://github.com/puppetlabs/puppetdb/pull/1072/files] h2. Pull Reques... This message was 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
Jira (PDB-869) PR (1081): (docs) Fixed contributor link - russell
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-869 PR (1081): (docs) Fixed contributor link - russell Change By: Kenneth Barber Story Points: 0 Fix Version/s: 2.2.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 (PDB-862) PR (137): Fix some Puppet Lint errors - baurmatt
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-862 PR (137): Fix some Puppet Lint errors - baurmatt 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-869) PR (1081): (docs) Fixed contributor link - russell
Title: Message Title Kenneth Barber assigned an issue to Wyatt Alt PuppetDB / PDB-869 PR (1081): (docs) Fixed contributor link - russell Change By: Kenneth Barber Assignee: WyattAlt 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-870) PR (140): (maint) Fix a linting issue (align =) - roidelapluie
Title: Message Title gepetto-bot commented on an issue Re: PR (140): (maint) Fix a linting issue (align =) - roidelapluie Pull request (maint) Fix a linting issue (align =) has been closed. Add Comment PuppetDB / PDB-870 PR (140): (maint) Fix a linting issue (align =) - roidelapluie h2. (maint) Fix a linting issue (align =) * Author: Julien Pivotto * Company: Inuits * Github ID: [roidelapluie|https://github.com/roidelapluie] * [Pull Request 140 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/140] * [Pull Request 140 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/140/files] h2. Pull Reque... This message was 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-870) PR (140): (maint) Fix a linting issue (align =) - roidelapluie
Title: Message Title gepetto-bot commented on an issue Re: PR (140): (maint) Fix a linting issue (align =) - roidelapluie kbarber commented: This is duplicated in PR 137, I think that does a lot more work as well. Closing this one in favour of the other, and I'll try and nurse 137 in myself. Add Comment PuppetDB / PDB-870 PR (140): (maint) Fix a linting issue (align =) - roidelapluie h2. (maint) Fix a linting issue (align =) * Author: Julien Pivotto * Company: Inuits * Github ID: [roidelapluie|https://github.com/roidelapluie] * [Pull Request 140 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/140] * [Pull Request 140 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/140/files] h2. Pull Reque... This message was 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-864) PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes
Title: Message Title gepetto-bot commented on an issue Re: PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes kbarber commented: @robinbowes the tests seem to be failing on this one ^^ Add Comment PuppetDB / PDB-864 PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes h2. Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini * Author: Robin Bowes robin.bo...@yo61.com * Company: YO61 Ltd * Github ID: [robinbowes|https://github.com/robinbowes] * [Pull Request 138 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/138] * [Pull Request 138 File Diff|https://github.com/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.
Jira (PDB-871) Release Module Version 4.0.0
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-871 Release Module Version 4.0.0 Change By: Kenneth Barber Sprint: 20140910to20140924 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-871) Release Module Version 4.0.0
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-871 Release Module Version 4.0.0 Issue Type: Task Assignee: Unassigned Components: Module Created: 15/Sep/14 9:02 AM Fix Versions: module-4.0.0 Priority: Normal Reporter: Kenneth Barber We need to release a new version of 4.0.0. This ticket tracks that work. Add Comment
Jira (PDB-864) PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-864 PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes Change By: Kenneth Barber Story Points: 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-894) Too easy to hit CRL not yet valid for host (and not very informative)
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-894 Too easy to hit CRL not yet valid for host (and not very informative) Change By: Britt Gresham Assignee: BrittGresham 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-868) Potential race condition causing API error in db_resilience/postgres_restart.rb
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-868 Potential race condition causing API error in db_resilience/postgres_restart.rb Change By: Kenneth Barber Sprint: 20140910to20140924 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-743) PE testing Report retrieval failure due to 57P01 database disconnection
Title: Message Title Kenneth Barber commented on an issue Re: PE testing Report retrieval failure due to 57P01 database disconnection I'm going to close this in favour of PDB-868, and move that into the current sprint. Add Comment PuppetDB / PDB-743 PE testing Report retrieval failure due to 57P01 database disconnection We've seen this failure a number of times. Digging into the puppetdb log, I can see that PuppetDB drops a connection for an unknown reason. A couple of recent examples: * http://jenkins-enterprise.delivery.puppetlabs.net/view/PE%20Platform/view/Puppet/job/PE%20Puppet%20Acceptance%20Tests/111/label=modgud.delivery.puppetlabs.net,layout=64mcd-64a,platfo... This message was 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-866) PR (139): Remove puppet_module_install in favor of copy_module_to - cyberious
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-866 PR (139): Remove puppet_module_install in favor of copy_module_to - cyberious Change By: Kenneth Barber Story Points: 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-3245) Function calls no longer showing up in profile data
Title: Message Title Andy Parker created an issue Puppet / PUP-3245 Function calls no longer showing up in profile data Issue Type: Bug Affects Versions: 3.7.0 Assignee: Andy Parker Components: DSL Created: 15/Sep/14 9:49 AM Fix Versions: 4.0.0 Priority: Normal Reporter: Andy Parker When the profile setting is enabled, the catalog compilation tracks course grained profiling information. One piece of information tracked is how long it takes it to make function calls. Debug: PROFILE [apply] 2.3.1 Called notice: took 0.0001 seconds However, this information is missing when the future parser is in effect. Without this, there is a large gap in accounting for where time is spent when producing a catalog.
Jira (PDB-865) Puppet DB Migrations Do not Handle Bad Data
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-865 Puppet DB Migrations Do not Handle Bad Data Change By: Kenneth Barber Sprint: 20140910to20140924 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-865) Puppet DB Migrations Do not Handle Bad Data
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-865 Puppet DB Migrations Do not Handle Bad Data Change By: Kenneth Barber Affects Version/s: 2.2.0 Story Points: 2 Fix Version/s: 2.2.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 (PDB-865) Puppet DB Migrations Do not Handle Bad Data
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-865 Puppet DB Migrations Do not Handle Bad Data Change By: Wyatt Alt Assignee: WyattAlt 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-3238) puppet reports end of file reached if server closes HTTP connection
Title: Message Title Josh Cooper commented on an issue Re: puppet reports end of file reached if server closes HTTP connection https://github.com/ruby/ruby/blob/v1_8_7_374/lib/net/http.rb#L1548 Add Comment Puppet / PUP-3238 puppet reports end of file reached if server closes HTTP connection I have two dirname.rb functions in my code, one from stdlib and one in a different module I installed at an earlier stage. This has never been a problem, puppet has somehow chosen one of them and not complained about it. After upgrading to 3.7.0 on the clients, the puppetruns crashes with Error: Could not retrieve catalog from remote server: end of file... This message was 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-743) PE testing Report retrieval failure due to 57P01 database disconnection
Title: Message Title Matthaus Owens commented on an issue Re: PE testing Report retrieval failure due to 57P01 database disconnection Kenneth Barber Thanks for fixing it up. Add Comment PuppetDB / PDB-743 PE testing Report retrieval failure due to 57P01 database disconnection We've seen this failure a number of times. Digging into the puppetdb log, I can see that PuppetDB drops a connection for an unknown reason. A couple of recent examples: * http://jenkins-enterprise.delivery.puppetlabs.net/view/PE%20Platform/view/Puppet/job/PE%20Puppet%20Acceptance%20Tests/111/label=modgud.delivery.puppetlabs.net,layout=64mcd-64a,platfo... This message was 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-3231) Specifying --tags doesn't cause suitability check to be skipped for skipped resources
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3231 Specifying --tags doesn't cause suitability check to be skipped for skipped resources Change By: Eric Thompson Assignee: EricThompson 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-3222) Windows service provider references a non-existent class
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-3222 Windows service provider references a non-existent class 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 (HI-8) Hiera stable acceptance testing for Windows using VCloud
Title: Message Title Roger Ignazio assigned an issue to Roger Ignazio Hiera / HI-8 Hiera stable acceptance testing for Windows using VCloud Change By: Roger Ignazio Assignee: MichelleJohansen RogerIgnazio Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-9) Hiera stable acceptance testing for Solaris with Vcloud
Title: Message Title Roger Ignazio assigned an issue to Roger Ignazio Hiera / HI-9 Hiera stable acceptance testing for Solaris with Vcloud Change By: Roger Ignazio Assignee: RogerIgnazio Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-7) Hiera stable acceptance tests use dynamically provisioned vcloud templates.
Title: Message Title Roger Ignazio assigned an issue to Roger Ignazio Hiera / HI-7 Hiera stable acceptance tests use dynamically provisioned vcloud templates. Change By: Roger Ignazio Assignee: JoshuaPartlow RogerIgnazio 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-3128) (PR 3003) Pacman provider does not work on manjaro linux
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3128 (PR 3003) Pacman provider does not work on manjaro linux Change By: Charlie Sharpsteen Summary: (PR3003) Pacmanproviderdoesnotworkonmanjarolinux 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-3231) Specifying --tags doesn't cause suitability check to be skipped for skipped resources
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3231 Specifying --tags doesn't cause suitability check to be skipped for skipped resources Change By: Eric Thompson QA Contact: EricThompson QA Status: Reviewed 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-3222) Windows service provider references a non-existent class
Title: Message Title Rob Reynolds commented on an issue Re: Windows service provider references a non-existent class 3.7.0 PS C:\code\puppetlabs\puppet bundle exec puppet resource service bob ensure=stopped Debug: new listener called log Debug: registering instrumentation listener log Debug: new listener called performance Debug: registering instrumentation listener performance Debug: Runtime environment: puppet_version=3.7.0, ruby_version=1.9.3, run_mode=user, default_encoding=IBM437 Debug: Puppet::Type::Service::ProviderDaemontools: file /usr/bin/svc does not exist Debug: Puppet::Type::Service::ProviderDebian: file /usr/sbin/update-rc.d does not exist Debug: Puppet::Type::Service::ProviderGentoo: file /sbin/rc-update does not exist Debug: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl does not exist Debug: Puppet::Type::Service::ProviderOpenrc: file /bin/rc-status does not exist Debug: Puppet::Type::Service::ProviderRedhat: file /sbin/chkconfig does not exist Debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not exist Debug: Puppet::Type::Service::ProviderSystemd: file systemctl does not exist Debug: Puppet::Type::Service::ProviderUpstart: 0 confines (of 2) were true Debug: Loaded state in 0.03 seconds Error: /Service[bob]: Could not evaluate: uninitialized constant Win32::Service::Error Debug: Finishing transaction 35893752 Debug: Storing state Debug: Stored state in 0.03 seconds Error: Could not run: uninitialized constant Win32::Service::Error 3.7.1: PS C:\code\puppetlabs\puppet bundle exec puppet resource service bob ensure=stopped Debug: new listener called log Debug: registering instrumentation listener log Debug: new listener called performance Debug: registering instrumentation listener performance Debug: Runtime environment: puppet_version=3.7.1, ruby_version=1.9.3, run_mode=user, default_encoding=IBM437 Debug: Puppet::Type::Service::ProviderDaemontools: file /usr/bin/svc does not exist Debug: Puppet::Type::Service::ProviderDebian: file /usr/sbin/update-rc.d does not exist Debug: Puppet::Type::Service::ProviderGentoo: file /sbin/rc-update does not exist Debug: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl does not exist Debug: Puppet::Type::Service::ProviderOpenrc: file /bin/rc-status does not exist Debug: Puppet::Type::Service::ProviderRedhat: file /sbin/chkconfig does not exist Debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not exist Debug: Puppet::Type::Service::ProviderSystemd: file systemctl does not exist Debug: Puppet::Type::Service::ProviderUpstart: 0 confines (of 2) were true Debug: Loaded state in 0.02 seconds Error: /Service[bob]: Could not evaluate: Cannot get status of bob, error was: The specified service does not exist as an installed service. - OpenService: The specified service does not exist as an installed service. Wrapped exception: The specified service does not exist as an installed service. - OpenService: The specified service does not exist as an installed service. Debug: Finishing transaction 35922588 Debug: Storing state Debug: Stored state in 0.02 seconds Error: Could not run: Cannot get status of bob, error was: The specified service does not exist as an installed service. - OpenService: The specified service does not exist as an installed service. Wrapped exception: The specified service does not exist as an installed service. - OpenService: The specified service does not exist as an installed service.
Jira (PUP-3246) Puppet Module Tool Does Not Honor puppet.conf Settings unless they are in [main]
Title: Message Title Nick Walker created an issue Puppet / PUP-3246 Puppet Module Tool Does Not Honor puppet.conf Settings unless they are in [main] Issue Type: Bug Affects Versions: 3.6.2 Assignee: Unassigned Created: 15/Sep/14 10:41 AM Labels: support customer Priority: Normal Reporter: Nick Walker When setting the environmentpath setting and basemodulepath setting if you place them in the [master] section of puppet.conf then `puppet module list` will not work correctly. If you place both settings in [master] then you just get the default modulepath returned from `puppet module list`. If you place just basemodulepath in [main] and environmentpath in [master] then `puppet module list` will return the basemodulepath. If you place both settings in [main] then `puppet module list` works as expected.
Jira (PUP-3247) Win32::TaskScheduler#trigger_string doesn't work
Title: Message Title Josh Cooper created an issue Puppet / PUP-3247 Win32::TaskScheduler#trigger_string doesn't work Issue Type: Bug Affects Versions: 3.7.0 Assignee: Kylo Ginsberg Components: Client, Types and Providers Created: 15/Sep/14 10:43 AM Priority: Normal Reporter: Josh Cooper Our vendored `Win32::TaskScheduler#trigger_string` method doesn't define the `trigger` variable, so the reference to `trigger` on line 576 will cause the `#trigger` method to be invoked with 0 arguments, and that fails with: in `trigger': wrong number of arguments (0 for 1) (ArgumentError) This code path doesn't occur in Puppet, just when using puppet as a library.
Jira (PUP-3248) Update PMT tests for directory environment support
Title: Message Title John Duarte created an issue Puppet / PUP-3248 Update PMT tests for directory environment support Issue Type: Bug Assignee: John Duarte Components: PMT Created: 15/Sep/14 10:43 AM Priority: Normal Reporter: John Duarte Most of the PMT acceptance tests use the `host['distmoduledir']` variable which is not meaningful if the install is using directory environments. The acceptance suite needs to be updated to introspect the module path rather than use `host['distmoduledir']`. Add Comment This
Jira (PDB-869) PR (1081): (docs) Fixed contributor link - russell
Title: Message Title gepetto-bot commented on an issue Re: PR (1081): (docs) Fixed contributor link - russell wkalt commented: manually merged to stable Add Comment PuppetDB / PDB-869 PR (1081): (docs) Fixed contributor link - russell h2. (docs) Fixed contributor link * Author: Russell Sim russell@gmail.com * Company: * Github ID: [russell|https://github.com/russell] * [Pull Request 1081 Discussion|https://github.com/puppetlabs/puppetdb/pull/1081] * [Pull Request 1081 File Diff|https://github.com/puppetlabs/puppetdb/pull/1081/files] h2. Pull Request Description Upda... This message was 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-869) PR (1081): (docs) Fixed contributor link - russell
Title: Message Title gepetto-bot commented on an issue Re: PR (1081): (docs) Fixed contributor link - russell Pull request (docs) Fixed contributor link has been closed. Add Comment PuppetDB / PDB-869 PR (1081): (docs) Fixed contributor link - russell h2. (docs) Fixed contributor link * Author: Russell Sim russell@gmail.com * Company: * Github ID: [russell|https://github.com/russell] * [Pull Request 1081 Discussion|https://github.com/puppetlabs/puppetdb/pull/1081] * [Pull Request 1081 File Diff|https://github.com/puppetlabs/puppetdb/pull/1081/files] h2. Pull Request Description Upda... This message was 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-3203) Errors when using scheduled_task on windows
Title: Message Title
Josh Cooper commented on an issue
Re: Errors when using scheduled_task on windows
Thanks Sam Weston, The manifest above has a problem in that the `command` property uses double-quotes and single backslashes. This will cause puppet to interpret \P, etc as escape sequences, leading to errors like:
Warning: Unrecognised escape sequence '\P' in file C:/Users/sweston/puppettest.pp at line 2
Warning: Unrecognised escape sequence '\P' in file C:/Users/sweston/puppettest.pp at line 2
Warning: Unrecognised escape sequence '\j' in file C:/Users/sweston/puppettest.pp at line 2
See https://docs.puppetlabs.com/puppet/3.7/reference/lang_windows_file_paths.html#using-backslashes-in-double-quoted-strings for more info. You'll want to either use single quotes and single backslashes, or double quotes and double backslashes.
That said, I was not able to reproduce the problem you're seeing. From the stack trace, it looks like puppet is trying to delete a trigger (by index) that doesn't exist.
Can you try running Start Command Prompt with Puppet as an Administrator, save the following script to tasks.rb, execute it as ruby tasks.rb, and attach the result?
require 'puppet'
require 'puppet/util/windows'
require 'puppet/util/windows/taskscheduler'
require 'pp'
require 'ffi'
# workaround https://tickets.puppetlabs.com/browse/PUP-3247
class Win32::TaskScheduler
def trigger_string(index)
raise Error.new('No current task scheduler. ITaskScheduler is NULL.') if @pITS.nil?
raise Error.new('No currently active task. ITask is NULL.') if @pITask.nil?
raise TypeError unless index.is_a?(Numeric)
trigger =
FFI::MemoryPointer.new(:pointer) do |ptr|
@pITask.GetTriggerString(index, ptr)
ptr.read_com_memory_pointer do |str_ptr|
trigger = str_ptr.read_arbitrary_wide_string_up_to(256)
end
end
trigger
end
end
Win32::TaskScheduler.new.tasks.collect do |job_file|
task = Win32::TaskScheduler.new
task.activate(job_file)
puts Task'#{job_file}'
puts Command '#{task.application_name}'
puts Args'#{task.parameters}'
puts Working dir '#{task.working_directory}'
puts User'#{task.account_information}'
count = task.trigger_count
puts Triggers #{count}
task.trigger_count.times do |i|
begin
puts trigger #{i}
pp task.trigger(i)
rescue = detail
puts Failed to load trigger '#{task.trigger_string(i)}'
end
end
end
Add Comment
Jira (PUP-2559) Remove couchdb facts terminus and associated settings
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2559 Remove couchdb facts terminus and associated settings Change By: Adrien Thebo Sprint: 2014-09-17 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-2558) Remove instrumentation system
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2558 Remove instrumentation system Change By: Adrien Thebo Sprint: 2014-09-17 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-779) Remove deprecated process execution methods in util
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-779 Remove deprecated process execution methods in util 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-2558) Remove instrumentation system
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-2558 Remove instrumentation system Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2559) Remove couchdb facts terminus and associated settings
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2559 Remove couchdb facts terminus and associated settings 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-779) Remove deprecated process execution methods in util
Title: Message Title Andy Parker commented on an issue Re: Remove deprecated process execution methods in util Merged into master in 1b5423 Add Comment Puppet / PUP-779 Remove deprecated process execution methods in util All the deprecated process execution methods in util should be 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-2559) Remove couchdb facts terminus and associated settings
Title: Message Title Andy Parker commented on an issue Re: Remove couchdb facts terminus and associated settings Merged into master in 5ae5d0 Add Comment Puppet / PUP-2559 Remove couchdb facts terminus and associated settings This message was 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-2560) Remove inventory service on the master
Title: Message Title Adrien Thebo commented on an issue Re: Remove inventory service on the master Merged in 22f4e59. Add Comment Puppet / PUP-2560 Remove inventory service on the master We may have to keep around storing facts on the master in some form, but we need to get rid of all of the querying and saving from remote sources. This message was 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-3249) Remove queue service on the master
Title: Message Title Andy Parker created an issue Puppet / PUP-3249 Remove queue service on the master Issue Type: Task Assignee: Unassigned Created: 15/Sep/14 11:30 AM Fix Versions: 4.0.0 Priority: Normal Reporter: Andy Parker We may have to keep around storing facts on the master in some form, but we need to get rid of all of the querying and saving from remote sources. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (HI-285) Remove saucy from build_defaults.yaml
Title: Message Title Melissa Stone commented on an issue Re: Remove saucy from build_defaults.yaml William Hopper same question: since this has been merged in, is this done? Add Comment Hiera / HI-285 Remove saucy from build_defaults.yaml Saucy has already gone EOL on July 17, 2014. We will be removing the saucy repo from apt.puppetlabs.com on Monday, September 15, 2014. The build_defaults.yaml file needs to be updated before then. This message was 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-3048) Remove saucy from build_defaults.yaml
Title: Message Title Melissa Stone commented on an issue Re: Remove saucy from build_defaults.yaml William Hopper since this has been merged in, is this done? Add Comment Puppet / PUP-3048 Remove saucy from build_defaults.yaml Saucy has already gone EOL on July 17, 2014. We will be removing the saucy repo from apt.puppetlabs.com on Monday, September 15, 2014. The build_defaults.yaml file needs to be updated before then. This message was 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-3249) Remove queue service on the master
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3249 Remove queue service on the master Change By: Adrien Thebo Reporter: AndyParker 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 (PUP-3250) Remove secret_agent
Title: Message Title Andy Parker created an issue Puppet / PUP-3250 Remove secret_agent Issue Type: Task Assignee: Unassigned Created: 15/Sep/14 11:36 AM Fix Versions: 4.0.0 Priority: Normal Reporter: Andy Parker The secret_agent face was an experiment to create a new agent built up of individual small tools (upload facts, perform pluginsync, fetch catalog, etc.). However it was never worked on and has languished. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3174) After enabling directory environments the manifestdir setting is still required to be valid
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3174 After enabling directory environments the manifestdir setting is still required to be valid Change By: Eric Thompson QA Status: Reviewed 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-3249) Remove async_storeconfigs and queue service on the master
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3249 Remove async_storeconfigs and queue service on the master Change By: Adrien Thebo Summary: Remove async_storeconfigsand queueserviceonthemaster 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-3249) Remove async_storeconfigs and queue service on the master
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3249 Remove async_storeconfigs and queue service on the master Change By: Adrien Thebo Wemayhavetokeeparoundstoringfactsonthemasterinsomeform Thepuppetqueuedaemonandasync_storeconfigssettingwereaddedasamethodofspeedingupactiverecordstoreconfigs ,but sincePuppetDBisourprimarystoreconfigsimplementationandtheactiverecordstoreconfigsimplementationisgoingaway we needtogetridofallof canremove the querying queuingfunctionality and savingfromremotesources async_storeconfigs . 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-3249) Remove async_storeconfigs and queue service on the master
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3249 Remove async_storeconfigs and queue service on the master Change By: Adrien Thebo Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-285) Remove saucy from build_defaults.yaml
Title: Message Title William Hopper commented on an issue Re: Remove saucy from build_defaults.yaml Melissa Stone since the update is in both master and stable, as far as we know this is indeed done, as long as everything looks good wrt saucy being gone for you folks in release! Add Comment Hiera / HI-285 Remove saucy from build_defaults.yaml Saucy has already gone EOL on July 17, 2014. We will be removing the saucy repo from apt.puppetlabs.com on Monday, September 15, 2014. The build_defaults.yaml file needs to be updated before then. This message was 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-3048) Remove saucy from build_defaults.yaml
Title: Message Title William Hopper commented on an issue Re: Remove saucy from build_defaults.yaml Melissa Stone I did a quick check, and this update is in both master and stable, so as far as we know this is done (as long as everything looks good to you!) Add Comment Puppet / PUP-3048 Remove saucy from build_defaults.yaml Saucy has already gone EOL on July 17, 2014. We will be removing the saucy repo from apt.puppetlabs.com on Monday, September 15, 2014. The build_defaults.yaml file needs to be updated before then. This message was 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-3236) In Puppet Gemfile, allow env var to indicate Puppet is already on load path
Title: Message Title Nicholas Fagerlund commented on an issue Re: In Puppet Gemfile, allow env var to indicate Puppet is already on load path Christopher Price Is this change relevant to end-users or community developers, or only relevant to developers at the company? Like, what's the situation where you'd want to set PUPPET_LOADED? Add Comment Puppet / PUP-3236 In Puppet Gemfile, allow env var to indicate Puppet is already on load path We have a use case where the puppet source code is already available on the ruby load path before we run bundler, and need a way to conditionally exclude the `gem` line that references puppet. After some discussion, it sounds like an environment variable is the preferred way of doing this. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2558) Remove instrumentation system
Title: Message Title Josh Cooper commented on an issue Re: Remove instrumentation system Merged in 163e936 to be released in puppet 4. Add Comment Puppet / PUP-2558 Remove instrumentation 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 (PUP-1745) Could not autoload puppet/util/ tagmail reports
Title: Message Title
Josh Cooper commented on an issue
Re: Could not autoload puppet/util/ tagmail reports
The code that triggers this error has been removed in puppet 4, see PUP-2558 for more details.
Add Comment
Puppet / PUP-1745
Could not autoload puppet/util/ tagmail reports
I started getting tagmail e-mails of this nature yesterday. {quote} Fri Feb 21 03:19:09 -0800 2014 Puppet (err): Could not autoload puppet/util/instrumentation/listeners/performance: Class Performance is already defined in Puppet::Util::Instrumentation Fri Feb 21 03:19:09 -0800 2014 Puppet (err): Failed to apply catalog: Could not autoload puppet/uti...
This message was 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-3251) Man page for puppet is useless
Title: Message Title
Andy Parker created an issue
Puppet / PUP-3251
Man page for puppet is useless
Issue Type:
Improvement
Assignee:
Unassigned
Created:
15/Sep/14 12:12 PM
Fix Versions:
4.0.0
Priority:
Normal
Reporter:
Andy Parker
If a user installs puppet and then types man puppet they are presented with
PUPPET(8) Puppet manual PUPPET(8)
NAME
puppet
[1;31mError: Could not parse application options: invalid option: --help[0m
Puppet Labs, LLC September 2014 PUPPET(8)
This is caused by the following code in tasks/manpages.rake:
Unable to find source-code formatter for language: ruby. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
# Create LEGACY binary man pages (i.e. delete me for 2.8.0)
binary = bins + sbins
binary.each do |bin|
b = bin.gsub( /^s?bin\//, )
%x{RUBYLIB=./lib:$RUBYLIB #{bin} --help
Jira (PUP-3252) Regenerate man pages automatically
Title: Message Title Andy Parker created an issue Puppet / PUP-3252 Regenerate man pages automatically Issue Type: Improvement Assignee: Unassigned Created: 15/Sep/14 12:15 PM Fix Versions: 4.0.0 Priority: Normal Reporter: Andy Parker Currently it is up do the developers of puppet to remember when things have changed in areas that affect the man pages, run rake gen_manpages, and then commit the changed files. This has lead to the man pages being years out of date since either people forgot, or the entire team had not realized that this was needed. Since this is all generated data, the creation of the manpages needs to be, and can be, automated. As a build step (package creation?) the man pages must be generated and the result is not checked into source control. Add Comment
Jira (PUP-2559) Remove couchdb facts terminus and associated settings
Title: Message Title Andy Parker commented on an issue Re: Remove couchdb facts terminus and associated settings Updated man pages as part of this. They were over a year out of date! I've open PUP-3252 so that we don't hit that problem again. Add Comment Puppet / PUP-2559 Remove couchdb facts terminus and associated settings This message was 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-870) PR (140): (maint) Fix a linting issue (align =) - roidelapluie
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-870 PR (140): (maint) Fix a linting issue (align =) - roidelapluie Change By: Kenneth Barber Story Points: 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-653) Certain metrics aren't getting updated
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-653 Certain metrics aren't getting updated Change By: Kenneth Barber Sprint: 20140507to20140521,20140827to20140910 ,20140910to20140924 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-3191) Symlinks to missing targets cause a File Not Found error instead of a warning
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-3191 Symlinks to missing targets cause a File Not Found error instead of a warning Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3206) Is the code ready for release?
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3206 Is the code ready for release? Change By: Andy Parker Assignee: HaileeKenney 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-3205) Puppet 3.7.1 2014-09-15 Release
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3205 Puppet 3.7.1 2014-09-15 Release Change By: Andy Parker Assignee: HaileeKenney 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-3206) Is the code ready for release?
Title: Message Title Andy Parker commented on an issue Re: Is the code ready for release? All tests passed for commit 85c16b7d1a2179565608ed40959c9472e938adc9 Add Comment Puppet / PUP-3206 Is the code ready for release? 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 sp... This message was 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-3191) Symlinks to missing targets cause a File Not Found error instead of a warning
Title: Message Title Josh Cooper commented on an issue Re: Symlinks to missing targets cause a File Not Found error instead of a warning Verified in 85c16b7d, we warn when a bad link is encountered, but continue installing. Using the module as reported in puppet-users: $ bundle exec puppet module install gini-archive -v 0.2.0 Notice: Preparing to install into /Users/josh/.puppet/modules ... Notice: Created target directory /Users/josh/.puppet/modules Notice: Downloading from https://forgeapi.puppetlabs.com ... Warning: Symlinks in modules are unsupported. Please investigate symlink gini-archive-0.2.0/spec/fixtures/modules/archive/files-../../../../files. Warning: Symlinks in modules are unsupported. Please investigate symlink gini-archive-0.2.0/spec/fixtures/modules/archive/lib-../../../../lib. Warning: Symlinks in modules are unsupported. Please investigate symlink gini-archive-0.2.0/spec/fixtures/modules/archive/manifests-../../../../manifests. Warning: Symlinks in modules are unsupported. Please investigate symlink gini-archive-0.2.0/spec/fixtures/modules/archive/templates-../../../../templates. Notice: Installing -- do not interrupt ... /Users/josh/.puppet/modules └── gini-archive (v0.2.0) Add Comment Puppet / PUP-3191 Symlinks to missing targets cause a File Not Found error instead of a warning When trying to warn about symlinks in a module that is being unpacked for any reason, we use Pathname.realpath, which gives a File Not Found error when the target of the symlink doesn't exist.
Jira (PUP-3211) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3211 Is the Jira tidy-up done for this release and prepared for the next one? Change By: Andy Parker Assignee: HaileeKenney 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-3212) 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 Short form story can be as follows: Puppet 3.7.1 is a bug fix release in the Puppet 3.7 series. It fixes regressions introduced by Puppet 3.7.0, some issues with directory environments, and a few other bugs. Add Comment Puppet / PUP-3212 Prepare long form release notes and short form release story 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? This message was 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
Jira (PUP-3249) Remove async_storeconfigs and queue service on the master
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3249 Remove async_storeconfigs and queue service on the master Change By: Adrien Thebo Sprint: 2014-09-17 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-3214) Smoke test packages
Title: Message Title Melissa Stone commented on an issue Re: Smoke test packages packages available at http://builds.puppetlabs.lan/puppet/3.7.1/ Add Comment Puppet / PUP-3214 Smoke test packages 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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create package... This message was 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-3214) Smoke test packages
Title: Message Title Andy Parker commented on an issue Re: Smoke test packages Description contains what we are going to check. Add Comment Puppet / PUP-3214 Smoke test packages 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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create pa... This message was 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-3214) Smoke test packages
Title: Message Title Andy Parker updated an issue Puppet / PUP-3214 Smoke test packages Change By: Andy Parker Proceduremayvarybyprojectandpointinthereleasecycle.Askaround. Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc). LightertestingofZreleasesisacceptable. *AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask *Pingfolksonyourteamforhelpwithdifferentplatforms. *Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput. *IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested. *Whenallplatformspickedhavebeensmoketested,movethistickettodone. IMPORTANT:PleaseeditthedescriptionofthisticketandremoveExample:below.Edittheplatformstosmoketeston,andthesmoketestprocedure.Example: Smoketestplatforms: * picksomeplatformssuchas* RHEL 5/ 6/7 (RPMinstall) * CentOS5/6* Windows 2003/ 2008/2012 (MSIinstall) * Debian6/7/*Ubuntu10.04/12.04/14.04 Anything(Geminstall) Smoketestprocedure: *Start/stop/restartamasterwiththeinitscripts( onDebiantrythepassengermaster RHELonly ) *Start/stop/restartanagent (WindowsandRHEL) *Help/man (All) *Writeandrunsomemanifests Dependencies:*Tagandcreatepackages*ForWindowsMSIs-Pushtag (All) 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
Jira (PUP-3214) Smoke test packages
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3214 Smoke test packages Change By: Andy Parker Assignee: HaileeKenney 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-3214) Smoke test packages
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3214 Smoke test packages Change By: Josh Cooper Proceduremayvarybyprojectandpointinthereleasecycle.Askaround.Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc).LightertestingofZreleasesisacceptable.*AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask*Pingfolksonyourteamforhelpwithdifferentplatforms.*Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput.*IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested.*Whenallplatformspickedhavebeensmoketested,movethistickettodone.Smoketestplatforms:*RHEL6/7(RPMinstall)*Windows2008/2012(MSIinstall x86x64 )*Anything(Geminstall)Smoketestprocedure:*Start/stop/restartamasterwiththeinitscripts(RHELonly)*Start/stop/restartanagent(WindowsandRHEL)*Help/man(All)*Writeandrunsomemanifests(All) 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-3245) Function calls no longer showing up in profile data
Title: Message Title
Adrien Thebo commented on an issue
Re: Function calls no longer showing up in profile data
Merged in 5f076ac.
Add Comment
Puppet / PUP-3245
Function calls no longer showing up in profile data
When the {{profile}} setting is enabled, the catalog compilation tracks course grained profiling information. One piece of information tracked is how long it takes it to make function calls. {noformat} Debug: PROFILE [apply] 2.3.1 Called notice: took 0.0001 seconds {noformat} However, this information is missing when the future parser is in effect...
This message was 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-3214) Smoke test packages
Title: Message Title Rob Reynolds commented on an issue Re: Smoke test packages Windows 2008 / 2012 x86 Add Comment Puppet / PUP-3214 Smoke test packages 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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create pa... This message was 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-3214) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages RedHat 6/7. Add Comment Puppet / PUP-3214 Smoke test packages 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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create pa... This message was 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-3214) Smoke test packages
Title: Message Title Andy Parker commented on an issue Re: Smoke test packages Gem, non-windows. Add Comment Puppet / PUP-3214 Smoke test packages 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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create pa... This message was 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-3214) Smoke test packages
Title: Message Title Andy Parker updated an issue Puppet / PUP-3214 Smoke test packages Change By: Andy Parker Proceduremayvarybyprojectandpointinthereleasecycle.Askaround. Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc). LightertestingofZreleasesisacceptable. *AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask *Pingfolksonyourteamforhelpwithdifferentplatforms. *Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput. *IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested. *Whenallplatformspickedhavebeensmoketested,movethistickettodone. Smoketestplatforms: * RHEL6/7(RPMinstall) OSX *Windows2008/2012(MSIinstallx86x64) *Anything(Geminstall) Smoketestprocedure: *Start/stop/restart amasterwiththeinitscripts(RHELonly)*Start/stop/restart anagent(Windows andRHEL ) *Help/man(All) *Writeandrunsomemanifests(All) 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
Jira (PUP-3214) Smoke test packages
Title: Message Title Andy Parker commented on an issue Re: Smoke test packages Handing gems over to Joshua Partlow. I'm picking up OSX. Add Comment Puppet / PUP-3214 Smoke test packages 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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create package... This message was 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-3214) Smoke test packages
Title: Message Title
Andy Parker commented on an issue
Re: Smoke test packages
OSX package looks good.
Caveat: you have to install facter separately.
Commands run:
puppet help
man puppet
man puppet-apply
puppet apply -e '[1,2,3].each |$x| { notice($x) }' --parser future
Add Comment
Puppet / PUP-3214
Smoke test packages
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). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create package...
Jira (PUP-3214) Smoke test packages
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3214 Smoke test packages Change By: Joshua Partlow Proceduremayvarybyprojectandpointinthereleasecycle.Askaround.Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc).LightertestingofZreleasesisacceptable.*AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask*Pingfolksonyourteamforhelpwithdifferentplatforms.*Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput.*IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested.*Whenallplatformspickedhavebeensmoketested,movethistickettodone.Smoketestplatforms:* -- OSX -- *Windows2008/2012(MSIinstallx86x64)*--Anything(Geminstall):onrhel7--Smoketestprocedure:*Start/stop/restartanagent(Windows)*Help/man(All)*Writeandrunsomemanifests(All) 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-3214) Smoke test packages
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3214 Smoke test packages Change By: Joshua Partlow Proceduremayvarybyprojectandpointinthereleasecycle.Askaround. Ingeneralthisshouldhappenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc). LightertestingofZreleasesisacceptable. *AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask *Pingfolksonyourteamforhelpwithdifferentplatforms. *Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput. *IfyoursmoketestingincludesMSIs,youwillgenerallytestonotherplatformsfirstandwhenthatislookinggood,pingtheReleaseEngineerthatbuilttheotherpackagestomoveforwardwithMSIs(theyrequiretagstobepushed).Thisticketdoesn'tcloseuntilallchosenplatforms(includingMSIs)havebeentested. *Whenallplatformspickedhavebeensmoketested,movethistickettodone. Smoketestplatforms: *OSX *Windows2008/2012(MSIinstallx86x64) * -- Anything(Geminstall) :onrhel7-- Smoketestprocedure: *Start/stop/restartanagent(Windows) *Help/man(All) *Writeandrunsomemanifests(All) 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-3214) Smoke test packages
Title: Message Title
Joshua Partlow commented on an issue
Re: Smoke test packages
Gem on RHEL7 seems fine:
wget http://builds.puppetlabs.lan/puppet/3.7.1/artifacts/puppet-3.7.1.gem
gem install puppet-3.7.1.gem
puppet --version
puppet help
puppet apply -e notify { hello: }
puppet resource group puppet ensure=present
puppet resource user puppet ensure=present groups=puppet
puppet master --autosign true --certname localhost
puppet agent -t --server localhost
Add Comment
Puppet / PUP-3214
Smoke test packages
Procedure may vary by project
Jira (FACT-707) improve facter acceptance pre-suite for more platforms and git install
Title: Message Title Eric Thompson created an issue Facter / FACT-707 improve facter acceptance pre-suite for more platforms and git install Issue Type: Improvement Assignee: Eric Thompson Components: QA Created: 15/Sep/14 2:42 PM Priority: Normal Reporter: Eric Thompson git method doesn't work on some platforms. some platforms don't spin up at all. streamline for future CI work. having these all work helps QA spin up boxes for FR and writing tests. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
