Jira (PUP-1271) puppet ca list --all fails with "Error: The certificate retrieved from the master does not match the agent's private key."
Title: Message Title Jacky Leung commented on PUP-1271 Re: puppet ca list --all fails with "Error: The certificate retrieved from the master does not match the agent's private key." I am having this issue too Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6777) regression: incompatible character encodings: UTF-8 and ASCII-8BIT
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6777 regression: incompatible character encodings: UTF-8 and ASCII-8BIT Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6772) Decision - Support extended UTF-8 characters in tags?
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6772 Decision - Support extended UTF-8 characters in tags? Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1384) Remove deprecated APIs necessitated by Server 2003 compat
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1384 Remove deprecated APIs necessitated by Server 2003 compat Change By: Michael Smith Status: Ready for CI Test Assignee: Michael Smith qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6794) acceptance: Sensitive inside Array, Hash, Object
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-6794 acceptance: Sensitive inside Array, Hash, Object Change By: Eric Thompson Resolution: Cannot Reproduce Assignee: Eric Thompson qa Status: In Progress Closed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6245) Acceptance: fix zpool create zone test
Title: Message Title John Duarte updated an issue Puppet / PUP-6245 Acceptance: fix zpool create zone test Change By: John Duarte QA Risk Assessment: High Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6245) Acceptance: fix zpool create zone test
Title: Message Title John Duarte updated an issue Puppet / PUP-6245 Acceptance: fix zpool create zone test Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6245) Acceptance: fix zpool create zone test
Title: Message Title John Duarte updated an issue Puppet / PUP-6245 Acceptance: fix zpool create zone test Change By: John Duarte QA Risk Assessment Reason: Functional expectation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6779) acceptance: puppet generate
Title: Message Title Eric Thompson commented on PUP-6779 Re: acceptance: puppet generate so i should be able to trigger a compilation issue via running the agent in the environment with the extra attribute? and then running it in the environment without the attribute in the same type? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1467) Add Windows computer_sid fact
Title: Message Title Ethan Brown commented on FACT-1467 Re: Add Windows computer_sid fact Note that our internal management module at https://github.com/puppetlabs/puppetlabs-modules/blob/f969898d4337b80b983a0f654fc41dc8f2934f32/site/profile/manifests/jenkins/slave/windows.pp#L55 harcodes the value Administrator, which suffers from the problem described in this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6779) acceptance: puppet generate
Title: Message Title Henrik Lindberg commented on PUP-6779 Re: acceptance: puppet generate Without generate; if your manifest references an attribute that does not exist then it should stop the compilation. If a version of the type (not having the attribute) is loaded first, it will be sticky. The "pluginsync" does not play a role in the compilation. On the agent side I am not sure if there has ever been an environment isolation problem - not sure how it gets rid of loaded ruby code though when running as a daemon. If not running as a daemon issues with environment isolation cannot occur agent side since it would always load the logic fresh. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6612) Scope effort for i18n string externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6612 Scope effort for i18n string externalization Change By: Geoff Nichols Sprint: AP Grooming Top 11-20 10 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6779) acceptance: puppet generate
Title: Message Title Eric Thompson commented on PUP-6779 Re: acceptance: puppet generate Henrik Lindberg still doesn't blow up as pluginsync somehow rectifies the difference. it's unclear which it thinks is authoritative: [root@vbhiovend7z1rfv environments]# puppet agent -t --server $(hostname -f) --environment pcore_generate_env_isolation_29hjrd6l Info: Using configured environment 'pcore_generate_env_isolation_29hjrd6l' Info: Retrieving pluginfacts Info: Retrieving plugin Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/type/conflicting.rb]/content: --- /opt/puppetlabs/puppet/cache/lib/puppet/type/conflicting.rb 2016-10-16 14:01:02.396561634 -0700 +++ /tmp/puppet-file20161016-21693-2sx7b6 2016-10-16 14:06:39.860569680 -0700 @@ -1,3 +1,4 @@ Puppet::Type.newtype(:conflicting) do
Jira (PUP-6188) Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6188 Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8 Change By: Geoff Nichols Sprint: AP 2016-11-02 Holding Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6761) [SPIKE] Find a workflow for POT file generation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6761 [SPIKE] Find a workflow for POT file generation Change By: Geoff Nichols Summary: [ SPIKE - ] Find a workflow for POT file generation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6762) [SPIKE] How and when do we get PO files from Transifex?
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6762 [SPIKE] How and when do we get PO files from Transifex? Change By: Geoff Nichols Summary: [ SPIKE - ] How and when do we get PO files from Transifex? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6762) SPIKE - How and when do we get PO files from Transifex?
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6762 SPIKE - How and when do we get PO files from Transifex? Change By: Geoff Nichols Sprint: AP 2016-11-02 Holding Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6761) SPIKE - Find a workflow for POT file generation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6761 SPIKE - Find a workflow for POT file generation Change By: Geoff Nichols Sprint: AP 2016-11-02 Holding Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6779) acceptance: puppet generate
Title: Message Title Eric Thompson commented on PUP-6779 Re: acceptance: puppet generate Henrik Lindberg should this blow up without generate [root@vbhiovend7z1rfv environments]# cat pcore_generate_env_isolation_jtg1fla5/modules/conflict/lib/puppet/type/conflicting.rb Puppet::Type.newtype(:conflicting) do newparam :name, :namevar => true newparam :other end [root@vbhiovend7z1rfv environments]# cat pcore_generate_env_isolation_njugd5la/modules/conflict/lib/puppet/type/conflicting.rb Puppet::Type.newtype(:conflicting) do newparam :name, :namevar => true end
Jira (PUP-6794) acceptance: Sensitive inside Array, Hash, Object
Title: Message Title Eric Thompson commented on PUP-6794 Re: acceptance: Sensitive inside Array, Hash, Object i can put it in the test for now with an expect_failure() and assert on what we think it might do later... but i'm thinking we defer this type of test against Sensitive Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6791) acceptance: add then and other functions to calling_all_functions test
Title: Message Title
Eric Thompson commented on PUP-6791
Re: acceptance: add then and other functions to calling_all_functions test
when the test abstraction receives a lambda it places it after the function call with an optional argument. the argument is placed before the function (so the function is called as a method as a member of the argument). so it could do something like
$x.lest |$y| {notice $y}
but it's not possible to do something like
lest($x) || |$y| {notice $y}
, without boiling the ocean around the rest of the test.
this could obviously use some work, like using templates for the manifest production, and make the abstraction more extensible/open, like what we've done with the puppet_resource_testing lib (see the sensitive and binary data type tests)
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6794) acceptance: Sensitive inside Array, Hash, Object
Title: Message Title Henrik Lindberg commented on PUP-6794 Re: acceptance: Sensitive inside Array, Hash, Object Not brilliant as suspected. Also note that doing the same from an agent will behave differently. Question is what it should do... Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6794) acceptance: Sensitive inside Array, Hash, Object
Title: Message Title
Eric Thompson commented on PUP-6794
Re: acceptance: Sensitive inside Array, Hash, Object
[root@vbhiovend7z1rfv ~]# puppet apply -e '$sens = Sensitive("lhone") host{"localhost2": ip => "127.0.0.1", host_aliases
=> [$sens, "lhtwo"]}'
Notice: Compiled catalog for vbhiovend7z1rfv.delivery.puppetlabs.net in environment production in 0.13 seconds
Notice: /Stage[main]/Main/Host[localhost2]/ensure: created
Notice: Applied catalog in 0.07 seconds
[root@vbhiovend7z1rfv ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
127.0.0.1 updates.puppetlabs.com
127.0.0.1 localhost2 Sensitive [value redacted] lhtwo
Jira (PUP-6822) Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist
Title: Message Title
Erik Hansen created an issue
Puppet / PUP-6822
Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/10/16 9:36 AM
Priority:
Normal
Reporter:
Erik Hansen
Linux agents don't seem to have this issue, for example:
]# puppet apply -e 'service {"notaservice": ensure => "stopped", enable => false,}'
Notice: Compiled catalog for pe-201620-master.example.com in environment production in 0.12 seconds
Notice: Applied catalog in 0.33 seconds
However, on Windows, an attempt to apply the same resource gives:
Jira (PUP-6791) acceptance: add then and other functions to calling_all_functions test
Title: Message Title Henrik Lindberg commented on PUP-6791 Re: acceptance: add then and other functions to calling_all_functions test Not sure what that means... - is it that you must pass a lambda/block to it? You can actually pass a ruby lambda/block if you like - that works just as well as having the call in a manifest with a puppet lambda. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6511) Add support for lookup.conf (version 5)
Title: Message Title Henrik Lindberg commented on PUP-6511 Re: Add support for lookup.conf (version 5) I take back my idea of making the entry's datadir relative a global datadir - that is just confusing. What you proposed; that datadir is in a defaults (and relative to "component" root), and that if used in an entry then that value is used as is. The overriding datadir in an entry is also relative to the "component" root. If a default datadir is missing, we can have a "factory default" of data (which I think is also the default in the hiera.yaml v4 format) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6821) binary_file() file not found: error message unclear
Title: Message Title Henrik Lindberg commented on PUP-6821 Re: binary_file() file not found: error message unclear Bad filesystem day? Funky quotes on the CLI ? Your absolute path was perhaps not absolute after all? Typo? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6794) acceptance: Sensitive inside Array, Hash, Object
Title: Message Title
Henrik Lindberg commented on PUP-6794
Re: acceptance: Sensitive inside Array, Hash, Object
titles of resources cannot be sensitive (at least not in this version)
you cannot unwrap what is not sensitive
Needs to be tested with an attribute of a resource type that supports array values. The title is not one of those since it will iterate over the content and create one resource per entry.
Given that there is a sometype with an attribute attr:
sometype { 'test-array': attr => [ Sensitive('heimlish mitteilung'), 'non secret message' ] }
sometype { 'test-hash': attr => { s_key => Sensitive('heimlish mitteilung'), ns_key => 'non secret message' } }
The sensitive values should not be leaked. Not when compiling, and not when agent operates or reports resource state to the server.
(I think the implementation most likely is flawed and that the sensitive values are not honoured). In the current implementation to get the wanted behavior you must (most likely) only use a Sensitive value as the value directly assigned to an attribute. I suspect that if they are nested in a structure we will see undefined behavior.
A resource type designed for the purpose of testing this may have to be designed.
Ping Adrien Thebo
Add Comment
Jira (PUP-6794) acceptance: Sensitive inside Array, Hash, Object
Title: Message Title
Eric Thompson commented on PUP-6794
Re: acceptance: Sensitive inside Array, Hash, Object
Henrik Lindberg i'll try more like this, but is this what you had in mind? anything seem wrong in the errors?
[root@e8lqfhdmeavh35j ~]# puppet apply -e '$sens = Sensitive("blah") notify{["one", "${sens}"]:}'
Notice: Compiled catalog for e8lqfhdmeavh35j.delivery.puppetlabs.net in environment production in 0.08 seconds
Notice: one
Notice: /Stage[main]/Main/Notify[one]/message: defined 'message' as 'one'
Notice: Sensitive [value redacted]
Notice: /Stage[main]/Main/Notify[Sensitive [value redacted]]/message: defined 'message' as 'Sensitive [value redacted]'
Notice: Applied catalog in 0.10 seconds
[root@e8lqfhdmeavh35j ~]# puppet apply -e '$sens = Sensitive("blah") notify{["one", "${sens.unwrap}"]:}'
Notice: Compiled catalog for e8lqfhdmeavh35j.delivery.puppetlabs.net in environment production in 0.08 seconds
