Jira (PUP-6320) Bad message when passing zero sized array where non empty array is required
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-6320 Bad message when passing zero sized array where non empty array is required Change By: Sean Griffin Assignee: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6319) Bad message when passing zero sized hash where non empty hash is required
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-6319 Bad message when passing zero sized hash where non empty hash is required Change By: Sean Griffin Assignee: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6319) Bad message when passing zero sized hash where non empty hash is required
Title: Message Title
Sean Griffin updated an issue
Puppet / PUP-6319
Bad message when passing zero sized hash where non empty hash is required
Change By:
Sean Griffin
Acceptance Criteria:
{code}puppet apply - d e 'assert_type(Hash[String,String,1,default], {})'{code}should output the message "expected size to be at least 1, got 0"
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6320) Bad message when passing zero sized array where non empty array is required
Title: Message Title
Sean Griffin updated an issue
Puppet / PUP-6320
Bad message when passing zero sized array where non empty array is required
Change By:
Sean Griffin
Acceptance Criteria:
{code}puppet apply - d e 'assert_type(Array[String,1,default], [])'{code}should output the message "expected size to be at least 1, got 0"
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6322) EPP and scope context
Title: Message Title
Henrik Lindberg commented on PUP-6322
Re: EPP and scope context
Elaborating on some comments received on my earlier post.
Node and Global name space are always available directly (no need to pass those variables) to EPP templates or functions written in the puppet language.
Note that I used an inline template in the example only for the sake of not having to split it up into a separate template file. The exact same template in the example works in a separate template file then just change the call to epp instead of inline_epp.
# foo.pp
class foo($a= 10, $b=20) {
$var = 100
}
include foo
notice epp('example.epp', {context => Class[foo]})
# example.epp
<% |Type[Class[foo]] $context | -%>
Jira (PUP-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title Curtis Ruck commented on PUP-6321 Re: undef in custom type autorequire value causes error in Puppet 4.5.0 Its added from line 353 in catalog.rb in that PR. type, title = Puppet::Resource.type_and_title(type, title) The real issue is that the method contract of def resource(type, title = nil) is essentially broken now, as even the default value of title is nil, but the first line in the method (above) throws an error if a nil is passed in. So another way to fix this potentially better would be to check for a nil title and return the previous functionality's result. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1414) Facter acceptance test facts/windows.rb doesn't account for Windows 10 / Windows Server 2016
Title: Message Title Glenn Sarti commented on FACT-1414 Re: Facter acceptance test facts/windows.rb doesn't account for Windows 10 / Windows Server 2016 Local acceptance tests passed for Win10 x86/x64 and 2012R2 x64 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title Kylo Ginsberg assigned an issue to Thomas Hallgren Puppet / PUP-6321 undef in custom type autorequire value causes error in Puppet 4.5.0 Change By: Kylo Ginsberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title Kylo Ginsberg commented on PUP-6321 Re: undef in custom type autorequire value causes error in Puppet 4.5.0 I used the reproducer above (thanks Chris Price!) after doing a puppet module install puppet-archive, and git bisected this down to https://github.com/puppetlabs/puppet/commit/eff7ac6fd73adb11ba98fb993c29fac69b473297. Thomas Hallgren: can you take a look at this? I'm hoping you'll have more context than I about why that commit would lead to this behavior. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6321 undef in custom type autorequire value causes error in Puppet 4.5.0 Change By: Kylo Ginsberg Scrum Team: Client Platform Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6259) File resource no_proxy behavior is ignored
Title: Message Title
Felix Frank commented on PUP-6259
Re: File resource no_proxy behavior is ignored
Eh, that would probably be gratuitous. I had so far assumed that this was a server certificate issue, but if the proxy returns 403s, that is the reason for your issues of course, and has little to do with other specifics.
It's a long shot, but can you try and run your resource through puppet apply?
puppet apply -e "file {'/var/opt/foo/client.config': ensure => present, source => 'https://files.internal/client.config', }"
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6329) puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Title: Message Title
Greg Larkin created an issue
Puppet / PUP-6329
puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Issue Type:
Bug
Assignee:
Kylo Ginsberg
Components:
Client
Created:
2016/05/19 3:53 PM
Priority:
Normal
Reporter:
Greg Larkin
I created a file named /tmp/foo/fo©.txt with some text in it. Then I wrote the following manifest and invoked it with puppet apply:
file { '/Users/glarkin/tmp':
source => '/private/tmp/foo',
ensure => directory,
Jira (PDB-136) Support for Oracle backend
Title: Message Title Susannah Axelrod updated an issue PuppetDB / PDB-136 Support for Oracle backend Change By: Susannah Axelrod Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2727) Update ezbake's bootstrap.cfg to match dev-resources
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2727 Update ezbake's bootstrap.cfg to match dev-resources Issue Type: Bug Assignee: Unassigned Created: 2016/05/19 2:28 PM Priority: Normal Reporter: gepetto-bot In commit 4334e5a77d99265e8ae147cc0bd05e8a790dc952, bootstrap.cfg in dev-resources was updated but resources/ext/config/bootstrap.cfg was not, which broke startup when the pdb-status service was not available. This commit updates the bootstrap.cfg in resources to match. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6328) Parsing of strings changes with puppet 4.5.0
Title: Message Title Reinhard Vicinus created an issue Puppet / PUP-6328 Parsing of strings changes with puppet 4.5.0 Issue Type: Bug Affects Versions: PUP 4.5.0 Assignee: Unassigned Components: Language Created: 2016/05/19 2:15 PM Priority: Normal Reporter: Reinhard Vicinus With Puppet 4.4.2 the following two code snippets work both: puppet apply -e 'notice(ubuntu)' Notice: Scope(Class[main]): ubuntu
Jira (FACT-1419) Add a 'privileged' element to the identity fact
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1419 Add a 'privileged' element to the identity fact Change By: Michael Smith Status: Ready for CI Test Assignee: Michal Ruzicka qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6320) Bad message when passing zero sized array where non empty array is required
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-6320 Bad message when passing zero sized array where non empty array is required Change By: Sean Griffin Assignee: qa Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6319) Bad message when passing zero sized hash where non empty hash is required
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-6319 Bad message when passing zero sized hash where non empty hash is required Change By: Sean Griffin Assignee: qa Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1427) identity.privileged fact is not set on zlinux based sles11
Title: Message Title John Duarte commented on FACT-1427 Re: identity.privileged fact is not set on zlinux based sles11 Hrm.. This doesn't work for me on sles11-x86_64 either. Maybe there is something I am missing. Reproduction steps Check out facter at sha a91b01e Run test using acceptance rake task against puppet-agent 1.5.0 SHA=1.5.0 TEST_TARGET=sles11-64a TESTS='tests/facts/sles.rb' be rake ci:test:aio Results Failed Tests Cases: Test Case tests/facts/sles.rb reported: # Actual: ""> Add Comment
Jira (FACT-1426) Triage acceptance failures on zlinux (s390x) sles-11
Title: Message Title John Duarte updated an issue Facter / FACT-1426 Triage acceptance failures on zlinux (s390x) sles-11 Change By: John Duarte Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1426) Triage acceptance failures on zlinux (s390x) sles-11
Title: Message Title John Duarte updated an issue Facter / FACT-1426 Triage acceptance failures on zlinux (s390x) sles-11 Change By: John Duarte Sprint: Client 2016-06-01 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1426) Triage acceptance failures on zlinux (s390x) sles-11
Title: Message Title John Duarte updated an issue Facter / FACT-1426 Triage acceptance failures on zlinux (s390x) sles-11 Change By: John Duarte Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1426) Triage acceptance failures on zlinux (s390x) sles-11
Title: Message Title John Duarte updated an issue Facter / FACT-1426 Triage acceptance failures on zlinux (s390x) sles-11 Change By: John Duarte Scope Change Reason: test failures on sles11 on zlinux Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6327) Puppet module tool should handle invalid paths better
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-6327
Puppet module tool should handle invalid paths better
Change By:
Ben Ford
When you install a module that contains file paths valid on the platform that it was built on, but not the platform it's being installed on, PMT fails with an inscrutable error. In hindsight, it's obvious, but the error messaging could be better about what went wrong.{code}PS C:\Users\Administrator> puppet module install trlinkin/domain_membershipNotice: Preparing to install into C:/ProgramData/PuppetLabs/code/environments/production/modules ...Notice: Downloading from https://forgeapi.puppetlabs.com ...Failed to add /C=US/O=GeoTrust Inc./CN=GeoTrust Global CAFailed to add /C=US/O=GeoTrust Inc./CN=GeoTrust Global CAFailed to add /C=US/O=GeoTrust Inc./CN=GeoTrust Global CAFailed to add /C=US/O=GeoTrust Inc./CN=GeoTrust Global CAFailed to add /C=US/O=GeoTrust Inc./CN=GeoTrust Global CAFailed to add /C=US/O=GeoTrust Inc./CN=GeoTrust Global CAFailed to add /C=US/O=GeoTrust Inc./CN=GeoTrust Global CAFailed to add /C=US/O=GeoTrust Inc./CN=GeoTrust Global CAError: Could not install package Package attempted to install file into "trlinkin-domain_membership-1.1.0/:78" under "C:/Users/ADMINI~1/AppData/Local/Temp/cache/tmp20160519-2896-bnlxhg".{code}The problem is that {{:78}} is an invalid filename. The actual error is something more like {{mkdir : The given path's format is not supported.}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google
Jira (PUP-6327) Puppet module tool should handle invalid paths better
Title: Message Title Ben Ford created an issue Puppet / PUP-6327 Puppet module tool should handle invalid paths better Issue Type: Bug Assignee: Unassigned Components: PMT Created: 2016/05/19 10:46 AM Priority: Normal Reporter: Ben Ford When you install a module that contains file paths valid on the platform that it was built on, but not the platform it's being installed on, PMT fails with an inscrutable error. In hindsight, it's obvious, but the error messaging could be better about what went wrong. PS C:\Users\Administrator> puppet module install trlinkin/domain_membership Notice: Preparing to install into C:/ProgramData/PuppetLabs/code/environments/pr oduction/modules ...
Jira (FACT-1426) Triage acceptance failures on zlinux (s390x) sles-11
Title: Message Title John Duarte commented on FACT-1426 Re: Triage acceptance failures on zlinux (s390x) sles-11 tests/facts/ruby.rb and tests/facts/sles.rb errors are due to lack of support in the tests for s390x architecture. Further exploration of the tests/facts/sles.rb revealed FACT-1427 The tests/options/custom_facts.rb failure is erroneous due to the ruby path resolving to the system ruby rather than the vendored ruby during test execution. This test passes when run manually on the zlinux sles-11 instance. The failure is probably a side effect of not using the automated rake task to properly setup the testing environment. The incorrect ruby path is also the cause of the load error in tests/load_libfacter.rb Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title Susan McNerney updated an issue Puppet / PUP-6258 Update Puppet OID lists to add new authorized extensions Change By: Susan McNerney Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1423) Ubuntu tests not run on Ubuntu
Title: Message Title Sean Griffin assigned an issue to qa Facter / FACT-1423 Ubuntu tests not run on Ubuntu Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6320) Bad message when passing zero sized array where non empty array is required
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-6320 Bad message when passing zero sized array where non empty array is required Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6319) Bad message when passing zero sized hash where non empty hash is required
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-6319 Bad message when passing zero sized hash where non empty hash is required Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6322) EPP and scope context
Title: Message Title
Henrik Lindberg commented on PUP-6322
Re: EPP and scope context
Have to think about this as it is like calling an external function and that function has access to all your local variables. That is truly horrible and it leads to problems like not being able to reuse templates. It is unspecific, not robust, not type safe, impure, (I can go on about this). It is ok for inline epp as it works like a lambda, it is embedded in the context it gets variables from. With external EPP from a file it is like an external function.
I do recognize the pain and I would like to help making it easier as you now manually have to assemble all variables and give them to the template - or access them via fully qualified names.
Note that there is new syntax that makes it easy to import a bunch of names at the same time from another namespace.
[$param1, $param2, $param3] = Class[foo::bar::fee::fum]
Would give you local variables $param1... etc. from $foo::bar::fee::fum::param1, $foo::bar::fee::fum::param2, etc. Which saves a lot of typing.
Ideally, a template should not pull anything at all from anywhere and only rely on what is given to it, and its parameters should be declared and typed. Then instead of empty strings, wrong data type, etc. will be caught automatically instead of just the "wrong text" being produced.
Currently you have to supply arguments as a hash. Maybe we can do something about that so that becomes easy(er/ish).
You can always do this:
class foo($a= 10, $b=20) {
}
include foo
notice inline_epp(@(EPP), {context => Class[foo]})
Jira (PUP-6324) DNF provider cannot update packages (install command will not update)
Title: Message Title
Peter Souter commented on PUP-6324
Re: DNF provider cannot update packages (install command will not update)
Some background reading as to why I picked update for yum and upgrade for dnf:
In yum both `upgrade` and `update` can be used to update packages `yum upgrade` == `yum --obsoletes update` Quote the DNF docs: Yum does this if its obsoletes config option is enabled but the behavior is not properly documented and can be harmful. So we'll stick with the safter option If a user wants to remove obsoletes, they can use { :install_options => '--obsoletes' } More detail here: https://bugzilla.redhat.com/show_bug.cgi?id=1096506
If any RHEL peeps are reading this and thing my assumptions are wrong, feel free to PR, I just went for the least destructive option
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1427) identity.privileged fact is not set on zlinux based sles11
Title: Message Title
John Duarte created an issue
Facter / FACT-1427
identity.privileged fact is not set on zlinux based sles11
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/05/19 9:52 AM
Priority:
Normal
Reporter:
John Duarte
Using puppet-agent at sha 6719e02 containing facter at sha be447f8, the identity fact does not contain a privileged value on sles11 running on zlinux.
identity fact on sles 11 running on zlinux
As root
# facter identity
{
gid => 0,
group => "root",
Jira (PDB-2715) Smoke test packages (PDB 4.1.0)
Title: Message Title Andrew Roetker commented on PDB-2715 Re: Smoke test packages (PDB 4.1.0) Good on Ubuntu Xenial using nightly puppetserver packages Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6324) DNF provider cannot update packages (install command will not update)
Title: Message Title William Hopper commented on PUP-6324 Re: DNF provider cannot update packages (install command will not update) A few useful links: Yum manuals for RedHat 5, 6, and 7: https://access.redhat.com/solutions/9934 DNF reference: http://www.liquidweb.com/kb/dnf-dandified-yum-command-examples-install-remove-upgrade-and-downgrade/ It looks like every version of Yum since RedHat 6 uses yum update package_name, while DNF uses dnf upgrade package_name. In DNF, update has been deprecated in favor of upgrade. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4742) Bring semantic_puppet library into Puppet
Title: Message Title Henrik Lindberg commented on PUP-4742 Re: Bring semantic_puppet library into Puppet This ticket has several related tickets (linked here, and in PUP-6240). Part of the work is already done, there is a PR with a removal (? or is there more in it?). Part of the task is figuring out what to do, and possibly close/resolve some of the tickets. The gem (that we want) is in the puppet agent for puppet 4.5.0. Is the gem in the gemspec so that development / running from source works ok? Is the PR with the removal ok (? does it remove everything needed, are there additional things to do?) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4742) Bring semantic_puppet library into Puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Henrik Lindberg Fix Version/s: PUP 4.5.1 Fix Version/s: PUP 4.6.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6088) Make TypeParser#interpret public API for Puppet Strings use
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6088 Make TypeParser#interpret public API for Puppet Strings use Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4742) Bring semantic_puppet library into Puppet
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6326) mount native type use systemd mount units rather than fstab entry
Title: Message Title Pat Riehecky created an issue Puppet / PUP-6326 mount native type use systemd mount units rather than fstab entry Issue Type: New Feature Affects Versions: PUP 4.5.0 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/05/19 9:19 AM Environment: Linux with systemd Priority: Normal Reporter: Pat Riehecky Can the mount native type be extended to allow for the creation of systemd.mount units rather than /etc/fstab entries? https://www.freedesktop.org/software/systemd/man/systemd.mount.html
Jira (PUP-6325) mount native type support /etc/fstab.d/
Title: Message Title Pat Riehecky created an issue Puppet / PUP-6325 mount native type support /etc/fstab.d/ Issue Type: Improvement Affects Versions: PUP 4.5.0 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/05/19 9:16 AM Environment: Linux with linux-utils >= 2.19 Priority: Normal Reporter: Pat Riehecky To help separate out various managed mounts, it would be helpful if I could elect to place a specific mount into /etc/fstab.d/ Ideally I'd like to be able to group some mounts together - ie all mounts for mywebapp - into a single file under /etc/fstab.d/ to help encapsulate the specific reason for the mounts rather than mixing them in with system mounts or mounts for another purpose.
Jira (PUP-6311) Define where XPP files should be written, and how resolution works
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-6311 Define where XPP files should be written, and how resolution works Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6324) DNF provider cannot update packages (install command will not update)
Title: Message Title William Hopper updated an issue Puppet / PUP-6324 DNF provider cannot update packages (install command will not update) Change By: William Hopper Affects Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6220) Add TypeSet type to the Puppet Type System
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-6220 Add TypeSet type to the Puppet Type System Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6240) Deprecate old semantic version implementation
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6240 Deprecate old semantic version implementation Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2715) Smoke test packages (PDB 4.1.0)
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-2715 Smoke test packages (PDB 4.1.0) Change By: Ryan Senior Assignee: Wyatt Alt Ryan Senior Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2715) Smoke test packages (PDB 4.1.0)
Title: Message Title Ryan Senior commented on PDB-2715 Re: Smoke test packages (PDB 4.1.0) Good to go on CentOS7 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6259) File resource no_proxy behavior is ignored
Title: Message Title Patrick Cable commented on PUP-6259 Re: File resource no_proxy behavior is ignored The proxy works fine with external sources. The problem we run into is that there are internal sources, that are defined in $no_proxy, that should not be proxied. If the internal sources hit the web proxy, the web proxy will return a 403. I can try to set up an internal puppet forge repository to see how the behavior works with puppet module install, but I can't get to that today unfortunately. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1426) Triage acceptance failures on zlinux (s390x) sles-11
Title: Message Title John Duarte created an issue Facter / FACT-1426 Triage acceptance failures on zlinux (s390x) sles-11 Issue Type: Task Assignee: John Duarte Created: 2016/05/19 7:52 AM Priority: Normal Reporter: John Duarte The following facter acceptance tests fail on sles-11 instance on zlinux s390x using puppet-agent at sha 6719e02: tests/facts/ruby.rb tests/facts/sles.rb tests/options/custom_facts.rb tests/load_libfacter.rb The beaker error report is as follows Test Case tests/facts/ruby.rb reported: # Test Case tests/facts/sles.rb reported: #
Jira (PUP-6324) DNF provider cannot update packages (install command will not update)
Title: Message Title
Peter Souter updated an issue
Puppet / PUP-6324
DNF provider cannot update packages (install command will not update)
Change By:
Peter Souter
tl;dr ` * dnf install ` * will not install a newer version of a package if it's already installed: {code}[root@fedora-22-x64 vagrant]# /bin/dnf -y install cockpitLast metadata expiration check performed 0:18:07 ago on Thu May 19 13:40:06 2016.Package cockpit-0.67-2.fc22.x86_64 is already installed, skipping.Dependencies resolved.Nothing to do.Complete!{code} Full log of proof:{code} [root@fedora-22-x64 vagrant]# rpm -qa cockpitcockpit-0.67-2.fc22.x86_64[root@fedora-22-x64 vagrant]# dnf list cockpitLast metadata expiration check performed 0:17:14 ago on Thu May 19 13:40:06 2016.Installed Packagescockpit.x86_64 0.67-2.fc22 @SystemAvailable Packagescockpit.src0.106-1.fc22 group_cockpit-cockpit-previewcockpit.x86_64 0.106-1.fc22 group_cockpit-cockpit-preview[root@fedora-22-x64 vagrant]# puppet resource package cockpitpackage { 'cockpit': ensure => '0.67-2.fc22',}[root@fedora-22-x64 vagrant]# puppet resource package cockpit ensure=latest --debugDebug: Prefetching dnf resources for packageDebug: Executing: '/bin/rpm --version'Debug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''Debug: Executing: '/bin/dnf check-update'Debug: /Package[cockpit]/ensure: cockpit "0.67-2.fc22" is installed, latest is "0:0.94-1.fc22"Debug: Package[cockpit](provider=dnf): Ensuring => latestDebug: Executing: '/bin/dnf -d 0 -e 1 -y install cockpit'Notice: /Package[cockpit]/ensure: ensure changed '0.67-2.fc22' to '0:0.94-1.fc22'Debug: Finishing transaction 36208880Debug: Storing stateDebug: Stored state in 0.01 secondsDebug: Executing: '/bin/rpm -q cockpit --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'package { 'cockpit': ensure => '0.67-2.fc22',}[root@fedora-22-x64 vagrant]# /bin/dnf -y install cockpitLast metadata expiration check performed 0:18:07 ago on Thu May 19 13:40:06 2016.Package cockpit-0.67-2.fc22.x86_64 is already installed, skipping.Dependencies resolved.Nothing to do.Complete![root@fedora-22-x64 vagrant]# /bin/dnf -y upgrade cockpitLast metadata expiration check performed 0:18:26 ago on Thu May 19 13:40:06 2016.Dependencies resolved.== Package Arch Version Repository Size==Installing: cockpit-networkmanager noarch 0.106-1.fc22 group_cockpit-cockpit-preview42 k cockpit-storaged noarch 0.106-1.fc22 group_cockpit-cockpit-preview52 k device-mapper-multipath x86_64 0.4.9-73.fc22
Jira (PUP-6324) DNF provider cannot update packages (install command will not update)
Title: Message Title Peter Souter created an issue Puppet / PUP-6324 DNF provider cannot update packages (install command will not update) Issue Type: Bug Assignee: Unassigned Created: 2016/05/19 7:12 AM Priority: Normal Reporter: Peter Souter tl;dr `dnf install` will not install a newer version of a package if it's already installed: Full log of proof: [root@fedora-22-x64 vagrant]# rpm -qa cockpit cockpit-0.67-2.fc22.x86_64
Jira (PUP-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title Kevin Corcoran commented on PUP-6258 Re: Update Puppet OID lists to add new authorized extensions Nathaniel Smith - Cool, thanks. We'll need some documentation on those new extensions - what they represent / how they should be used. I imagine that is part of what you're working on right now, yeah? Tangential question: is there any reasonable way for us to share these between the two codebases instead of defining them twice? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title Fabien Wernli commented on FACT-1356 Re: External facts should be able to return structured data For consistency this should also allow using YAML. One easy solution would be to check extension and executable bit Examples: 1. executable foo.yaml → ./foo.yaml | parse_yaml 2. not executable bar.json → parse_json bar.json 3. executable bar → ./bar | parse_key_value etc. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Alex Box commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir +1 for James Kenney use cases; please don't remove the filebucket! In real world environments the guaranteed path to recovery and auditing convenience that it provides is very important. It's very easy to find/grep/diff while troubleshooting. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1419) Add a 'privileged' element to the identity fact
Title: Message Title James Stocks updated an issue Facter / FACT-1419 Add a 'privileged' element to the identity fact Change By: James Stocks QA Risk Assessment: Medium QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1425) Facter 3.1.7 incorrectly identifies itself as version 3.2.0
Title: Message Title Christoph Schug created an issue Facter / FACT-1425 Facter 3.1.7 incorrectly identifies itself as version 3.2.0 Issue Type: Bug Affects Versions: FACT 3.1.7 Assignee: Unassigned Components: Community Created: 2016/05/19 2:30 AM Priority: Normal Reporter: Christoph Schug Facter 3.1.7 incorrectly identifies itself as version 3.2.0. Code build from the 3.1.7 release tarball on Github, facter-3.1.7.tar.gz (SHA256 ebb703068daaf6ff880be8d14898709ccea44288874450e25a887ecb0a5e04ae) $ facter facterversion 3.2.0
Jira (PUP-6323) Support tdnf package provider for VMware PhotonOS
Title: Message Title Gareth Rushgrove created an issue Puppet / PUP-6323 Support tdnf package provider for VMware PhotonOS Issue Type: Bug Assignee: Unassigned Created: 2016/05/19 12:55 AM Priority: Normal Reporter: Gareth Rushgrove PhotonOS is a RPM derivative OS from VMware. However it does not use yum, nor the newer DNF. It uses a DNF compatible application called TDNF (https://github.com/vmware/tdnf). Some details from http://www.vcritical.com/2015/06/quickly-update-to-docker-1-6-on-photon-by-using-tdnf/ TDNF is a VMware innovation that offers DNF-compatible package management without a massive Python footprint. Add Comment
Jira (PUP-6259) File resource no_proxy behavior is ignored
Title: Message Title Felix Frank commented on PUP-6259 Re: File resource no_proxy behavior is ignored How does external HTTPS work in this scenario? I would assume the proxy also interferes with access to, say, forge.puppet.com. Can you puppet module install things on this machine? How are the "global" environment variables managed? Is it certain that the Puppet agent uses them? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
