Jira (PUP-1570) Puppet Agent hanging on applying configuration
Title: Message Title Naresh V commented on an issue Re: Puppet Agent hanging on applying configuration GDB backtrace if it's of any help: root@MIA01-DNS02:~# gdb -p 12508 GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://bugs.launchpad.net/gdb-linaro/. Attaching to process 12508 Reading symbols from /usr/bin/ruby1.8...Reading symbols from /usr/lib/debug/usr/bin/ruby1.8...done. done. Reading symbols from /usr/lib/libruby1.8.so.1.8...Reading symbols from /usr/lib/debug/usr/lib/libruby1.8.so.1.8.7...done. done. Loaded symbols for /usr/lib/libruby1.8.so.1.8 Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libc.so.6 Reading symbols from /lib/x86_64-linux-gnu/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fc999b98700 (LWP 13151)] Loaded symbols for /lib/x86_64-linux-gnu/libpthread.so.0 Reading symbols from /lib/x86_64-linux-gnu/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/librt.so.1 Reading symbols from /lib/x86_64-linux-gnu/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libdl.so.2 Reading symbols from /lib/x86_64-linux-gnu/libcrypt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libcrypt.so.1 Reading symbols from /lib/x86_64-linux-gnu/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libm.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /usr/lib/ruby/1.8/x86_64-linux/stringio.so...Reading symbols from /usr/lib/debug/usr/lib/ruby/1.8/x86_64-linux/stringio.so...done. done. Loaded symbols for /usr/lib/ruby/1.8/x86_64-linux/stringio.so Reading symbols from /usr/lib/ruby/1.8/x86_64-linux/syck.so...Reading symbols from /usr/lib/debug/usr/lib/ruby/1.8/x86_64-linux/syck.so...done. done. Loaded symbols for /usr/lib/ruby/1.8/x86_64-linux/syck.so Reading symbols from /usr/lib/ruby/1.8/x86_64-linux/openssl.so...Reading symbols from /usr/lib/debug/usr/lib/ruby/1.8/x86_64-linux/openssl.so...done. done. Loaded symbols for /usr/lib/ruby/1.8/x86_64-linux/openssl.so Reading symbols from /lib/x86_64-linux-gnu/libssl.so.1.0.0...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libssl.so.1.0.0 Reading symbols from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 Reading symbols from /lib/x86_64-linux-gnu/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libz.so.1 Reading symbols from /usr/lib/ruby/1.8/x86_64-linux/digest.so...Reading symbols from /usr/lib/debug/usr/lib/ruby/1.8/x86_64-linux/digest.so...done. done. Loaded symbols for /usr/lib/ruby/1.8/x86_64-linux/digest.so Reading symbols from /usr/lib/ruby/1.8/x86_64-linux/fcntl.so...Reading symbols from /usr/lib/debug/usr/lib/ruby/1.8/x86_64-linux/fcntl.so...done. done. Loaded symbols for /usr/lib/ruby/1.8/x86_64-linux/fcntl.so Reading symbols from /usr/lib/ruby/1.8/x86_64-linux/thread.so...Reading symbols from
Jira (PUP-1497) Missing version number in Windows packages displayname prevents update
Title: Message Title Dirk Heinrichs commented on an issue Re: Missing version number in Windows packages displayname prevents update Ah, OK. That's great. Thanks a lot. Add Comment Puppet / PUP-1497 Missing version number in Windows packages displayname prevents update Wanted to update the Puppet agent on Windows via Puppet. Unfortunately, the displayname, which is what the package resource looks after, of the Puppet package for Windows is just Puppet. So no matter what version I want to update to, the package resource is always satisfied if ANY version of puppet is already installed. Putting the version number into t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1927) Yum package Provider ignores Source parameter
Title: Message Title Christopher Barbour created an issue Puppet / PUP-1927 Yum package Provider ignores Source parameter Issue Type: Bug Affects Versions: 3.4.3 Assignee: Kylo Ginsberg Components: Types and Providers Created: 13/Mar/14 12:57 AM Priority: Normal Reporter: Christopher Barbour The YUM provider for the package type ignores the source parameter, and instead uses the name parameter for all package installation tasks. This behavior is somewhat inconsistent with other providers for this resource type. For example, with the RPM provider, the name parameter is compared against the packages instances list. If the defined package is not installed but should be, the provider will then download the package supplied by the source parameter and install it. With the yum provider, in the same conditions, puppet will kick off a yum installation of the named package, not the package supplied by the source parameter. This is okay if the desired package happens to be in a configured yum repository, but not so great otherwise. YUM fully supports installation from a source path; on older releases using the localinstall command, and on newer systems using the install command. This behavior is useful for multi-platform support and for module testing. In testing, I may wish to pass a explicit source for
Jira (PUP-1927) Yum Package Provider Ignores Source Parameter
Title: Message Title Christopher Barbour updated an issue Puppet / PUP-1927 Yum Package Provider Ignores Source Parameter Change By: Christopher Barbour Summary: Yum package Package Provider ignores Ignores Source parameter Parameter 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-1927) Yum Package Provider Ignores Source Parameter
Title: Message Title Christopher Barbour updated an issue Puppet / PUP-1927 Yum Package Provider Ignores Source Parameter Change By: Christopher Barbour Labels: wf001 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-1909) Priority setting also given to started processes/services
Title: Message Title
Steven Post commented on an issue
Re: Priority setting also given to started processes/services
Hi Joashua,
That server is managed using the 'service' type: service { 'httpd': ensure = $service_ensure, name = $service_name, enable = $service_enable, }
To be more precise, this is from the puppetlabs apache module. It would indeed be logical that execs get the same priority as the agent, but I think 'service' resources should not inherit that priority. I suppose there is a workaround by defining the priority inside the init script itself (or in this case, the /etc/sysconfig/httpd file), but in the bigger picture, this may not me feasible to add to all services. Since this is a RHEL 6 installation, I suspect that puppet is using the 'redhat' provider.
Perhaps the service type should invoke underlying infrastructure such as services using the default priority, but execs, package resources and other things that are really part of the puppet run should respect the priority of the config setting.
On a side note: how are puppet masters affected by this setting, since it only seems to work in the [main] section, and not in the [agent] section.
Add Comment
Puppet / PUP-1909
Priority setting also given to started processes/services
When setting the priority level in /etc/puppet.puppet.conf, this value also affects services that are started by the agent process. Example: We manage an apache service using puppet, without configuring the priority, the httpd process show a default priority of 20 (nice 0). When setting the priority to 'low' in the 'main' section, we see the puppet a...
Jira (PUP-1909) Priority setting also given to started processes/services
Title: Message Title Steven Post updated an issue Puppet / PUP-1909 Priority setting also given to started processes/services Change By: Steven Post Assignee: StevenPost 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-1928) puppet's idea of /etc/hosts management does not match real world use
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1928
puppet's idea of /etc/hosts management does not match real world use
Issue Type:
Bug
Assignee:
Unassigned
Created:
13/Mar/14 2:46 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Here is a valid extract from an /etc/hosts files on a RHEL box:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
Here is the code to make puppet add these entries:
host { 'localhost': ip = '127.0.0.1', host_aliases = [ 'localhost.localdomain', 'localhost4', 'localhost4.localdomain4', ], }
host { 'localhost': ip = '::1', host_aliases = [ 'localhost.localdomain', 'localhost6', 'localhost6.localdomain6', ], }
Notice the localhost part is the same in both cases. This causes a problem:
Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate definition: Host[localhost] is already defined in file /etc/puppet/modules/networking/manifests/init.pp
puppet-2.7.6-2.el6.noarch
Jira (PUP-1570) Puppet Agent hanging on applying configuration
Title: Message Title Naresh V commented on an issue Re: Puppet Agent hanging on applying configuration Hello again, I have more stacktraces and an additional info which correlates with the incidence of these hangs: network turbulence between puppet-master server and these nodes (they're on different continents). Two kinds of stracktraces, one something to with puppet/configurer.rb's apply_catalog(): https://gist.githubusercontent.com/nareshov/9527181/raw/7bbaafb6e272f46c9145bbff1a9530b3b3f79e46/sd1 And the other, net/http.rb's connect(): https://gist.githubusercontent.com/nareshov/9527191/raw/c3781e929ab4583cfa51452f04313e5ea1d71050/sd2 https://gist.githubusercontent.com/nareshov/9527197/raw/18c2fe8a1da3b16ddf4e04f53398aa037ea906be/sa9 https://gist.githubusercontent.com/nareshov/9527214/raw/c3f74367d3ca925ab3828a6d3a753e3e8e22966a/sa14 https://gist.githubusercontent.com/nareshov/9527224/raw/5521a4826c1da7dd3b21af2210a3483d391d742a/sa16 Thanks! Add Comment Puppet / PUP-1570 Puppet Agent hanging on applying configuration
Jira (PUP-1570) Puppet Agent hanging on applying configuration
Title: Message Title Naresh V commented on an issue Re: Puppet Agent hanging on applying configuration P.S. All the nodes in my previous comment run these versions: ii facter 1.7.4-1puppetlabs1 Ruby module for collecting simple facts about a host operating system ii hiera 1.3.1-1puppetlabs1 A simple pluggable Hierarchical Database. ii puppet 3.4.2-1puppetlabs1 Centralized configuration management - agent startup and compatibility scripts ii puppet-common 3.4.2-1puppetlabs1 Centralized configuration management Add Comment Puppet / PUP-1570 Puppet Agent hanging on applying configuration Probably worth noting, I run a setup with a puppetmaster and the agents connecting to that to get their manifests. My puppet agents get stuck applying configuration every once and awhile. For example: root 769 0.0 2.8 42616 29292 ? S Jan16 0:02 puppet agent: applying configurat root 28554 0.4 2.5 38244 25996 ? Ss... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1929) catalog failures should cause an exit status other than 0
Title: Message Title
Kenny Rasschaert updated an issue
Puppet / PUP-1929
catalog failures should cause an exit status other than 0
Change By:
Kenny Rasschaert
Whenusingthe--detailed-exitcodesoption,andpreformingthefollowing: pre {code} bundleexecpuppetapply--detailed-exitcodes-e'notify{foo:require=Notify[foo]}'/dev/mem:PermissiondeniedNotice:Compiledcatalogforblahinenvironmentproductionin0.04seconds/dev/mem:PermissiondeniedError:Couldnotapplycompletecatalog:Found1dependencycycle:(Notify[foo]=Notify[foo])Trythe'--graph'optionandopeningtheresulting'.dot'fileinOmniGraffleorGraphVizNotice:Finishedcatalogrunin0.02secondslhanel@Blah:~/git/puppet$echo$?0 /pre {code} puppetshouldexitwithanexitcodeOTHERthan0
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-1929) catalog failures should cause an exit status other than 0
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1929
catalog failures should cause an exit status other than 0
Issue Type:
New Feature
Assignee:
Unassigned
Created:
13/Mar/14 5:57 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
When using the --detailed-exitcodes option, and preforming the following:
pre bundle exec puppet apply --detailed-exitcodes -e 'notify { foo: require = Notify[foo] }
' /dev/mem: Permission denied Notice: Compiled catalog for blah in environment production in 0.04 seconds /dev/mem: Permission denied Error: Could not apply complete catalog: Found 1 dependency cycle: (Notify[foo] = Notify[foo]) Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz Notice: Finished catalog run in 0.02 seconds lhanel@Blah:~/git/puppet$ echo $? 0 /pre
puppet should exit with an exit code OTHER than 0
Add Comment
Jira (PUP-1158) PR (2061) Augeas provider warns on parse errors in other files handled by same lens
Title: Message Title Dominic Cleal commented on an issue Re: PR (2061) Augeas provider warns on parse errors in other files handled by same lens Zach, set the incl and lens parameters on your resource so it loads a specific file, instead of using the default mechanism. See http://docs.puppetlabs.com/guides/augeas.html#loading-generic-lenses-for-non-standard-files for more details. Add Comment Puppet / PUP-1158 PR (2061) Augeas provider warns on parse errors in other files handled by same lens Greetings, we are evaluating Puppet 3.0. At the moment we are getting errors from the augeas provider: Warning: Augeas[xx](provider=augeas): Loading failed for one or more files, see debug for /augeas//error output $ rpm -qa|grep puppet puppet-server-3.0.1-1.el6.noarch puppet-3.0.1-1.el6.noarch puppetdb-terminus-1.0.2-1.el6.noarch puppet-da... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PDB-511) PR (886): WIP - Doc changes for the environment support - senior
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-511 PR (886): WIP - Doc changes for the environment support - senior Issue Type: Task Assignee: Unassigned Created: 13/Mar/14 6:25 AM Labels: github Priority: Normal Reporter: gepetto-bot WIP - Doc changes for the environment support Author: Ryan Senior senior.r...@gmail.com Company: Github ID: senior Pull Request 886 Discussion Pull Request 886 File Diff Pull Request Description This change documents our new approach with version the wire formats (and commands). The real work in making these changes happen in the code still needs to be done, but I'm submitting this PR to facilitate discussion on the changes. (webhooks-id:
Jira (PDB-511) PR (886): WIP - Doc changes for the environment support - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (886): WIP - Doc changes for the environment support - senior senior commented: @kbarber @grimradical I made the wire format and command doc changes based on our discussion yesterday. Thoughts? Add Comment PuppetDB / PDB-511 PR (886): WIP - Doc changes for the environment support - senior h2. WIP - Doc changes for the environment support * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 886 Discussion|https://github.com/puppetlabs/puppetdb/pull/886] * [Pull Request 886 File Diff|https://github.com/puppetlabs/puppetdb/pull/886/files] h2. Pull Request Description ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more
Jira (PUP-1775) yumhelper.py: Not respecting the yum lock leads to RPM database corruption
Title: Message Title Dominic Cleal updated an issue Puppet / PUP-1775 yumhelper.py: Not respecting the yum lock leads to RPM database corruption While I don't intend to reproduce the corruption aspect, attached is an RPM I installed in parallel to running yumhelper/puppet to demonstrate that the lock was indeed being respected by the patch. The sleeper RPM will sleep for two minutes during %post, during which time yumhelper/puppet should also wait to acquire the lock. Change By: Dominic Cleal Attachment: sleeper-1-1.fc20.x86_64.rpm Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-380) Private ipaddress is used as ipaddress fact
Title: Message Title Tomas Barton created an issue Facter / FACT-380 Private ipaddress is used as ipaddress fact Issue Type: Bug Affects Versions: 1.7.4 Assignee: Adrien Thebo Components: Community Created: 13/Mar/14 7:11 AM Priority: Normal Reporter: Tomas Barton After adding docker interface all servers have the same :ipaddress fact. It seems that Facter is using the very first alphabetically sorted interface as the primary one. docker0 Link encap:Ethernet HWaddr 12:de:2d:b1:9d:14 inet addr:172.17.42.1 Bcast:0.0.0.0 Mask:255.255.0.0 eth0 Link encap:Ethernet HWaddr 00:25:90:d1:d1:7a inet addr: ... I think facter should ignore private addresses if there is an interface with a public ipaddress. https://github.com/deric/puppet-mesos/pull/1
Jira (PDB-510) ERROR: duplicate key value violates unique constraint catalogs_pkey
Title: Message Title Tyler Parsons commented on an issue Re: ERROR: duplicate key value violates unique constraint catalogs_pkey Kenneth, Here are the results of the commands you requested. postgres=# \c puppetdb psql (8.4.18) You are now connected to database puppetdb. puppetdb=# select relname from pg_class where relkind='S'; relname catalogs_transform_id_seq1 (1 row) puppetdb=# select * from catalogs_transform_id_seq1; sequence_name| last_value | start_value | increment_by | max_value | min_value | cache_value | log_cnt | is_cycled | is_called ++-+--+-+---+-+-+---+--- catalogs_transform_id_seq1 |574 | 1 |1 | 9223372036854775807 | 1 | 1 | 32 | f | t (1 row) puppetdb=# select id from catalogs order by id desc limit 1; id -- 1825 (1 row) puppetdb=# select count(id) from catalogs; count --- 1825 (1 row) Note: (show all) didn't seem to produce a result. postgres=# \x auto unrecognized boolean value; assuming on. Expanded display is on. postgres=# show all postgres-# \c puppetdb psql (8.4.18) You are now connected to database puppetdb. puppetdb-# \di+ List of relations -[ RECORD 1 ]- Schema | public Name| catalog_resources_pkey Type| index Owner | puppetdb Table | catalog_resources Size| 154 MB Description | -[ RECORD 2 ]- Schema | public Name| catalogs_certname_key Type| index Owner | puppetdb Table | catalogs Size| 168 kB Description | -[ RECORD 3 ]- Schema | public Name| catalogs_hash_key Type| index Owner | puppetdb Table | catalogs Size| 264 kB Description | -[ RECORD 4 ]- Schema | public Name| catalogs_pkey Type| index Owner | puppetdb Table | catalogs Size| 104 kB Description | -[ RECORD 5 ]- Schema | public Name| certname_facts_metadata_certname_key Type| index Owner | puppetdb Table | certname_facts_metadata Size| 184 kB Description | -[ RECORD 6 ]- Schema | public Name| certname_facts_metadata_pkey Type| index Owner | puppetdb Table | certname_facts_metadata Size| 296 kB Description | -[ RECORD 7 ]- Schema | public Name| certname_facts_pkey Type| index Owner | puppetdb Table | certname_facts Size| 35 MB Description | -[ RECORD 8 ]- Schema | public Name| certnames_pkey Type| index Owner | puppetdb Table | certnames Size| 144 kB Description | -[ RECORD 9 ]- Schema | public Name| constraint_resource_events_unique Type| index Owner | puppetdb Table | resource_events Size| 6200 kB Description | -[ RECORD 10 ]
Jira (PDB-511) PR (886): WIP - Doc changes for the environment support - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (886): WIP - Doc changes for the environment support - senior pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/286/ Add Comment PuppetDB / PDB-511 PR (886): WIP - Doc changes for the environment support - senior h2. WIP - Doc changes for the environment support * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 886 Discussion|https://github.com/puppetlabs/puppetdb/pull/886] * [Pull Request 886 File Diff|https://github.com/puppetlabs/puppetdb/pull/886/files] h2. Pull Request Description ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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-511) PR (886): WIP - Doc changes for the environment support - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (886): WIP - Doc changes for the environment support - senior pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/287/ Add Comment PuppetDB / PDB-511 PR (886): WIP - Doc changes for the environment support - senior h2. WIP - Doc changes for the environment support * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 886 Discussion|https://github.com/puppetlabs/puppetdb/pull/886] * [Pull Request 886 File Diff|https://github.com/puppetlabs/puppetdb/pull/886/files] h2. Pull Request Description ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (FACT-380) Private ipaddress is used as ipaddress fact
Title: Message Title Adrien Thebo assigned an issue to Unassigned Facter / FACT-380 Private ipaddress is used as ipaddress fact Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-380) Private ipaddress is used as ipaddress fact
Title: Message Title Adrien Thebo updated an issue Facter / FACT-380 Private ipaddress is used as ipaddress fact Change By: Adrien Thebo Component/s: Community 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-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title
Andy Parker commented on an issue
Re: Make modulepath, manifest, and config_version configurable per-environment
Joshua Partlow, we have a ticket to track getting performance up to snuff (PUP-1699), which we should do soon. Last time I took a stab at that it turned out to be much more difficult than I anticipated
Add Comment
Puppet / PUP-1596
Make modulepath, manifest, and config_version configurable per-environment
In order to make the new environment system fully usable, the default modulepath, manifest, and config_version needs to be overridable on a per-environment basis. This is possible in the current system with the environment stanzas and similar flexibility needs to be retained in the directory environments. Each environment should optionally have an {{en...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-1928) puppet's idea of /etc/hosts management does not match real world use
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: puppet's idea of /etc/hosts management does not match real world use
To recap discussion in the Redmine ticket: Hosts resources should be using the IP address as a unique key instead of host name. This will probably require breaking changes to the Hosts Type and Provider.
Add Comment
Puppet / PUP-1928
puppet's idea of /etc/hosts management does not match real world use
Here is a valid extract from an /etc/hosts files on a RHEL box: 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 Here is the code to make puppet add these entries: host { 'localhost': ip = '127.0.0.1', ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more
Jira (PDB-511) PR (886): WIP - Doc changes for the environment support - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (886): WIP - Doc changes for the environment support - senior pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/288/ Add Comment PuppetDB / PDB-511 PR (886): WIP - Doc changes for the environment support - senior h2. WIP - Doc changes for the environment support * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 886 Discussion|https://github.com/puppetlabs/puppetdb/pull/886] * [Pull Request 886 File Diff|https://github.com/puppetlabs/puppetdb/pull/886/files] h2. Pull Request Description ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-1885) File type ignore can't convert Fixnum into String
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Puppet / PUP-1885 File type ignore can't convert Fixnum into String Change By: Joshua Cooper Assignee: JoshuaCooper 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-876) upstart service operating system confine should include redhat and centos
Title: Message Title Tony Vu assigned an issue to Tony Vu Puppet / PUP-876 upstart service operating system confine should include redhat and centos Change By: Tony Vu Assignee: TonyVu 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-511) PR (886): WIP - Doc changes for the environment support - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-511 PR (886): WIP - Doc changes for the environment support - senior Change By: Kenneth Barber Fix Version/s: 2.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-511) PR (886): WIP - Doc changes for the environment support - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-511 PR (886): WIP - Doc changes for the environment support - senior Change By: Kenneth Barber Sprint: 20140312to20140326 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-508) Provide a first seen style field to nodes end-point to track when a node first submitted data
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-508 Provide a first seen style field to nodes end-point to track when a node first submitted data Change By: Kenneth Barber Summary: Provideafirstseenstylefieldtonodes end-point totrackwhenanodefirstsubmitteddata 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-508) Provide a first seen style field to nodes to track when a node first submitted data
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-508 Provide a first seen style field to nodes to track when a node first submitted data Change By: Kenneth Barber Summary: Adding Provide a firstseenstyle fieldto certnamestable nodestotrackwhenanodefirstsubmitteddata 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-508) Provide a first seen style field to nodes end-point to track when a node first submitted data
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-508 Provide a first seen style field to nodes end-point to track when a node first submitted data Change By: Kenneth Barber Component/s: Platform Affects Version/s: 1.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-508) Provide a first seen style field to nodes end-point to track when a node first submitted data
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-508 Provide a first seen style field to nodes end-point to track when a node first submitted data Change By: Kenneth Barber Story Points: 3 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-504) Pull out anonymization code into its own repo
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-504 Pull out anonymization code into its own repo Change By: Kenneth Barber Story Points: 8 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-196) SRV record support for terminus
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-196 SRV record support for terminus Change By: Kenneth Barber Story Points: 5 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-186) JVM heap size pointless without context
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-186 JVM heap size pointless without context Change By: Kenneth Barber Story Points: 3 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-1041) PR (2385) naginator not parsing blank parameters
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: PR (2385) naginator not parsing blank parameters
Notes for functional review: See Josh Cooper's testcase.
Add Comment
Puppet / PUP-1041
PR (2385) naginator not parsing blank parameters
Even though it wrote it, and is valid nagios syntax, The Naginator can not parse this: {code} define host { host_name gib-proxytest parents hostgroups gib use linux-server address 10.3.100.72 ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1860) Is there a bug targeted at the release for every commit?
Title: Message Title Henrik Lindberg commented on an issue Re: Is there a bug targeted at the release for every commit? Re-ran script for stable vs 3.4.3 and compared against initial report - everything now looks fine. Add Comment Puppet / PUP-1860 Is there a bug targeted at the release for every commit? This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1861) Is there a commit for every bug targeted at the release?
Title: Message Title Henrik Lindberg commented on an issue Re: Is there a commit for every bug targeted at the release? Re-ran script for stable vs 3.4.3 and compared against initial report - everything now looks fine. Add Comment Puppet / PUP-1861 Is there a commit for every bug 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 more options, visit https://groups.google.com/d/optout.
Jira (PUP-1101) static compiler does not filter exported resources from the catalog
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-1101 static compiler does not filter exported resources from the catalog Change By: Nicholas Fagerlund Fix Version/s: 3.5.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-1101) static compiler does not filter exported resources from the catalog
Title: Message Title
Nicholas Fagerlund commented on an issue
Re: static compiler does not filter exported resources from the catalog
Adding fix version since this is the bug of record for pup-609 and the commit is merged into 3.5.
Add Comment
Puppet / PUP-1101
static compiler does not filter exported resources from the catalog
Usually you'd want to not include resources a node is exporting in its catalog: pre node foo { @@notify{x: } } /pre should not have the notify. The static compiler though does not have a filter method in the node terminus and so the notify is present whenever the static compiler is used.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1570) Puppet Agent hanging on applying configuration
Title: Message Title Nicholas Jackson commented on an issue Re: Puppet Agent hanging on applying configuration Seeing this on CentOS 6 as well, the agents will sometimes get stuck applying the configuration during a network latency spike in a WAN. Similar straces. Add Comment Puppet / PUP-1570 Puppet Agent hanging on applying configuration Probably worth noting, I run a setup with a puppetmaster and the agents connecting to that to get their manifests. My puppet agents get stuck applying configuration every once and awhile. For example: root 769 0.0 2.8 42616 29292 ? S Jan16 0:02 puppet agent: applying configurat root 28554 0.4 2.5 38244 25996 ? Ss... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1585) PR (2342) cron resources with target specified generate duplicate entries
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: PR (2342) cron resources with target specified generate duplicate entries
Merged into master in 97c480b.
Notes for functional review:
Consider a test manifest:
cron { 'cron-test':
ensure = present,
month = '11',
command = '/bin/true',
target = 'vagrant',
}
Every time this manifest is applied, a duplicate entry will show up in the crontab of the Vagrant user. This duplication behavior should be addressed by commits e61ac84...0608933. Further fixes are covered by PUP-1624.
Add Comment
Puppet / PUP-1585
PR (2342) cron resources with target specified generate duplicate entries
The following resource results in duplicate cron entry added with each puppet run: {noformat} cron { 'bacula_vacuumdb': ensure = present, minute = '00', hour = '12', command = 'vacuumdb --analyze -U postgres bacula', target = 'postgres', }{noformat} Example of Cron: {noformat}~# crontab -l ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1897) EPP ignores code after parameter declaration
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1897 EPP ignores code after parameter declaration 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-1898) EPP - Error when trying to report argument error in inline_epp
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1898 EPP - Error when trying to report argument error in inline_epp 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 (PDB-511) PR (886): WIP - Doc changes for the environment support - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-511 PR (886): WIP - Doc changes for the environment support - senior Change By: Kenneth Barber Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-511) PR (886): WIP - Doc changes for the environment support - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-511 PR (886): WIP - Doc changes for the environment support - senior Change By: Kenneth Barber Story Points: 1 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1624) PR (2342) Cron handles crontab's equality of target and user strangely
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: PR (2342) Cron handles crontab's equality of target and user strangely
Merged into master in 97c480b.
Notes for functional review:
Consider a test manifest:
cron { 'cron-test':
ensure = present,
month = '11',
command = '/bin/true',
target = 'vagrant',
}
After commits e61ac84...0608933 to resolve PUP-1585, a new behavior will appear. Repeatedly applying the above manifest will cause the cron resource to flicker. The first application will create an entry in the vagrant crontab and the next will delete it while printing out the following message:
/Stage[main]//Cron[cron-test]/user: user changed 'vagrant' to 'root'
This behavior is addressed by commits 0608933...0187ee5.
Add Comment
Puppet / PUP-1624
PR (2342) Cron handles crontab's equality of target and user strangely
When managing the target property of a cronjob, the user property uses its default instead (which is the user running puppet). To the crontab provider, these are basically the same, and there is code to handle them equally. Through the mixtures of defaults and actual supplied values, though, bizarre behaviors come up: {code} # HEADER: This file was au...
Jira (PUP-1910) PR (231): Numerous changes to update testing gems. - apenney
Title: Message Title gepetto-bot commented on an issue Re: PR (231): Numerous changes to update testing gems. - apenney joshcooper commented: @apenney I'm getting a spec failure with 193: pre ~/work/modules/puppetlabs-stdlib (3.2.x) $ ruby --version ruby 1.9.3p392 (2013-02-22 revision 39386) [x86_64-darwin12.4.0] ~/work/modules/puppetlabs-stdlib (3.2.x) $ bundle exec rake spec ... 1) anchorrefresh propagates events through the anchored class Failure/Error: expect(resource.restarted).to eq(true) expected: true got: nil (compared using ==) ./.bundle/gems/ruby/1.9.1/gems/rspec-expectations-2.14.5/lib/rspec/expectations/fail_with.rb:32:in `fail_with' ./.bundle/gems/ruby/1.9.1/gems/rspec-expectations-2.14.5/lib/rspec/expectations/handler.rb:34:in `handle_matcher' ./.bundle/gems/ruby/1.9.1/gems/rspec-expectations-2.14.5/lib/rspec/expectations/expectation_target.rb:34:in `to' ./spec/classes/anchor_spec.rb:27:in `block (2 levels) in top (required)' ./.bundle/gems/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/example.rb:114:in `instance_eval' ./.bundle/gems/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/example.rb:114:in `block in run' ./.bundle/gems/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/example.rb:254:in `with_around_each_hooks' ./.bundle/gems/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/example.rb:111:in `run' ./.bundle/gems/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/example_group.rb:390:in `block in run_examples' ./.bundle/gems/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/example_group.rb:386:in `map' ./.bundle/gems/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/example_group.rb:386:in `run_examples' ./.bundle/gems/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/example_group.rb:371:in `run'
Jira (PUP-1895) EPP - Define parameters with % |$x| % instead of % ($x) %
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1895 EPP - Define parameters with % |$x| % instead of % ($x) % 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-1910) PR (231): Numerous changes to update testing gems. - apenney
Title: Message Title gepetto-bot commented on an issue Re: PR (231): Numerous changes to update testing gems. - apenney apenney commented: N! I thought I'd fixed this. Turns out the fix is to remove the entire test, because the def refresh stuff wasn't added until 4.x. Pushed a commit to fix. Add Comment Puppet / PUP-1910 PR (231): Numerous changes to update testing gems. - apenney h2. Numerous changes to update testing gems. * Author: Ashley Penney ashley.pen...@puppetlabs.com * Company: Puppetlabs * Github ID: [apenney|https://github.com/apenney] * [Pull Request 231 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/231] * [Pull Request 231 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/231/fil... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-1897) EPP ignores code after parameter declaration
Title: Message Title
Andy Parker commented on an issue
Re: EPP ignores code after parameter declaration
This seems to be catching the mistakes that I was making.
Add Comment
Puppet / PUP-1897
EPP ignores code after parameter declaration
If the parameter declaration for a single parameter in an EPP template is in a {{%= ... %}} snippet along with other code, the parameter declaration seems to be evaluated but all of the following code is ignored. If multiple parameters are specified then it ends up being a syntax error. Example {noformat} be puppet apply -e notice(inline_epp('%...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1895) EPP - Define parameters with % |$x| % instead of % ($x) %
Title: Message Title
Andy Parker commented on an issue
Re: EPP - Define parameters with % |$x| % instead of % ($x) %
The new syntax for parameters is in place. Unfortunately using %- ($x) -% doesn't produce an error because ($x) is a valid _expression_. I don't see any way around this without creating special EPP tags that create the parameter declaration (%|...|% maybe?). I think we should put this in front of people as is and see if we get any feedback.
Add Comment
Puppet / PUP-1895
EPP - Define parameters with % |$x| % instead of % ($x) %
Since the parameter syntax for lambdas is {noformat} |$x| { ... } {noformat} it seems like the parameters for EPP templates should follow the same style. That would mean that they are {noformat} inline_epp('% |$x| %', { x = 1 }) {noformat} instead of {noformat} inline_epp('% ($x) %', { x = 1 }) {noformat}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send
Jira (PUP-1930) PR (235): [WIP] Add some acceptance tests for functions. - apenney
Title: Message Title gepetto-bot created an issue Puppet / PUP-1930 PR (235): [WIP] Add some acceptance tests for functions. - apenney Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 13/Mar/14 11:23 AM Labels: github Priority: Normal Reporter: gepetto-bot [WIP] Add some acceptance tests for functions. Author: Ashley Penney ashley.pen...@puppetlabs.com Company: Puppetlabs Github ID: apenney Pull Request 235 Discussion Pull Request 235 File Diff Pull Request Description
Jira (PDB-510) ERROR: duplicate key value violates unique constraint catalogs_pkey
Title: Message Title
Kenneth Barber commented on an issue
Re: ERROR: duplicate key value violates unique constraint catalogs_pkey
Tyler Parsons so the problem is that your sequence is no longer representative of your id column ... its fallen out of sync (for some reason we're yet to determine).
The fix is something like the following:
root@pg1:~# su - postgres
postgres@pg1:~$ psql
Expanded display is used automatically.
Timing is on.
psql (9.3.3)
Type help for help.
puppetdb=# select id from catalogs order by id desc limit 1;
id
1825
(1 row)
Time: 0.338 ms
puppetdb=# select setval('catalogs_transform_id_seq1', 1825);
setval
1825
(1 row)
Time: 0.727 ms
puppetdb=# select * from catalogs_transform_id_seq1;
sequence_name| last_value | start_value | increment_by | max_value | min_value | cache_value | log_cnt | is_cycled | is_called
++-+--+-+---+-+-+---+---
catalogs_transform_id_seq1 | 1825 | 1 |1 | 9223372036854775807 | 1 | 1 | 0 | f | t
(1 row)
Can you test that and confirm it solves your issue?
As far as the root cause of this, I'm totally unsure about it. Our code doesn't randomly pick numbers it relies completely on the sequence on that column ... so I can't see how we would have done it ourselves.
Can you describe how you upgraded this? Did anything out of the ordinary occur? Did you have disk space issues perhaps during the upgrade or some other problem? Did you ever dump the data and restore it via postgresql tooling at any time?
A look into what the puppetdb.log looked like during the upgrade would be helpful.
Add Comment
PuppetDB / PDB-510
ERROR: duplicate key value violates unique constraint catalogs_pkey
Jira (PUP-1563) PR (2322) Module tool rechecks for conflicts for each installed module
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1563 PR (2322) Module tool rechecks for conflicts for each installed module 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 (FACT-184) Using 'ip addr' over ifconfig
Title: Message Title Adam Stephens commented on an issue Re: Using 'ip addr' over ifconfig This issue is bigger than the OP's description, as evidenced by the number of 'relates to' tickets from redmine. For me, the use of ifconfig leaves facter blind to iproute configured IP addresses. For others, including archlinux, there is no ifconfig on the default base install. Add Comment Facter / FACT-184 Using 'ip addr' over ifconfig pre # facter /usr/lib/ruby/site_ruby/1.8/facter/ipmess.rb:85: command not found: /sbin/ifconfig -a /usr/bin/facter:54: command not found: /sbin/ifconfig -a /usr/bin/facter:54: command not found: dnsdomainname /usr/bin/facter:54: command not found: domainname /usr/bin/facter:54: command not found: /sbin/ifconfig architecture = i386 domain = int... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-1743) Catalog retrieval problems
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Catalog retrieval problems
It is interesting that puppet agent -t appears to be working fine. However, given that pulling the catalog directly from the master using curl resulted in an incomplete transfer I'm not sure if this proves anything.
The master log output looks normal. One way of determining whether or not this is a network issue would be to set up a static file server on the master and see if you can pull files over to the agent using curl or if those transfers time out as well.
Add Comment
Puppet / PUP-1743
Catalog retrieval problems
Hello, we have some problems with puppet agent catalog retrieval. When I run puppet agent start -t i got error like: {noformat} Error: Could not retrieve catalog from remote server: Could not intern from text/pson: source did not contain any PSON! or Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': C...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs
Jira (PUP-1563) PR (2322) Module tool rechecks for conflicts for each installed module
Title: Message Title Andy Parker commented on an issue Re: PR (2322) Module tool rechecks for conflicts for each installed module Functionality does not seem to be affected and so I suppose that I just am not aware of the exact scenario that the problem shows up in. Add Comment Puppet / PUP-1563 PR (2322) Module tool rechecks for conflicts for each installed module resolve_install_conflicts causes a very long (edited from endless) recursion because the recursion loop is inside the modules_by_path iterator causing each module and dependency to be checked for conflict once for each module that is installed. With a tree of dependencies and mearly dozens of previously installed modules, this walk can take hours. Si... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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-1563) PR (2322) Module tool rechecks for conflicts for each installed module
Title: Message Title Andy Parker commented on an issue Re: PR (2322) Module tool rechecks for conflicts for each installed module I did not see any significant changes in module install time between puppet 3.4.3 and the code that included this change. I tried installing the puppetlabs-openstack modules (took ~2 minutes) as well as other modules (all into the same modulepath). However, I may not have been using the right combination or number of modules. Add Comment Puppet / PUP-1563 PR (2322) Module tool rechecks for conflicts for each installed module resolve_install_conflicts causes a very long (edited from endless) recursion because the recursion loop is inside the modules_by_path iterator causing each module and dependency to be checked for conflict once for each module that is installed. With a tree of dependencies and mearly dozens of previously installed modules, this walk can take hours. Si... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-1905) Multiple paths in --modulepath command line option not parsed
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1905 Multiple paths in --modulepath command line option not parsed 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-1905) Multiple paths in --modulepath command line option not parsed
Title: Message Title
Andy Parker commented on an issue
Re: Multiple paths in --modulepath command line option not parsed
Verified that modules installed into different directories and combined on the command line via --modulepath are respected both by puppet apply and puppet module list.
[root@localhost ~]# puppet apply -e 'include tomcat' --modulepath other:testing
Warning: Could not load fact file /root/other/puppi/lib/facter/windows_common_appdata.rb: no such file to load -- win32/dir
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Notice: Compiled catalog for localhost.corp.puppetlabs.net in environment production in 0.82 seconds
Notice: /Stage[main]/Tomcat/Package[tomcat]/ensure: created
Notice: /Stage[main]/Tomcat/File[tomcat.conf]/mode: mode changed '0664' to '0644'
Notice: /Stage[main]/Tomcat/Service[tomcat]/ensure: ensure changed 'stopped' to 'running'
Notice: Finished catalog run in 121.05 seconds
[root@localhost ~]# puppet apply -e 'include ntp' --modulepath other:testing
Warning: Could not load fact file /root/other/puppi/lib/facter/windows_common_appdata.rb: no such file to load -- win32/dir
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Notice: Compiled catalog for localhost.corp.puppetlabs.net in environment production in 0.77 seconds
Notice: /Stage[main]/Ntp::Config/File[/etc/ntp.conf]/content: content changed '{md5}23775267ed60eb3b50806d7aeaa2a0f1' to '{md5}af2c4d9dba34bb187ddfbf76bbf74815'
Notice: /Stage[main]/Ntp::Service/Service[ntp]/ensure: ensure changed 'stopped' to 'running'
Notice: Finished catalog run in 0.41 seconds
[root@localhost ~]# puppet module list --modulepath other:testing
/root/other
├── example42-puppi (v2.1.8)
└── example42-tomcat (v2.1.5)
/root/testing
├── 5ubZ3r0-httpd (v0.2.0)
├── dprince-qpid (v1.0.2)
├── duritong-sysctl (v0.0.2)
├── puppetlabs-apache (v0.11.0)
├── puppetlabs-apt (v1.4.2)
├── puppetlabs-ceilometer (v3.1.0)
├── puppetlabs-cinder (v3.0.0)
├── puppetlabs-concat (v1.0.2)
├── puppetlabs-firewall (v1.0.2)
├── puppetlabs-glance (v3.0.0)
├── puppetlabs-heat (v3.0.0)
├── puppetlabs-horizon (v3.0.1)
├── puppetlabs-inifile (v1.0.3)
├── puppetlabs-keystone (v3.0.0)
├── puppetlabs-mysql (v0.9.0)
Add Comment
Puppet / PUP-1905
Jira (PUP-1931) mount provider improvement when options property is not specified
Title: Message Title
Kylo Ginsberg created an issue
Puppet / PUP-1931
mount provider improvement when options property is not specified
Issue Type:
Improvement
Assignee:
Unassigned
Created:
13/Mar/14 12:24 PM
Fix Versions:
3.6.0
Priority:
Normal
Reporter:
Kylo Ginsberg
Not specifying options to a mount resource results in an opaque error message because it creates a bogus fstab without an options field.
E.g. I create a loop mountable ext2 filsystem on a CentOS 6 VM and verified that error message when not specifying options and that it goes away if you do specify (correct) options:
[root@qolo808yryboag9 puppet]# bundle exec puppet apply -e 'mount { /mnt/loop: ensure = mounted, fstype = ext2, device = /root/1m } '
Notice: Compiled catalog for qolo808yryboag9.delivery.puppetlabs.net in environment production in 0.07 seconds
Notice: /Stage[main]//Mount[/mnt/loop]/ensure: ensure changed 'unmounted' to 'mounted'
Error: /Stage[main]//Mount[/mnt/loop]: Could not evaluate: Execution of '/bin/mount /mnt/loop' returned 32: mount: /root/1m is not a block device (maybe try `-o loop'?)
Notice: Finished catalog run in 0.10 seconds
vs
[root@qolo808yryboag9 puppet]# bundle exec puppet apply -e 'mount { /mnt/loop: ensure = mounted, fstype = ext2, device = /root/1m, options =
Jira (PUP-1932) systemd reports transient (in-memory) services
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-1932 systemd reports transient (in-memory) services Issue Type: Improvement Assignee: Unassigned Created: 13/Mar/14 12:35 PM Priority: Normal Reporter: Kylo Ginsberg This CI triage note discusses an intermittent failure on rhel7 and fedora20 where the NetworkManager-dispatcher.service apparently disappears. I dug into this a little and it seems that the current systemd provider's `instances` implementation may need to be tweaked. I think that the answer may involve using `list-unit-files` rather than `list-units` but this will take some more investigation. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1885) File type ignore can't convert Fixnum into String
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1885 File type ignore can't convert Fixnum into String Change By: Joshua Cooper Affects Version/s: 3.4.3 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-1885) File type ignore can't convert Fixnum into String
Title: Message Title
Joshua Cooper commented on an issue
Re: File type ignore can't convert Fixnum into String
Verified broken in 3.4.3 and fixed in stable to be released in 3.5.0
Add Comment
Puppet / PUP-1885
File type ignore can't convert Fixnum into String
The following worked in Puppet 3.1 but throws errors in Puppet 3.4.x {noformat} file { $::epiphany::cluster_dir: ensure = directory, mode = $::epiphany::config_file_mode, owner = $::epiphany::config_file_owner, group = $::epiphany::config_file_group, require = Exec[${::epiphany::cluster_dir}/registry/...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-979) future parser fails to recognize hash as parameter in un-parenthesized calls
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Puppet / PUP-979 future parser fails to recognize hash as parameter in un-parenthesized calls Change By: Joshua Cooper Assignee: JoshuaCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-231) PR (608): Fix to Virtual Machine detection on Darwin - keeleysam
Title: Message Title gepetto-bot commented on an issue Re: PR (608): Fix to Virtual Machine detection on Darwin - keeleysam adrienthebo commented: This looks good, but before we merge this it would be good to do a little bit of bookkeeping. I can't recall if I already asked for this but it would be good to have a JIRA issue associated with this issue. In addition the commits should be squashed into a single commit, and the commit message should be updated to match the format in https://github.com/puppetlabs/facter/blob/master/CONTRIBUTING.md#making-changes . These changes make it easier to understand what was done here in case we need to review this later. Thanks Add Comment Facter / FACT-231 PR (608): Fix to Virtual Machine detection on Darwin - keeleysam h2. Fix to Virtual Machine detection on Darwin * Author: Samuel Keeley s...@keeleysam.com * Company: * Github ID: [keeleysam|https://github.com/keeleysam] * [Pull Request 608 Discussion|https://github.com/puppetlabs/facter/pull/608] * [Pull Request 608 File Diff|https://github.com/puppetlabs/facter/pull/608/files] h2. Pull Request Description ---... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-231) PR (608): Fix to Virtual Machine detection on Darwin - keeleysam
Title: Message Title gepetto-bot commented on an issue Re: PR (608): Fix to Virtual Machine detection on Darwin - keeleysam ahpook commented: @adrienthebo https://tickets.puppetlabs.com/browse/FACT-231 Add Comment Facter / FACT-231 PR (608): Fix to Virtual Machine detection on Darwin - keeleysam h2. Fix to Virtual Machine detection on Darwin * Author: Samuel Keeley s...@keeleysam.com * Company: * Github ID: [keeleysam|https://github.com/keeleysam] * [Pull Request 608 Discussion|https://github.com/puppetlabs/facter/pull/608] * [Pull Request 608 File Diff|https://github.com/puppetlabs/facter/pull/608/files] h2. Pull Request Description ---... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1933) Re-work or remove the Cron Type target property
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-1933 Re-work or remove the Cron Type target property Issue Type: Improvement Assignee: Kylo Ginsberg Components: Types and Providers Created: 13/Mar/14 1:05 PM Fix Versions: 4.x Labels: type_cron Priority: Normal Reporter: Charlie Sharpsteen Like other Types with core Providers implemented by ParsedFile, Cron has a target property. For most ParsedFile providers, target is used to specify which filesystem entry the resource is stored in. However, Cron is a special snowflake because the provider does not directly interface with the filesystem. Instead, all actions are proxied through system calls to crontab -u user command and the cron type also has a user property that specifies which username gets passed into the command. So, we have an awkward situation where both the user and target properties specify which crontab to manipulate. As demonstrated by PUP-1585, a lot of complicated logic is required to ensure these two properties stay perfectly in sync. Testing is messy as there are a lot of edge cases.
Jira (PUP-1345) Incoherent error message on ERB syntax error
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-1345
Incoherent error message on ERB syntax error
Change By:
Eric Sorenson
IhavehadthefollowingERBtemplatewithasyntaxerroronthefirstline(missing%forpasswordvariable): {code} test-z%=user%||exportUSER_PIECE=--username%=user%--password%=passwordifsvninfo%=destination%2/dev/null;thensvn-q--non-interactive$USER_PIECEup%=destination%;elsemkdir-p%=destination%;svn-q--non-interactive$USER_PIECEco%=source%%=destination%;fi; {code} Thisisthepuppetoutput: {code} bash-3.2#puppetd--test..info:Loadingfactsinrm_privsinfo:Loadingfactsinenv_varserr:Couldnotretrievecatalogfromremoteserver:wrongheaderlineformatwarning:Notusingcacheonfailedcatalogerr:Couldnotretrievecatalog;skippingrun {code} IthinkitwouldbehelpfultohaveERBcompilationerrorsmorecoherenttomakedebuggingeasier.
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-1895) EPP - Define parameters with % |$x| % instead of % ($x) %
Title: Message Title
Henrik Lindberg commented on an issue
Re: EPP - Define parameters with % |$x| % instead of % ($x) %
The remaining issue is actually validating no-ops. i.e. if a ($x) is followed by a render/string/_expression_ the ($x) (or any similar _expression_ such as just a literal, addition etc, becomes a no-op and can be flagged as at least a warning. (This kind of validation is however both somewhat slow and not perfectly accurate since we have to treat all function calls as having side effects).
The no-ops validation is a general issue, not just for EPP.
The syntax % |$x, $y| % allows for the setup to continue after the last pipe. If %| and |% becomes EPP tokens, that will not work, and users have to have to opening set of tags to do the same. e.g.
%-|$x,$y| $product = $x * $y -%
...
vs.
%| $x,$y |%%-$product = $x * $y -%
...
So, yeah - I don't know, you would have to know how it works in both/all cases since there is no precedent in ERB.
What would make the most sense from a Puppet Programming Language perspective would be that the entire file was a lambda and that it started with a brace, and ended with a brace - but that is just painful (i.e. having to always end the file with a right brace). e.g.
%-|$x,$y| { $product = $x * $y -%
...
%- } -%
Add Comment
Puppet / PUP-1895
EPP - Define parameters with % |$x| % instead of % ($x) %
Jira (PUP-979) future parser fails to recognize hash as parameter in un-parenthesized calls
Title: Message Title
Joshua Cooper commented on an issue
Re: future parser fails to recognize hash as parameter in un-parenthesized calls
Verified in puppet/stable
Add Comment
Puppet / PUP-979
future parser fails to recognize hash as parameter in un-parenthesized calls
If an attempt is made to evaluate this {code} notice {a = 10} {code} The result is the error message: ll resource specifications require names This is because it was once allowed to have resource initialization without a name, and the parser issues a deprecation error for this. This is somewhat tricky to work around as the grammar does not ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1799) New Function API
Title: Message Title Henrik Lindberg commented on an issue Re: New Function API Yes, I started on something before the trip to Portland, and continued on it during the trip home. I have a pretty good idea about how I think it should work. There are a couple of aspects of it that I have not yet considered (injection, varargs). What I am thinking is that there could be a first cut of the API and then move on to the loader side. Add Comment Puppet / PUP-1799 New Function API This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1370) when init scripts have been ported to upstart puppet does not detect service that are not working
Title: Message Title
Adrien Thebo commented on an issue
Re: when init scripts have been ported to upstart puppet does not detect service that are not working
I stumbled across this issue while looking at the behavior in https://github.com/puppetlabs/puppet/pull/2276, and I don't know if this is still an issue:
root@ubuntu-server-10044-x64-vbox4210-nocm:~# apt-cache policy mysql-server
mysql-server:
Installed: 5.1.73-0ubuntu0.10.04.1
Candidate: 5.1.73-0ubuntu0.10.04.1
Version table:
*** 5.1.73-0ubuntu0.10.04.1 0
500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages
100 /var/lib/dpkg/status
5.1.41-3ubuntu12.10 0
500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
5.1.41-3ubuntu12.7 0
500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages
5.1.41-3ubuntu12 0
500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
root@ubuntu-server-10044-x64-vbox4210-nocm:~# /etc/init.d/mysql status
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service mysql status
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the status(8) utility, e.g. status mysql
mysql stop/waiting
root@ubuntu-server-10044-x64-vbox4210-nocm:~# echo $?
0
root@ubuntu-server-10044-x64-vbox4210-nocm:~# service mysql status
mysql stop/waiting
root@ubuntu-server-10044-x64-vbox4210-nocm:~# echo $?
0
root@ubuntu-server-10044-x64-vbox4210-nocm:~# puppet resource service mysql
service { 'mysql':
ensure = 'stopped',
enable = 'true',
}
root@ubuntu-server-10044-x64-vbox4210-nocm:~# service mysql start
mysql start/running, process 3616
root@ubuntu-server-10044-x64-vbox4210-nocm:~# service mysql status
mysql start/running, process 3616
root@ubuntu-server-10044-x64-vbox4210-nocm:~# puppet resource service mysql
service { 'mysql':
ensure = 'running',
enable = 'true',
}
Upstart does have a compatibility layer with legacy init scripts, as demonstrated with the following:
root@ubuntu-server-10044-x64-vbox4210-nocm:~# service ntp start
* Starting NTP server ntpd[ OK ]
root@ubuntu-server-10044-x64-vbox4210-nocm:~# cat ntp.pp
service { 'ntp':
ensure = stopped,
provider = upstart,
}
root@ubuntu-server-10044-x64-vbox4210-nocm:~# puppet apply ntp.pp
Notice: Compiled catalog for ubuntu-server-10044-x64-vbox4210-nocm.vm in environment production in 0.04 seconds
Notice: /Stage[main]/Main/Service[ntp]/ensure: ensure changed 'running' to 'stopped'
Notice: Finished catalog run in 0.04 seconds
While I don't know if this is still broken (and given the above it looks to be resolved) I think that removing the defaultfor statement on
Jira (PUP-748) PR (2067): Zypper provider install options - darix
Title: Message Title
gepetto-bot commented on an issue
Re: PR (2067): Zypper provider install options - darix
peterhuene commented:
I was able to reproduce on SLES 11: `puppet apply -e 'package { vim: ensure = present, install_options = { --from = 1 }
}'` fails with `Unknown option '--from '1''`. I'm not quite sure yet why this is confusing zypper, as if I run the same command directly, zypper parses the option correctly.
I've verified that this fix (when itself is fixed, since `v` is always `nil` in the requested change) does cause zypper to properly respect install_options. I'll get this cleaned up and merged in.
Add Comment
Puppet / PUP-748
PR (2067): Zypper provider install options - darix
h2. Zypper provider install options * Author: * Company: * Github ID: [darix|https://github.com/darix] * [Pull Request 2067 Discussion|https://github.com/puppetlabs/puppet/pull/2067] * [Pull Request 2067 File Diff|https://github.com/puppetlabs/puppet/pull/2067/files] h2. Pull Request Description The old code would convert install_option...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1282) puppet gem does not include platform specific gem dependencies
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-1282 puppet gem does not include platform specific gem dependencies Change By: Joshua Cooper Assignee: JoshuaCooper 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-759) Remove ca_days from --genconfig output
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-759 Remove ca_days from --genconfig output Change By: Joshua Cooper Assignee: JoshuaCooper 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-1284) win32-security gem doesn't handle 'Authenticated Users' correctly
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-1284 win32-security gem doesn't handle 'Authenticated Users' correctly Change By: Joshua Cooper Assignee: JoshuaCooper 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-1370) when init scripts have been ported to upstart puppet does not detect service that are not working
Title: Message Title Adrien Thebo commented on an issue Re: when init scripts have been ported to upstart puppet does not detect service that are not working The upstart provider was set as the default on Ubuntu in commit dc3bb9fb2546eba61d57f61994e453cd8780e5d1, which was released in 2.7.14. Since upstart can correctly handle this service and will be the default in Ubuntu I think this is solved. I'm going to mark this as needs information so that we can get additional verification of this. If this doesn't see any comments in a month or so I think we can assume this is resolved and close it. Add Comment Puppet / PUP-1370 when init scripts have been ported to upstart puppet does not detect service that are not working I do not believe that this is a regresson and it was observed on 2.7.12 when a init script has been disabled, the following message is printed to stdout: pre root@db:~# /etc/init.d/mysql status Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service mysql status Since the script you are attempting to i... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1387) CA generates subjectKeyIdentifier from issuer cert instead of cert itself
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-1387 CA generates subjectKeyIdentifier from issuer cert instead of cert itself Change By: Joshua Cooper Assignee: JoshuaCooper 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-1421) appdmg prematurely filters for sources ending in .dmg
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-1421 appdmg prematurely filters for sources ending in .dmg Change By: Joshua Cooper Assignee: JoshuaCooper 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-797) PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-797 PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez Change By: Joshua Cooper Assignee: JoshuaCooper 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-1934) PR (2432): Calling 'ruby' in Windows Tests Fails for PE - colinPL
Title: Message Title gepetto-bot created an issue Puppet / PUP-1934 PR (2432): Calling 'ruby' in Windows Tests Fails for PE - colinPL Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 13/Mar/14 1:34 PM Labels: github Priority: Normal Reporter: gepetto-bot Calling 'ruby' in Windows Tests Fails for PE Author: Colin Company: Github ID: colinPL Pull Request 2432 Discussion Pull Request 2432 File Diff Pull Request Description The 'ruby' executable does not exist on a PE installation. Instead,
Jira (PUP-1935) puppetd ignores local ca.pem when connecting to master for the first time
Title: Message Title redmine.exporter created an issue Puppet / PUP-1935 puppetd ignores local ca.pem when connecting to master for the first time Issue Type: Bug Assignee: Unassigned Created: 13/Mar/14 1:37 PM Labels: redmine Priority: Normal Reporter: redmine.exporter Hi, I have a clean machine, with only puppet.conf configured (using --genconfig) and /etc/puppet/ssl/certs/ca.pem. I now run for the first time puppetd and connect to a server that has a different CA. I believe the expected behavior should be that puppetd will abort the connection because it connects to an unauthorized server. Instead, puppetd continues to communicate with the unauthorized master and generates a new certificate request. Unless I'm mistaken, this scenario could lead to a security breach: if an attacker gains control over the DNS, it can redirect new machines to its own malicious master. The master will make the node install a rootkit for example. Afterwards the attacker will redirect the DNS back to the original master. The node will then retrieve from the original (unsuspecting) master sensitive information, information that now the attacker can access. I'm running puppet version 2.6.2. Thanks, Tal
Jira (PUP-1679) Eradicate usage of FileUtils / File .chmod and move to the FileSystem abstraction
Title: Message Title Eric Sorenson commented on an issue Re: Eradicate usage of FileUtils / File .chmod and move to the FileSystem abstraction Not only started there, but completed as well--just cleaning up the book-keeping for it. Add Comment Puppet / PUP-1679 Eradicate usage of FileUtils / File .chmod and move to the FileSystem abstraction The built-in Ruby classes FileUtils.chmod and File.chmod do not behave correctly under Windows. We do however have a nice method Puppet::Util::Windows::Security.set_mode(mode, path) that does it's best job to simulate a POSIX mode and roundtrip it properly. All call sites that use the Ruby methods should be updated to use a new Puppet::FileSystem.ch... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-876) upstart service operating system confine should include redhat and centos
Title: Message Title Adrien Thebo commented on an issue Re: upstart service operating system confine should include redhat and centos Before I launch in to this issue, how important is the fallback behavior from redhat to upstart? I don't want us to spend a bunch of time on this if it's a small oddity that we took as a critical problem. In other cases where a single system has multiple init providers, there's usually an inheritance relationship between the different init providers. This is how the upstart provider works on Ubuntu. When the upstart provider is running it determines if the given service is an upstart service or if it's a sysvinit script; if it's the latter then the upstart provider can just call `super` to get the parent behavior. This is how the upstart provider can fall back to the debian service provider. On Redhat this is much messier because we are using the same upstart provider but we can't fall back in the same manner. To make the same trick work the upstart provider would have to inherit from the Redhat provider, which isn't the case today. In addition the upstart provider is the default on Ubuntu while the redhat provider is default on Redhat, and to provide a fallback mechanism like this the upstart provider would need to be the default provider so that it could invoke `super` to get at the parent redhat behavior. Lastly, default providers are set on a global basis so we can't detect what provider to use on a per-instance basis. Even if we could do that detection it would get super screwy if a package installed an init script or upstart file while running and we created the wrong type beforehand. I see two approaches to this. The first is to have two upstart implementations, one for Ubuntu and one for Redhat 6, but that's a lot of code duplication. Alternately we could detect what system we're running and dynamically set the parent class of the upstart provider based on that, but that's the road to madness. This is why I'm asking how important this limitation is; we can fix this but it will either be ugly or require a fair amount of work. If upstart isn't very prevalent then I think we should accept the limitations and tell users that if they're using upstart on Redhat 6 then the upstart services will have to explicitly declare the appropriate provider in the given service resources. Michael Stahnke thoughts? Add Comment
Jira (PUP-1864) Tag the release and create packages
Title: Message Title Ryan McKern commented on an issue Re: Tag the release and create packages Packaging is on-hold. We can't package for debian-testing due to their removal of the virtual package libopenssl-ruby from the ruby package in debian-testing. I'm opening a bug with them now. Add Comment Puppet / PUP-1864 Tag the release and create packages This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1864) Tag the release and create packages
Title: Message Title Ryan McKern commented on an issue Re: Tag the release and create packages the package gas apparently been renamed to 'libopenssl-ruby1.9.1' so dependencies are being updated Add Comment Puppet / PUP-1864 Tag the release and create packages This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1679) Eradicate usage of FileUtils / File .chmod and move to the FileSystem abstraction
Title: Message Title Ethan Brown commented on an issue Re: Eradicate usage of FileUtils / File .chmod and move to the FileSystem abstraction Actually, this ticket can remain open. I think the idea here was to take the fixes implemented as part of PUP-1681 and make sure all the calls that use stock Ruby code are instead using our filesystem code. At the time, we needed the fix in quickly, and I didn't want to rock the boat replacing all the existing callsites. Add Comment Puppet / PUP-1679 Eradicate usage of FileUtils / File .chmod and move to the FileSystem abstraction The built-in Ruby classes FileUtils.chmod and File.chmod do not behave correctly under Windows. We do however have a nice method Puppet::Util::Windows::Security.set_mode(mode, path) that does it's best job to simulate a POSIX mode and roundtrip it properly. All call sites that use the Ruby methods should be updated to use a new Puppet::FileSystem.ch... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1864) Tag the release and create packages
Title: Message Title Ryan McKern commented on an issue Re: Tag the release and create packages I've got an updated Debian control file ready to test. If it builds correctly, I'll submit a PR for it. Add Comment Puppet / PUP-1864 Tag the release and create packages This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1679) Eradicate usage of FileUtils / File .chmod and move to the FileSystem abstraction
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-1679 Eradicate usage of FileUtils / File .chmod and move to the FileSystem abstraction Change By: Eric Sorenson Fix Version/s: 3.x Fix Version/s: 3.6.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-1936) PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern
Title: Message Title gepetto-bot created an issue Puppet / PUP-1936 PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 13/Mar/14 2:28 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Update Debian depenencies for new debian-testing packages Author: Ryan McKern r...@orangefort.com Company: Puppet Labs Github ID: mckern Pull Request 2433 Discussion Pull Request 2433 File Diff Pull Request Description
Jira (PUP-1864) Tag the release and create packages
Title: Message Title Ryan McKern commented on an issue Re: Tag the release and create packages Opened PR 2433 Add Comment Puppet / PUP-1864 Tag the release and create packages This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1936) PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern
Title: Message Title gepetto-bot commented on an issue Re: PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern mckern commented: DON'T MERGE, THERE'S A TYPO! OH NO! Add Comment Puppet / PUP-1936 PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern h2. (maint) Update Debian depenencies for new debian-testing packages * Author: Ryan McKern r...@orangefort.com * Company: Puppet Labs * Github ID: [mckern|https://github.com/mckern] * [Pull Request 2433 Discussion|https://github.com/puppetlabs/puppet/pull/2433] * [Pull Request 2433 File Diff|https://github.com/puppetlabs/puppet/pull/2433/files] ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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-1936) PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern
Title: Message Title gepetto-bot commented on an issue Re: PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern Pull request (maint) Update Debian depenencies for new debian-testing packages has been reopened. Add Comment Puppet / PUP-1936 PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern h2. (maint) Update Debian depenencies for new debian-testing packages * Author: Ryan McKern r...@orangefort.com * Company: Puppet Labs * Github ID: [mckern|https://github.com/mckern] * [Pull Request 2433 Discussion|https://github.com/puppetlabs/puppet/pull/2433] * [Pull Request 2433 File Diff|https://github.com/puppetlabs/puppet/pull/2433/files] ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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-1936) PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern
Title: Message Title gepetto-bot commented on an issue Re: PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern Pull request (maint) Update Debian depenencies for new debian-testing packages has been closed. Add Comment Puppet / PUP-1936 PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern h2. (maint) Update Debian depenencies for new debian-testing packages * Author: Ryan McKern r...@orangefort.com * Company: Puppet Labs * Github ID: [mckern|https://github.com/mckern] * [Pull Request 2433 Discussion|https://github.com/puppetlabs/puppet/pull/2433] * [Pull Request 2433 File Diff|https://github.com/puppetlabs/puppet/pull/2433/files] ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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-1936) PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern
Title: Message Title gepetto-bot commented on an issue Re: PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern mckern commented: OK, typo fixed. Add Comment Puppet / PUP-1936 PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern h2. (maint) Update Debian depenencies for new debian-testing packages * Author: Ryan McKern r...@orangefort.com * Company: Puppet Labs * Github ID: [mckern|https://github.com/mckern] * [Pull Request 2433 Discussion|https://github.com/puppetlabs/puppet/pull/2433] * [Pull Request 2433 File Diff|https://github.com/puppetlabs/puppet/pull/2433/files] ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1931) mount provider improvement when options property is not specified
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1931 mount provider improvement when options property is not specified Change By: Charlie Sharpsteen Labels: customer 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-1936) PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern
Title: Message Title gepetto-bot commented on an issue Re: PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern shrug commented: :+1: Add Comment Puppet / PUP-1936 PR (2433): (maint) Update Debian depenencies for new debian-testing packages - mckern h2. (maint) Update Debian depenencies for new debian-testing packages * Author: Ryan McKern r...@orangefort.com * Company: Puppet Labs * Github ID: [mckern|https://github.com/mckern] * [Pull Request 2433 Discussion|https://github.com/puppetlabs/puppet/pull/2433] * [Pull Request 2433 File Diff|https://github.com/puppetlabs/puppet/pull/2433/files] ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
