Jira (HI-46) Hiera should support alternate environments
Title: Message Title Jiri Horky updated an issue Hiera / HI-46 Hiera should support alternate environments Change By: Jiri Horky Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-46) Hiera should support alternate environments
Title: Message Title Jiri Horky commented on an issue Re: Hiera should support alternate environments This is a major problem with increasing priority as the hiera gets more and more inevitable. The puppet's environments are great but to really be able to test complex changes, this bug must be resolved. Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2751) exec:commands seprated with ;, , ||, the results does not match what we expect
Title: Message Title zhangzhipeng updated an issue Puppet / PUP-2751 exec:commands seprated with ;, , ||, the results does not match what we expect Change By: zhangzhipeng Priority: Major Normal 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-2751) exec:commands seprated with ;, , ||, the results does not match what we expect
Title: Message Title zhangzhipeng assigned an issue to zhangzhipeng Puppet / PUP-2751 exec:commands seprated with ;, , ||, the results does not match what we expect Change By: zhangzhipeng Assignee: zhangzhipeng 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-2751) exec:commands seprated with ;, , ||, the results does not match what we expect
Title: Message Title
zhangzhipeng updated an issue
Puppet / PUP-2751
exec:commands seprated with ;, , ||, the results does not match what we expect
Change By:
zhangzhipeng
Afterexecwastriggered,threelineswasexpectedtobeaddedto/tmp/sssd.conf,butonlythelastone line wasaddedtothefile.Itriedinstead,buttheresultwasunchangedeither.{noformat}classsudo_ipa::log{$log_config1=Defaults\tlogfile=/var/log/sudo\n$log_config2=Defaults\tloglinelen=0\n$log_config3=Defaults\t!syslog$sudo_path=/tmp/sssd.confexec{echo$log_config1$sudo_path;echo$log_config2$sudo_path;echo$log_config3$sudo_path:path=/bin,unless=greplogfile/etc/sudoers,}}{noformat}logs:{noformat}Info:RetrievingpluginfactsInfo:RetrievingpluginInfo:Cachingcatalogforrhel.cqrd.comInfo:Applyingconfigurationversion'1402473836'Notice:/Stage[main]/Sudo_ipa::Log/Exec[echoDefaultslogfile=/var/log/sudo/tmp/sssd.conf;echoDefaultsloglinelen=0/tmp/sssd.conf;echoDefaults!syslog/tmp/sssd.conf]/returns:executedsuccessfullyNotice:Finishedcatalogrunin0.35seconds{noformat}/tmp/sssd.conf{noformat}[root@rhel/tmp]#tail-n6sssd.confDefaults!syslogDefaults!syslogDefaults!syslogDefaults!syslogDefaults!syslog{noformat}
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-2751) exec:commands seprated with ;, , ||, the results does not match what we expect
Title: Message Title
zhangzhipeng created an issue
Puppet / PUP-2751
exec:commands seprated with ;, , ||, the results does not match what we expect
Issue Type:
Bug
Affects Versions:
3.6.1
Assignee:
Unassigned
Created:
11/Jun/14 1:07 AM
Priority:
Major
Reporter:
zhangzhipeng
After exec was triggered, three lines was expected to be added to /tmp/sssd.conf, but only the last one line was added to the file.
I tried instead, but the result was unchanged either.
class sudo_ipa::log {
$log_config1=Defaults\tlogfile=/var/log/sudo\n
$log_config2=Defaults\tloglinelen=0\n
$log_config3=Defaults\t!syslog
$sudo_path=/tmp/sssd.conf
exec { echo $log_config1 $sudo_path; echo $log_config2 $sudo_path; echo $log_config3 $sudo_path:
path = /bin,
unless = grep logfile /etc/sudoers,
}
}
logs:
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Caching catalog for rhel.cqrd.com
Info: Applying configuration version '1402473836'
Notice: /Stage[main]/Sudo_ipa::Log/Exec[echo Defaults logfile=/var/log/sudo
/tmp/sssd.conf; echo Defaults loglinelen=0
/tmp/sssd.conf; echo Defaults !syslog /tmp/sssd.conf]/returns: executed successfully
Notice: Finished catalog run in 0.35 seconds
Jira (PUP-2752) Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format
Title: Message Title Tristan Helmich created an issue Puppet / PUP-2752 Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format Issue Type: Bug Affects Versions: 3.6.2, 3.6.1, 3.6.0 Assignee: Pieter van de Bruggen Components: PMT Created: 11/Jun/14 1:20 AM Labels: moduletool pmt Priority: Critical Reporter: Tristan Helmich Since Puppet 3.6.0 the module tool is unable to install new modules if an already existing modules version does not conform to the MAJOR.MINOR.PATCH format. I believe this behaviour was introduced with the dependency resolver ( https://github.com/puppetlabs/puppet/commit/6fa68b54ac621d60dbf1b062f8dd66b186d1a87f ) How to reproduce problem: Place a module that does not conform with the X.Y.Z version format in your module folder (e.g. https://github.com/mrintegrity/puppet-pound ). To simulate this with another module just edit the metadata.json
Jira (PUP-2751) exec:commands seprated with ;, , ||, the results does not match what we expect
Title: Message Title zhangzhipeng updated an issue Puppet / PUP-2751 exec:commands seprated with ;, , ||, the results does not match what we expect Change By: zhangzhipeng Priority: Normal Blocker 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-2751) exec:commands seprated with ;, , ||, the results does not match what we expect
Title: Message Title
zhangzhipeng updated an issue
Puppet / PUP-2751
exec:commands seprated with ;, , ||, the results does not match what we expect
Change By:
zhangzhipeng
Afterexecwastriggered,threelineswasexpectedtobeaddedto/tmp/sssd.conf,butonlythelastonewasaddedtothefile. nothing Itriedinstead,buttheresultwasunchangedeither.{noformat}classsudo_ipa::log{$log_config1=Defaults\tlogfile=/var/log/sudo\n$log_config2=Defaults\tloglinelen=0\n$log_config3=Defaults\t!syslog$sudo_path=/tmp/sssd.confexec{echo$log_config1$sudo_path;echo$log_config2$sudo_path;echo$log_config3$sudo_path:path=/bin,unless=greplogfile/etc/sudoers,}}{noformat}logs:{noformat}Info:RetrievingpluginfactsInfo:RetrievingpluginInfo:Cachingcatalogforrhel.cqrd.comInfo:Applyingconfigurationversion'1402473836'Notice:/Stage[main]/Sudo_ipa::Log/Exec[echoDefaultslogfile=/var/log/sudo/tmp/sssd.conf;echoDefaultsloglinelen=0/tmp/sssd.conf;echoDefaults!syslog/tmp/sssd.conf]/returns:executedsuccessfullyNotice:Finishedcatalogrunin0.35seconds{noformat}/tmp/sssd.conf{noformat}[root@rhel/tmp]#tail-n6sssd.confDefaults!syslogDefaults!syslogDefaults!syslogDefaults!syslogDefaults!syslog{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-46) Hiera should support alternate environments
Title: Message Title
Michal Zubac commented on an issue
Re: Hiera should support alternate environments
solved by prefixing each hierarchy item in hiera.yaml with %{::environment}/. having separate hiera subtrees checked out for each branch/environment.
Add Comment
Hiera / HI-46
Hiera should support alternate environments
Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-46) Hiera should support alternate environments
Title: Message Title Michal Zubac commented on an issue Re: Hiera should support alternate environments problem with having separate hierachy definition for each branch/environment is still open though. Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1137) Maintenance task for the filebucket
Title: Message Title
Paul Ttterman commented on an issue
Re: Maintenance task for the filebucket
Would the tidy resource solve this?
tidy { '/var/lib/puppet/clientbucket':
age = '5w',
recurse = true,
rmdirs = true,
}
Add Comment
Puppet / PUP-1137
Maintenance task for the filebucket
As per: * https://groups.google.com/forum/#!topic/puppet-users/GjTxlD7VRww/discussion * https://ask.puppetlabs.com/question/132/does-filebucket-need-periodic-maintenance-cleaning/ Sometimes it's useful to clean the clientbucket on a Puppet master as it can grow over time and after a while becomes useless. It would be nice if there's a rake task...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you 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-1112) Puppet Packages should be built to support Ruby 1.9 from Software Collections.
Title: Message Title Drew Blessing commented on an issue Re: Puppet Packages should be built to support Ruby 1.9 from Software Collections. With RHEL7 shipping now it would be a great opportunity for PuppetLabs to make sure new packages are flexible. Please support at LEAST software collections Ruby 2.1 in RHEL7, but if possible make it flexible enough to use a non-software collection package, too. Add Comment Puppet / PUP-1112 Puppet Packages should be built to support Ruby 1.9 from Software Collections. Many RHEL/CentOS users wish to move to Ruby 1.9 but without having to roll their own environment and repackage all Puppet packages. The Fedora Software Collections gives us this capability and I would like to request that a set of packages be rolled to support Ruby from SC. https://fedorahosted.org/SoftwareCollections/ This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this 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 (PUP-2753) Adding FQDN with Host type breaks /etc/hosts
Title: Message Title
Albin Gustavsson created an issue
Puppet / PUP-2753
Adding FQDN with Host type breaks /etc/hosts
Issue Type:
Bug
Affects Versions:
3.6.2, 3.4.3
Assignee:
Unassigned
Created:
11/Jun/14 5:59 AM
Priority:
Major
Reporter:
Albin Gustavsson
Hello,
We have discovered that managing the hosts file with this puppet module tends to break the /etc/hosts file: https://github.com/ghoneycutt/puppet-module-hosts This will eventually run the following code
host { $::fqdn:
ensure = present,
host_aliases = $::hostname,
ip = $::ipaddress,
}
This happens for us when a system doesn't have the fqdn in the hosts file and when the module attempts to add it the system ends up with two lines for the same IP in the hosts file. This has shown to break som services, for example xauth.
Original file
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
10.0.1.100 srv100
Jira (PDB-704) PuppetDB installing postgresql is not optional
Title: Message Title Kenneth Barber commented on an issue Re: PuppetDB installing postgresql is not optional I'll make a PR and see how it looks from there. Code definitely speaks louder than words, feel free to raise a PR and we'll take a look. The current implementation forces the PostgreSQL server to be installed with only those parameters exposed by the classes in the PuppetDB module. You can't even specify that the data directory should be somewhere else, or if you want PostGIS installed. Well PostGIS isn't needed by PuppetDB, why would we want to express this capability within the PDB module? Again, I'm wary of just proxying a whole bunch of parameters, this is definitely not something I'm interested in supporting going forward, not when you have the full capability escape hatch right at your finger tips. This speaks of a shared database scenario, which I'm wary of fully supporting anyway for reasons outlined below. At least I'm wary of supporting the primary 'postgresql::server' definition for this in our module. Cut-pasting code out of the PuppetDB module is... bad... and will lead to configuration drift and duplicate declarations of resources. I would agree with you more, if the amount of code required wasn't tiny anyway, so I'm not entirely sure this is a pragmatic viewpoint today but if you're opinionated enough about this then raising a PR is best. I think if we had more stringent requirements beyond just user/db/grant (like if we absolutely required certain PG extensions to be installed) then I would be more opinionated about how we do this. But again, show your ideas in the form of code and I'll take a look. Anyway, I think on a minimal level I could see the postgresql instance creation (the postgresql::server class) being separate from the postgresql resource declarations at least (the postgresql::server::db resource) - we could certainly split this into two classes (for example) that would avoid your duplication problem. I can see where someone might want to manage a shared database or have very strong opinions beyond the how postgresql gets set up beyond how PuppetDB wants to do it. (Although I wouldn't recommend a shared instance to anyone, for resource/performance reasons - PDB should have its own postgresql instance, sharing a database is not going to be a good idea, purely for the reason that you can't fine-tune the database settings for the application without affecting everything else. What more its harder to determine if any application is draining your DB resources over another when you mix things up . So I would be open to splitting up that functionality at the very least to avoid your duplication issue. What I don't want is every feature in postgresql proxied to our puppetdb module, I've been down this road for many different modules, its always a PITA . Anyway, this isn't a bug by our definition - so I'm changing it to a feature. I think the rough outline above probably warrants it as a 2 day piece of work (max, including rspec testing etc.) so I'll mark it as such. If you provide a PR update the ticket.
Jira (PDB-704) PuppetDB installing postgresql is not optional
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-704 PuppetDB installing postgresql is not optional Change By: Kenneth Barber Story Points: 2 Issue Type: Bug NewFeature Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1072) support HTTP(S) URL as the file 'source'
Title: Message Title Anthony Ryan commented on an issue Re: support HTTP(S) URL as the file 'source' Since this is being evaluated, I'd like to throw in my two cents for how this should be done: `/lib/sources` should be created in the code. It can contain source providers `file.rb`, `puppet.rb` `http.rb`. It should also be possible to register source protocols within puppet plugins. This way developers can create their own implementations to suit their needs (and don't need to request every new source protocol they want). This means that if you achieve no consensus for how http should be implemented. Implementing plugin support alone will allow the creation of all the various http implementations people desire. If a consensus is found and a http source provider gets included, I believe it should be possible to overwrite it from a puppet plugin. This way if the built-in http implementation doesn't suit a group of people, they can use their own implementation. Comparing checksums should be a part of the source providers, because different checksums are going to be desired for different protocols. This way some http implementations can use etags, others can use X-SHA1 or other custom http headers. Source providers should also be able to pick their default checksum in cases where one is not explicitly specified. It should be possible for a single provider to handle more than one protocol, for example a http source provider would need to register `http` and `https`. Add Comment
Jira (PUP-1062) Add virtualenv support to the pip package provider
Title: Message Title
Jason Antman commented on an issue
Re: Add virtualenv support to the pip package provider
There isn't. I did some work on this, and ended up giving up on it. I don't think it's feasible, at least not without some major changes to the package type and provider.
For our internal use, we've developed a virtualenv module with its own types that handle this... I'm working on trying to get it released, but we've been caught up in a corporate legal mire for ages.
Add Comment
Puppet / PUP-1062
Add virtualenv support to the pip package provider
Now that #6527 is merged into master, it is possible to easily add support for virtualenvs and fully complete #3572. A `virtualenv` argument could be added to the `package` type in order to instrument `pip` to install the requested package into the given virtualenv directory. For example:package { my-python-package: ensure ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an
Jira (PUP-2570) Inconsistent results with Solaris kernelrelease fact
Title: Message Title John Lyman commented on an issue Re: Inconsistent results with Solaris kernelrelease fact I just noticed this is also an isssue with operatingsystemrelease. Looking at the code, that makes sense because on Solaris, operatingsystemrelease is set to kernelrelease. What is interesting is that the two do not always agree: err: Could not retrieve catalog from remote server: Error 400 on SERVER: kernelrelease = 5.1 operatingsystemrelease = 5.10 at /source/bugtest/manifests/site.pp:1 on node server.example.com err: Could not retrieve catalog from remote server: Error 400 on SERVER: kernelrelease = 5.10 operatingsystemrelease = 5.1 at /source/bugtest/manifests/site.pp:1 on node server.example.com err: Could not retrieve catalog from remote server: Error 400 on SERVER: kernelrelease = 5.10 operatingsystemrelease = 5.1 at /source/bugtest/manifests/site.pp:1 on node server.example.com err: Could not retrieve catalog from remote server: Error 400 on SERVER: kernelrelease = 5.10 operatingsystemrelease = 5.1 at /source/bugtest/manifests/site.pp:1 on node server.example.com err: Could not retrieve catalog from remote server: Error 400 on SERVER: kernelrelease = 5.1 operatingsystemrelease = 5.10 at /source/bugtest/manifests/site.pp:1 on node server.example.com err: Could not retrieve catalog from remote server: Error 400 on SERVER: kernelrelease = 5.1 operatingsystemrelease = 5.10 at /source/bugtest/manifests/site.pp:1 on node server.example.com err: Could not retrieve catalog from remote server: Error 400 on SERVER: kernelrelease = 5.10 operatingsystemrelease = 5.1 at /source/bugtest/manifests/site.pp:1 on node server.example.com I'm not sure if 5.10 is getting truncated or converted to a float. Add Comment Puppet / PUP-2570 Inconsistent results with Solaris kernelrelease fact
Jira (PUP-574) NTFS ACL module
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-574 NTFS ACL module Change By: Kenn Hussey Epic Status: Done Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1066) yum repos should be ensurable.
Title: Message Title Timothy Clarke commented on an issue Re: yum repos should be ensurable. I don't think (#1023) yumrepo option to purge unmanaged repos has been completed While you can ensure = absent that will only apply to configured repo's rather than removing all unmanaged repo's Add Comment Puppet / PUP-1066 yum repos should be ensurable. This should be done so that we can solve: #949 - yumrepo should support removal of repository #1023 - yumrepo option to purge unmanaged repos This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2754) Exit status is 0, even in the presence of errors, without --detailed-exitcodes
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-2754
Exit status is 0, even in the presence of errors, without --detailed-exitcodes
Issue Type:
Bug
Assignee:
Unassigned
Created:
11/Jun/14 8:56 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
When an error is encountered while running either `puppet apply` or `puppet agent`, the program exits with status 0. If `--detailed-exitcodes` is used with `puppet agent`, the status is nonzero as expected. I would expect that non-detailed exit codes would still include 1 for the case of a failure to apply the catalog.
You can recreate this with the following manifest: pre exec { 'false': command = '/bin/false', }
/pre
Example run: pre marmida@monolith:~$ puppet apply fail_manifest.py warning: Could not retrieve fact fqdn err: /Stage[main]//Exec[false]/returns: change from notrun to 0 failed: /bin/false returned 1 instead of one of [0] at /home/marmida/fail_manifest.py:3 notice: Finished catalog run in 0.14 seconds marmida@monolith:~$ echo $? 0 marmida@monolith:~$ puppet apply fail_manifest.py --detailed-exitcodes warning: Could not retrieve fact fqdn err: /Stage[main]//Exec[false]/returns: change from notrun to 0 failed: /bin/false returned 1 instead of one of [0] at /home/marmida/fail_manifest.py:3 notice: Finished catalog run in 0.13 seconds marmida@monolith:~$ echo $? 4 /pre
The same problems occur in `puppet agent`.
I couldn't find another issue specific to the exit status, but I did notice it mentioned once here:
Jira (PUP-1983) contain causes edges with nil targets to be added to the catalog
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1983 contain causes edges with nil targets to be added to the catalog Change By: Henrik Lindberg Assignee: NicholasFagerlund 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-1983) contain causes edges with nil targets to be added to the catalog
Title: Message Title
Henrik Lindberg commented on an issue
Re: contain causes edges with nil targets to be added to the catalog
Nicholas Fagerlund assigned to you to make you aware of the discussion and the changes in 3.7 that fixes the reported issue. (The issue itself will be closed as a duplicate, and I wanted you to get a chance to react to it before closing).
Add Comment
Puppet / PUP-1983
contain causes edges with nil targets to be added to the catalog
With certain manifests, interestingly enough not all of them, using contain causes nil edges to be added to the catalog. {noformat} class profile::apt { contain apt contain apt::backports contain apt::unattended_upgrades } {noformat} This causes a nil edge to appear in the catalog from {{Class\[Apt\]}} to nothing. Using this pattern, wh...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this
Jira (HI-46) Hiera should support alternate environments
Title: Message Title garrett honeycutt commented on an issue Re: Hiera should support alternate environments Michal Zubac It is not solved by prefixing each level of the hierarchy with an environment. hiera_hash() and hiera_array() will merge data from the entire hierarchy which allows data from one environment to leak into another. Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1983) contain causes edges with nil targets to be added to the catalog
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1983 contain causes edges with nil targets to be added to the catalog Change By: Henrik Lindberg Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-46) Hiera should support alternate environments
Title: Message Title R.I.Pienaar commented on an issue Re: Hiera should support alternate environments those functions only take data from the hierarchy that matches the node. So it will work fine Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1762) Puppet compiler does not bat an eye at variables that are missing a dollar sign
Title: Message Title
Henrik Lindberg commented on an issue
Re: Puppet compiler does not bat an eye at variables that are missing a dollar sign
No, there is nothing we can do about this. Closing.
Add Comment
Puppet / PUP-1762
Puppet compiler does not bat an eye at variables that are missing a dollar sign
{noformat} Notice: Finished catalog run in 0.03 seconds antarus@goats5 /tmp $ cat foo.pp $foo = ::puppetversion ? { '3.2.4' = 'broken', default = 'goats' } notice($::puppetversion) notice($foo) antarus@goats5 /tmp $ puppet apply foo.pp Notice: Scope(Class[main]): 3.2.4 Notice: Scope(Class[main]): goats Notice: Finished catalog run in...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-46) Hiera should support alternate environments
Title: Message Title garrett honeycutt commented on an issue Re: Hiera should support alternate environments R.I.Pienaar If you knew the other environment names, couldn't you just specify your environment as another one and access their data? Also, how does it solve the issue of different environment using multiple backends? Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2755) Move iterative functions to 4x function API
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2755 Move iterative functions to 4x function API Issue Type: Improvement Assignee: Andy Parker Components: DSL Created: 11/Jun/14 9:21 AM Fix Versions: 3.7.0 Priority: Normal Reporter: Henrik Lindberg The iterative functions (each, map, filter, reduce, slice) should be moved to the 4x function API. (Currently there is a cheat implemented in the evaluator when these are called to avoid having the arguments transformed to the 3x function API). Add Comment
Jira (PUP-2756) Fix faulty acceptance test for future parser
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2756 Fix faulty acceptance test for future parser Issue Type: Bug Assignee: Unassigned Created: 11/Jun/14 9:25 AM Priority: Blocker Reporter: Henrik Lindberg This test: https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/apply/conditionals/should_evaluate_undef.rb Is faulty for future parser since undef is no longer equal to an empty string. This blocks getting a clean acceptance test run. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1066) yum repos should be ensurable.
Title: Message Title Adrien Thebo commented on an issue Re: yum repos should be ensurable. Timothy Clarke `ensure = absent` only removes a single resource, not all resources. Why can't you use the `resources` resource to purge all unmanaged repos? Add Comment Puppet / PUP-1066 yum repos should be ensurable. This should be done so that we can solve: #949 - yumrepo should support removal of repository #1023 - yumrepo option to purge unmanaged repos This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1137) Maintenance task for the filebucket
Title: Message Title Josh Cooper commented on an issue Re: Maintenance task for the filebucket With the addition of PUP-1840 , it would be nice to upgrade file content from one checksum to another, e.g. md5 - sha256, or remove content for a given checksum type, e.g. md5 Add Comment Puppet / PUP-1137 Maintenance task for the filebucket As per: * https://groups.google.com/forum/#!topic/puppet-users/GjTxlD7VRww/discussion * https://ask.puppetlabs.com/question/132/does-filebucket-need-periodic-maintenance-cleaning/ Sometimes it's useful to clean the clientbucket on a Puppet master as it can grow over time and after a while becomes useless. It would be nice if there's a rake task... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this 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 (PUP-2300) Prune dead code from PMT
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2300 Prune dead code from PMT Change By: Josh Cooper Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2304) Implement requirements support for the PMT
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2304 Implement requirements support for the PMT Change By: Josh Cooper Assignee: PietervandeBruggen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper Change By: Josh Cooper Assignee: AndyParker PietervandeBruggen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2186) Add `puppet module show` action
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2186 Add `puppet module show` action Change By: Josh Cooper Assignee: AndersonMills PietervandeBruggen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2454 User ID's below 1000, not 500, are generally considered system users on OpenBSD Change By: Josh Cooper Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD
Title: Message Title Josh Cooper commented on an issue Re: User ID's below 1000, not 500, are generally considered system users on OpenBSD Merged in 2849ba36 into master to be released in 3.7.0 Add Comment Puppet / PUP-2454 User ID's below 1000, not 500, are generally considered system users on OpenBSD Users can still modify this with 'uid_start' in adduser.conf, but in that case they'd need to provide an actual value instead of 'true'. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2079) puppet module generate can't copy template files without parsing/renaming them
Title: Message Title Andy Parker updated an issue Puppet / PUP-2079 puppet module generate can't copy template files without parsing/renaming them Change By: Andy Parker Component/s: PMT Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2078) Puppet module install --force does not re-install dependencies
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2078 Puppet module install --force does not re-install dependencies Change By: Josh Cooper Component/s: PMT Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2513) puppet module install fails when url includes basic auth
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2513 puppet module install fails when url includes basic auth Change By: Josh Cooper Component/s: PMT Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2312) puppet module search for module by name fails
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2312 puppet module search for module by name fails Change By: Josh Cooper Assignee: AndyParker PietervandeBruggen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2312) puppet module search for module by name fails
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2312 puppet module search for module by name fails Change By: Josh Cooper Component/s: PMT Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2513) puppet module install fails when url includes basic auth
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2513 puppet module install fails when url includes basic auth Change By: Josh Cooper Assignee: PietervandeBruggen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2078) Puppet module install --force does not re-install dependencies
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2078 Puppet module install --force does not re-install dependencies Change By: Josh Cooper Assignee: AndyParker PietervandeBruggen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2312) puppet module search for module by name fails
Title: Message Title Josh Cooper commented on an issue Re: puppet module search for module by name fails Jesse Scott can we close this? Add Comment Puppet / PUP-2312 puppet module search for module by name fails On PE, the following search fails: puppet module search puppetlabs-mysql I expect it to find the module named puppetlabs-mysql. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Rudy McComb commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log ruby 2.0.0p451 (2014-02-24 revision 45167) [universal.x86_64-darwin13] puppet 3.6.0 Mac OSX 10.9 Mavericks filesystems: HFS+ Installed puppet via gem then uninstalled gem and installed with dmg. Issue showed up randomly on some systems that were updated after 3.4.2 Issue does not show up on RHEL or Ubuntu Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2312) puppet module search for module by name fails
Title: Message Title Jesse Scott commented on an issue Re: puppet module search for module by name fails Fine with me. Add Comment Puppet / PUP-2312 puppet module search for module by name fails On PE, the following search fails: puppet module search puppetlabs-mysql I expect it to find the module named puppetlabs-mysql. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1069) Implement feature :upgradeable for OpenBSD package provider
Title: Message Title Adrien Thebo commented on an issue Re: Implement feature :upgradeable for OpenBSD package provider Merged in 07250d9. Add Comment Puppet / PUP-1069 Implement feature :upgradeable for OpenBSD package provider It's currently not possible to use ensure = latest on OpenBSD. The code itself works correct in my testing, however I'm having some issues with getting spec tests to pass and I'd appreciate some help with that as it appears to return the version for the bash fixture, and not the new (or old) version of tcsh. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1069) Implement feature :upgradeable for OpenBSD package provider
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1069 Implement feature :upgradeable for OpenBSD package provider Change By: Adrien Thebo Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1069) Implement feature :upgradeable for OpenBSD package provider
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1069 Implement feature :upgradeable for OpenBSD package provider Change By: Adrien Thebo Sprint: Week2014-6-11to2014-6-18 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-46) Hiera should support alternate environments
Title: Message Title Jo Rhett commented on an issue Re: Hiera should support alternate environments Garret, I'm not sure that preventing people from poking under the hood is necessary. I'm aware of one site that does this extensively and considers it a feature. That's a YMMV issue I totally agree with you that separate hiera.yaml files are useful for configuring different backends and hierarchy paths. However, one could argue that this perhaps marks the distinction where a separate Puppet server is necessary. I personally don't think it's a problem to mark the hiera hierarchy as the boundary distinction between distinct servers. Given how trivial it is to run N puppet servers on the same box sharing some common module paths, this is perhaps a documentation request more than a technical problem. All IMHO naturally, and I have no clue how this would impact PE product. I suspect its only a few man-days worth of effort to autobuild distinct servers from the control panel. (I've built such a thing in roughly half a day for a customer, although I was able to re-use their existing web panel and tune it specifically to their needs so my scope was less) Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment.
Jira (HI-46) Hiera should support alternate environments
Title: Message Title garrett honeycutt commented on an issue Re: Hiera should support alternate environments Jo Rhett Your work around of using multiple puppet masters is very interesting, but still a work around for what this ticket aims to solve. If Puppet could use different Hiera configurations, separate puppet masters would not be needed. Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2569) puppet cert revoke name doesn't always revoke what you expect
Title: Message Title
Andy Parker commented on an issue
Re: puppet cert revoke name doesn't always revoke what you expect
Merged into master in bf6d1a6
Add Comment
Puppet / PUP-2569
puppet cert revoke name doesn't always revoke what you expect
When revoking a certificate by name and there is not certificate by that name present (for instance if the certificates were deleted) the puppet cert command falls back to the {{inventory.txt}} file to find the serial number. When it does this it ends up only revoking the first serial number recorded in the file. This leaves the most recent certificate ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-2569) puppet cert revoke name doesn't always revoke what you expect
Title: Message Title Andy Parker updated an issue Puppet / PUP-2569 puppet cert revoke name doesn't always revoke what you expect Change By: Andy Parker Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2365) Puppet module tool on windows cannot connect to the forge
Title: Message Title
Josh Cooper commented on an issue
Re: Puppet module tool on windows cannot connect to the forge
Still waiting on ops to deploy the new cert
Add Comment
Puppet / PUP-2365
Puppet module tool on windows cannot connect to the forge
Due to heartbleed, operations obtained a wildcard SSL certificate issued by {code}Issuer: C=US, ST=UT, L=Salt Lake City, O=The USERTRUST Network, OU=http://www.usertrust.com, CN=UTN-USERFirst-Hardware{code} This certificate is not installed by default on Windows hosts, as a result the PMT cannot make an authenticated SSL connection to the forge: {code}...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2365) Puppet module tool on windows cannot connect to the forge
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-2365 Puppet module tool on windows cannot connect to the forge Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2569) puppet cert revoke name doesn't always revoke what you expect
Title: Message Title
Andy Parker commented on an issue
Re: puppet cert revoke name doesn't always revoke what you expect
Jeremy Barlow, Nate Wolfe this is now in. You will probably want to update the way you are implementing certificate revocation.
Add Comment
Puppet / PUP-2569
puppet cert revoke name doesn't always revoke what you expect
When revoking a certificate by name and there is not certificate by that name present (for instance if the certificates were deleted) the puppet cert command falls back to the {{inventory.txt}} file to find the serial number. When it does this it ends up only revoking the first serial number recorded in the file. This leaves the most recent certificate ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2365) Puppet module tool on windows cannot connect to the forge
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2365 Puppet module tool on windows cannot connect to the forge Change By: Josh Cooper Component/s: PMT Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2569) puppet cert revoke name doesn't always revoke what you expect
Title: Message Title Andy Parker updated an issue Puppet / PUP-2569 puppet cert revoke name doesn't always revoke what you expect Change By: Andy Parker Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2569) puppet cert revoke name doesn't always revoke what you expect
Title: Message Title Andy Parker updated an issue Puppet / PUP-2569 puppet cert revoke name doesn't always revoke what you expect Change By: Andy Parker Sprint: Week2014-6-11to2014-6-18 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1069) Implement feature :upgradeable for OpenBSD package provider
Title: Message Title Andy Parker updated an issue Puppet / PUP-1069 Implement feature :upgradeable for OpenBSD package provider Change By: Andy Parker Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-46) Hiera should support alternate environments
Title: Message Title Jo Rhett commented on an issue Re: Hiera should support alternate environments I understand, but if it was my project I would question if there was a demonstrable need that justified the effort. From what I have seen of these internals, you're looking at a pretty significant refactor. IMHO and I'll shut up as my opinion is expressed Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1069) Implement feature :upgradeable for OpenBSD package provider
Title: Message Title Andy Parker updated an issue Puppet / PUP-1069 Implement feature :upgradeable for OpenBSD package provider Change By: Andy Parker Component/s: TypesandProviders 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-2569) puppet cert revoke name doesn't always revoke what you expect
Title: Message Title Andy Parker updated an issue Puppet / PUP-2569 puppet cert revoke name doesn't always revoke what you expect Change By: Andy Parker 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-2579) ssh_autorized_key does not handle options with escaped double quotes
Title: Message Title
Josh Cooper commented on an issue
Re: ssh_autorized_key does not handle options with escaped double quotes
Romain I added a test and merged into master in 28464ba to be released in 3.7.0
Add Comment
Puppet / PUP-2579
ssh_autorized_key does not handle options with escaped double quotes
With the following declaration: {code} ssh_authorized_key { 'title': user = 'root', ensure = 'present', name = 'mykey', options = [ 'command=/usr/local/bin/mybin \$SSH_ORIGINAL_COMMAND\' ], type = 'ssh-rsa', key = 'xxx', } {code} It creates the following entry: {code}command=/usr/local/bin/myb...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-464) Mandrake osfamily is missing in stable/facter-2
Title: Message Title Joshua Partlow commented on an issue Re: Mandrake osfamily is missing in stable/facter-2 Merged to facter-2 in b10635 Add Comment Facter / FACT-464 Mandrake osfamily is missing in stable/facter-2 In master, the osfamily fact returns Mandrake for the following operating systems: - Mandrake - Mandriva - Mageia This is missing for both facter stable (2.0.1) and facter-2 (2.1.0). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1066) yum repos should be ensurable.
Title: Message Title
Timothy Clarke commented on an issue
Re: yum repos should be ensurable.
Yes, sorry, long week and my mind was stuck in the yumrepo resource type. Tried resources { 'yumrepo' : purge = true }
and it's good
Add Comment
Puppet / PUP-1066
yum repos should be ensurable.
This should be done so that we can solve: #949 - yumrepo should support removal of repository #1023 - yumrepo option to purge unmanaged repos
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-197) processorcount counting CPU cores on Solaris
Title: Message Title Peter Huene updated an issue Facter / FACT-197 processorcount counting CPU cores on Solaris Change By: Peter Huene 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 (FACT-179) fqdn Fact returns nil when hostname or domain are nil
Title: Message Title
Josh Cooper commented on an issue
Re: fqdn Fact returns nil when hostname or domain are nil
Merged into facter-2 in e0aeebd to be released in 2.1. Also see note in https://github.com/puppetlabs/facter/pull/687#discussion_r13664762
Add Comment
Facter / FACT-179
fqdn Fact returns nil when hostname or domain are nil
In the case where domain is nil the fqdn is then nil. This causes a number of modules that use fqdn to break. When fqdn is nil I also cannot run puppet agent -t as I get the following error {noformat} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Must provide non empty value. on node master Warning: Not using cache ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-179) fqdn Fact returns nil when hostname or domain are nil
Title: Message Title Josh Cooper updated an issue Facter / FACT-179 fqdn Fact returns nil when hostname or domain are nil Change By: Josh Cooper Fix Version/s: 2.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 (FACT-464) Mandrake osfamily is missing in stable/facter-2
Title: Message Title Joshua Partlow updated an issue Facter / FACT-464 Mandrake osfamily is missing in stable/facter-2 Change By: Joshua Partlow Sprint: Week2014-6-11to2014-6-18 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2747) support multiple profilers
Title: Message Title Christopher Price commented on an issue Re: support multiple profilers Andy Parker I responded to all of your comments, and will probably need some more info from you before I know what my next steps are. Should I assign this ticket back to you? Add Comment Puppet / PUP-2747 support multiple profilers The current implementation of the profiling system uses a single setter method to assign/remove the active profiler. This means that it's not safe to manipulate the active profiler in new code unless you know for sure that it will not be manipulated by any other parts of the code that will be executed during the run. It also means that you can only have... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-197) processorcount counting CPU cores on Solaris
Title: Message Title Peter Huene updated an issue Facter / FACT-197 processorcount counting CPU cores on Solaris Change By: Peter Huene Fix Version/s: 2.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 (FACT-197) processorcount counting CPU cores on Solaris
Title: Message Title Peter Huene updated an issue Facter / FACT-197 processorcount counting CPU cores on Solaris Change By: Peter Huene Sprint: Week2014-6-11to2014-6-18 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-197) processorcount counting CPU cores on Solaris
Title: Message Title
Peter Huene commented on an issue
Re: processorcount counting CPU cores on Solaris
I'm putting the fix version to 2.1 currently as there doesn't seem to be a version for a next stable release (which may in fact be 2.1).
Add Comment
Facter / FACT-197
processorcount counting CPU cores on Solaris
The processorcount fact on Solaris is counting CPU cores {noformat} physicalprocessorcount = 1 processor0 = SPARC-T4 processor1 = SPARC-T4 processor2 = SPARC-T4 processor3 = SPARC-T4 processorcount = 1 {noformat} and on linux it counts CPU threads. This was reported as http://projects.puppetlabs.com/issues/18215 and a working fix is...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2747) support multiple profilers
Title: Message Title Andy Parker assigned an issue to Christopher Price Puppet / PUP-2747 support multiple profilers Change By: Andy Parker Assignee: ChristopherPrice 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-1983) contain causes edges with nil targets to be added to the catalog
Title: Message Title
Nicholas Fagerlund commented on an issue
Re: contain causes edges with nil targets to be added to the catalog
Henrik Lindberg So just to make sure I've got it:
Contain wasn't treating class name lookups the same way the other functions were.
This meant you couldn't contain ::class with the :: prefix.
This also meant that if you tried to contain apt within class profile::apt – that is, if you would have been running into the whole relative namespacing problem – it would create an edge to nil.
The above was the only situation where contain would create an edge to nil.
All of this will be fixed in 3.7, and contain will look up class names the same way the other functions do, in both parsers.
Did I get that right?
Add Comment
Puppet / PUP-1983
contain causes edges with nil targets to be added to the catalog
With certain manifests, interestingly enough not all of them, using contain causes nil edges to be added to the catalog. {noformat} class profile::apt { contain apt contain apt::backports contain apt::unattended_upgrades } {noformat} This causes a nil edge to appear in the catalog from {{Class\[Apt\]}}
Jira (PDB-648) Publicize EC2 image creation packer templates
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-648 Publicize EC2 image creation packer templates Change By: Kenneth Barber Sprint: 20140618to20140702 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-121) Add Ruby 2.0 to spec test matrix for puppetdb
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-121 Add Ruby 2.0 to spec test matrix for puppetdb Change By: Kenneth Barber Sprint: 20140618to20140702 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-2622) Exit code 0 on wrong command
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2622 Exit code 0 on wrong command Change By: Joshua Partlow Sprint: Week2014-6-11to2014-6-18 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2622) Exit code 0 on wrong command
Title: Message Title
Joshua Partlow commented on an issue
Re: Exit code 0 on wrong command
Merged to master in 433864
Add Comment
Puppet / PUP-2622
Exit code 0 on wrong command
Running {code}puppet garbarge ; echo $?{code} generates {noformat} Error: Unknown Puppet subcommand 'garbarge' See 'puppet help' for help on available puppet subcommands 0 {noformat} The exit code should not be 0. In my case I run {code}puppet --detailed-exitcodes apply ... {code} in automated way and the failure was not detected because of exit cod...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1983) contain causes edges with nil targets to be added to the catalog
Title: Message Title
Henrik Lindberg commented on an issue
Re: contain causes edges with nil targets to be added to the catalog
Yes, more or less - not sure about the statement that the above was the only situation where contain would create an edge to nil though. I think that the relative name resolution is the main culprit here in that you may end up with either circular or nil dependencies. When that happens, the error that it tries to report will fail because the target (or source) is nil and the real problem (the name resolution picking the correct (but unexpected) thing) gets masked by an internal error (nil does not respond to ref, or something like that).
In 3.7 you are still exposed to relative name resolution that may result in surprises.
Add Comment
Puppet / PUP-1983
contain causes edges with nil targets to be added to the catalog
With certain manifests, interestingly enough not all of them, using contain causes nil edges to be added to the catalog. {noformat} class profile::apt { contain apt contain apt::backports contain apt::unattended_upgrades } {noformat} This causes a nil edge to appear in the catalog from {{Class\[Apt\]}} to nothing. Using this pattern, wh...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-574) NTFS ACL module
Title: Message Title Heidi Pio commented on an issue Re: NTFS ACL module Thank you Kenn Hussey. I had this on my list to address today but you beat me to the punch! Add Comment Puppet / PUP-574 NTFS ACL module Create a module that supports the following aspects of NTFS security: manage security descriptor manage dacl manage entries inheritance propagation This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2576) Implement behavioral change in the crontab provider to allow more drastic purging
Title: Message Title Josh Cooper commented on an issue Re: Implement behavioral change in the crontab provider to allow more drastic purging Merged into puppet-4 in 8b02c2a to be released in 4.0 Add Comment Puppet / PUP-2576 Implement behavioral change in the crontab provider to allow more drastic purging See PUP-1381 for details on the bug being fixed. This new ticket was created to track the fix itself vs. adding a warning about the change. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2622) Exit code 0 on wrong command
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2622 Exit code 0 on wrong command Change By: Joshua Partlow Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2454 User ID's below 1000, not 500, are generally considered system users on OpenBSD Change By: Josh Cooper Sprint: Week2014-6-11to2014-6-18 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-179) fqdn Fact returns nil when hostname or domain are nil
Title: Message Title Josh Cooper updated an issue Facter / FACT-179 fqdn Fact returns nil when hostname or domain are nil Change By: Josh Cooper Sprint: Week2014-6-11to2014-6-18 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2579) ssh_authorized_key does not handle options with escaped double quotes
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2579 ssh_authorized_key does not handle options with escaped double quotes Change By: Josh Cooper Summary: ssh_autorized_key ssh_authorized_key doesnothandleoptionswithescapeddoublequotes 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-2579) ssh_autorized_key does not handle options with escaped double quotes
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2579 ssh_autorized_key does not handle options with escaped double quotes Change By: Josh Cooper 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-2579) ssh_autorized_key does not handle options with escaped double quotes
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2579 ssh_autorized_key does not handle options with escaped double quotes Change By: Josh Cooper Sprint: Week2014-6-11to2014-6-18 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1983) contain causes edges with nil targets to be added to the catalog
Title: Message Title
Henrik Lindberg commented on an issue
Re: contain causes edges with nil targets to be added to the catalog
We have not yet fully reviewed the code in question that creates the dependencies - in a way I guess that means that currently it is the one thing we have detected as the cause for nil entries, I have a strong feeling there are other cases.
Add Comment
Puppet / PUP-1983
contain causes edges with nil targets to be added to the catalog
With certain manifests, interestingly enough not all of them, using contain causes nil edges to be added to the catalog. {noformat} class profile::apt { contain apt contain apt::backports contain apt::unattended_upgrades } {noformat} This causes a nil edge to appear in the catalog from {{Class\[Apt\]}} to nothing. Using this pattern, wh...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit
Jira (PUP-2622) Exit code 0 on wrong command
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2622 Exit code 0 on wrong command Change By: Josh Cooper 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 (FACT-179) fqdn Fact returns nil when hostname or domain are nil
Title: Message Title Josh Cooper updated an issue Facter / FACT-179 fqdn Fact returns nil when hostname or domain are nil Change By: Josh Cooper Component/s: Community Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2579) ssh_authorized_key does not handle options with escaped double quotes
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2579 ssh_authorized_key does not handle options with escaped double quotes Change By: Josh Cooper Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2622) Exit code 0 on wrong command
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2622 Exit code 0 on wrong command Change By: Josh Cooper Component/s: Community Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-46) Hiera should support alternate environments
Title: Message Title James Sweeny commented on an issue Re: Hiera should support alternate environments This is covered a bit in the original Redmine ticket, but the real importance of having environment specific hiera.yaml files comes down to how you release changes to the hierarchy. It's a very common pattern to use multiple environments (very often tied to a VCS branch) to test changes before they get merged into a mainline/moved to production. With hiera.yaml being the same across all environments, it is impossible to make a hierarchy change in dev or a feature branch before merging or deploying to production servers. This seriously cripples many organizations' ability to test changes to the code base, since hierarchy changes need to be done all at once. The argument for this feature is that hiera.yaml should not be any different in terms of how it can be tested from the hieradata itself (which can reference $environment) or the puppet modules and manifests. The only way to do this testing without allowing multiple environment-specific versions of hiera.yaml is to have a separate master for each application landscape and manually move hiera.yaml changes among them. This is, of course, extremely impractical if you're trying to test short-lived feature branches. Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment.
Jira (PUP-2757) Apply parses everything twice
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2757 Apply parses everything twice Issue Type: Bug Assignee: Andy Parker Components: DSL Created: 11/Jun/14 1:27 PM Fix Versions: 3.7.0 Priority: Normal Reporter: Henrik Lindberg When the runtime creates Puppet::Resource instances, an attempt is made to lookup its type. This means that code will attempt to lookup the type in known_resource_types. If known_resource_type is nil, the runtime will issue a call to initial_import which is the starting point of parsing and evaluating code. The Puppet::Resource#envronment method attempts to figure out which environment to use (since that hold on to known_resource_type by looking at the resource instance's catalog's environment. The problem is when resource instances are created for the purpose of acting as a reference to a resource (rather than the instance itself), since such references are never contained in a Catalog per se. The environment method used a synthetic environment called NONE internally, and when NONE is not initialized the initial_import ill be called to again perform parsing. This is fixed in this commit: https://github.com/hlindberg/puppet/commit/3ab10bc6ffe724a204e0fd2d1df0e651c9d93d66 as part of PUP-2714, where this problem was detected. Currently, the fix is is part
Jira (PUP-1057) Remove 'collect' and 'select' iterative function stubs
Title: Message Title Henrik Lindberg commented on an issue Re: Remove 'collect' and 'select' iterative function stubs I think we can remove these stubs in 3.7 rather than moving them to the new API. They only apply to the future parser, and those that use it should have seen the deprecation warnings already. Changing this ticket to 3.7 Add Comment Puppet / PUP-1057 Remove 'collect' and 'select' iterative function stubs The functions 'select' and 'collect' are currently stubs that raise an error (to help those using the future parser from 3.5 migrate their code). In 4.0.0 those stubs should be removed. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
