Jira (PUP-6363) The puppet master should accept reports submitted for an environment that doesn't exist
Title: Message Title Ryan Whitehurst updated an issue Puppet / PUP-6363 The puppet master should accept reports submitted for an environment that doesn't exist Change By: Ryan Whitehurst Issue Type: Bug Improvement 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-6363) The puppet master should accept reports submitted for an environment that doesn't exist
Title: Message Title Henrik Lindberg commented on PUP-6363 Re: The puppet master should accept reports submitted for an environment that doesn't exist Ping Kylo Ginsberg and Chris Price 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-6364) On AIX, an already installed package is not updated when using "ensure => latest"
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6364 On AIX, an already installed package is not updated when using "ensure => latest" Change By: Henrik Lindberg Scrum Team: Client Platform 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-6159) OSX Passwords not setting under Puppet 4.4.1
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6159 OSX Passwords not setting under Puppet 4.4.1 Change By: Eric Thompson Release Notes Summary: directoryservice user provider was failing to set password and salt under certain circumstances on OSX Release Notes: Bug Fix 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-1408) Facter productname issue on Solaris
Title: Message Title John Duarte assigned an issue to Nerissa Lemon Facter / FACT-1408 Facter productname issue on Solaris Change By: John Duarte Assignee: qa Nerissa Lemon 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 commented on FACT-1426 Re: Triage acceptance failures on zlinux (s390x) sles-11 The tests/facts/ruby.rb and tests/facts/sles.rb errors are also present on the sles-12 instance. The pending PR should address these on both platforms. 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-6159) OSX Passwords not setting under Puppet 4.4.1
Title: Message Title
Eric Thompson commented on PUP-6159
Re: OSX Passwords not setting under Puppet 4.4.1
validated on osx1010 at master puppet-agent SHA: e741b4854aa60b474c0fda636f9b9ffc40c9ffbe
vtpzzcb2ekgnuu9:~ root# puppet apply test.pp
Notice: Compiled catalog for vtpzzcb2ekgnuu9.delivery.puppetlabs.net in environment production in 0.08 seconds
Notice: /Stage[main]/Main/User[test]/salt: salt changed '33699bb4ed05d8a31530889491c4b764e3eeaeb66634449feab43f6a3cd14873' to '62133b77a7aeecf506ffe99d064b3f8c068344de0a619a573a871f2fd6fe9eaf'
Notice: /Stage[main]/Main/User[test]/iterations: iterations changed '38461' to '46948'
Notice: Applied catalog in 9.61 seconds
vtpzzcb2ekgnuu9:~ root# cat test.pp
user { 'test':
ensure => 'present',
comment
Jira (PUP-6364) On AIX, an already installed package is not updated when using "ensure => latest"
Title: Message Title
Geoff Nichols updated an issue
Puppet / PUP-6364
On AIX, an already installed package is not updated when using "ensure => latest"
Change By:
Geoff Nichols
On AIX (reported on 7.1 TL3 SP5), when using "ensure => latest" on a package, puppet does not install the latest version available if the package (in this case, an older version) is already installed. If specifying a version number (i.e. 6.0.0.5), the package is updated to this version.Below is a sample output of the command puppet uses to produce a list of packages and their version numbers:{code}#/usr/sbin/installp -L -d .EMC:EMC.CELERRA.aix.rte:6.0.0.5::I:C:b:EMC CELERRA AIX Support Software0::EMC:EMC.CELERRA.iscsi.rte:6.0.0.5::I:C:b:EMC CELERRA iSCSI Support Software0::EMC:EMC.CLARiiON.aix.rte:6.0.0.5::I:C:b:EMC CLARiiON AIX Support Software0::EMC:EMC.CLARiiON.fcp.MPIO.rte:6.0.0.5::I:C:b:EMC CLARiiON FCP MPIO Support Software0::EMC:EMC.CLARiiON.fcp.rte:6.0.0.5::I:T:b:EMC CLARiiON FCP Support Software0::EMC:EMC.CLARiiON.iscsi.rte:6.0.0.5::I:C:b:EMC CLARiiON iSCSI Support Software0::EMC:EMC.INVISTA.aix.rte:6.0.0.5::I:C:b:EMC INVISTA AIX Support Software0::EMC:EMC.INVISTA.fcp.MPIO.rte:6.0.0.5::I:C:b:EMC INVISTA FCP MPIO Support Software0::EMC:EMC.INVISTA.fcp.rte:6.0.0.5::I:T:b:EMC INVISTA FCP Support Software0::EMC:EMC.Symmetrix.aix.rte:6.0.0.5::I:C:b:EMC Symmetrix AIX Support Software0::EMC:EMC.Symmetrix.fcp.MPIO.rte:6.0.0.5::I:T:b:EMC Symmetrix FCP MPIO Support Software0::EMC:EMC.Symmetrix.fcp.rte:6.0.0.5::I:T:b:EMC Symmetrix FCP Support Software0::EMC:EMC.Symmetrix.iscsi.rte:6.0.0.5::I:T:b:EMC Symmetrix iSCSI Support Software0::EMC:EMC.XtremIO.aix.rte:6.0.0.5::I:T:b:EMC XtremIO AIX Support Software0::EMC:EMC.XtremIO.fcp.MPIO.rte:6.0.0.5::I:T:b:EMC XtremIO FCP MPIO Support Software0::EMC:EMC.XtremIO.fcp.rte:6.0.0.5::I:T:b:EMC XtremIO FCP Support Software0:: {code} So the version available to install is 6.0.0.5, version 6.0.0.3 is currently installed, but the newer version is not installed when using ensure => latest. When specifying 6.0.0.5 as the version, the package is updated. {code}
Add Comment
Jira (PUP-6159) OSX Passwords not setting under Puppet 4.4.1
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-6159
OSX Passwords not setting under Puppet 4.4.1
Change By:
Eric Thompson
Acceptance Criteria:
This was working without issue under puppet 3. should not error:user { 'test': ensure => 'present', comment=> 'test', home => '/Users/test', iterations => '46948', password => '9690da8dd8f90f6e3fed4f267c86110e29d75e8448efdacdee9bd5cc20f81a563c9e6c6c328694fac80910ba99508cc373525ac592b87fbec0ac1a1e26a51f01873c25f2450aa78e09c8498df0f11fa930c3f655e7aeed6bc61e8475ca84297b3a2273d31974ddd232e872d9b66be82d0246d094d60155c93c6b7a27ba1aa390', salt => '62133b77a7aeecf506ffe99d064b3f8c068344de0a619a573a871f2fd6fe9eaf', shell => '/bin/bash', uid=> '503',}
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-6364) On AIX, an already installed package is not updated when using "ensure => latest"
Title: Message Title Geoff Nichols created an issue Puppet / PUP-6364 On AIX, an already installed package is not updated when using "ensure => latest" Issue Type: Bug Affects Versions: PUP 4.5.0 Assignee: Unassigned Created: 2016/05/26 4:04 PM Priority: Normal Reporter: Geoff Nichols On AIX (reported on 7.1 TL3 SP5), when using "ensure => latest" on a package, puppet does not install the latest version available if the package (in this case, an older version) is already installed. If specifying a version number (i.e. 6.0.0.5), the package is updated to this version. Below is a sample output of the command puppet uses to produce a list of packages and their version numbers: #/usr/sbin/installp -L -d . EMC:EMC.CELERRA.aix.rte:6.0.0.5::I:C:b:EMC CELERRA AIX Support Software0::
Jira (PUP-6159) OSX Passwords not setting under Puppet 4.4.1
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-6159 OSX Passwords not setting under Puppet 4.4.1 Change By: Eric Thompson Assignee: qa Eric Thompson 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-6363) The puppet master should accept reports submitted for an environment that doesn't exist
Title: Message Title Ryan Whitehurst updated an issue Puppet / PUP-6363 The puppet master should accept reports submitted for an environment that doesn't exist Change By: Ryan Whitehurst At least currently, puppet server doesn't use environments to determine what report processors to use, so it should be able to accept a report from a node for an environment that doesn't exist.The use case for this is when you have agent-specified environments enabled, and a node is in an environment that was removed (e.g., what might happen when using an r10k feature branch workflow). The node will try to pluginsync, which will fail, then it will submit the facts it has and request a catalog, which will also fail (see PE-12497). The node will then attempt to submit a report for the failed run, which will also fail. At no point during this process is any data recorded for this process except in logs. That means that the only way to discover this situation is to either notice that a node is unresponsive before it falls out of puppetdb or to search the access logs manually for such failed requests.It would be much better IMO if the report was accepted and submitted as such. Then that failure would show up in PuppetDB and any other report processors configured (e.g., the PE Console), which would make it much easier to discover and troubleshoot. Not really sure what project this belongs under specifically. 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
Jira (PUP-6362) Warning should be easily visible when Plugin Sync overwrites files from another Module
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6362 Warning should be easily visible when Plugin Sync overwrites files from another Module Change By: Ethan Brown Component/s: PMT 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-6363) The puppet master should accept reports submitted for an environment that doesn't exist
Title: Message Title Ryan Whitehurst created an issue Puppet / PUP-6363 The puppet master should accept reports submitted for an environment that doesn't exist Issue Type: Bug Assignee: Unassigned Created: 2016/05/26 4:01 PM Priority: Normal Reporter: Ryan Whitehurst At least currently, puppet server doesn't use environments to determine what report processors to use, so it should be able to accept a report from a node for an environment that doesn't exist. The use case for this is when you have agent-specified environments enabled, and a node is in an environment that was removed (e.g., what might happen when using an r10k feature branch workflow). The node will try to pluginsync, which will fail, then it will submit the facts it has and request a catalog, which will also fail (see PE-12497). The node will then attempt to submit a report for the failed run, which will also fail. At no point during this process is any data recorded for this process except in logs. That means that the only way to discover this situation is to either notice that a node is unresponsive before it falls out of puppetdb or to search the access logs manually for such failed requests. It would be much better IMO if the report was accepted and submitted as such. Then that failure would show up in PuppetDB and any other report processors configured (e.g., the PE Console), which would make it much easier to discover and troubleshoot.
Jira (PUP-6362) Warning should be easily visible when Plugin Sync overwrites files from another Module
Title: Message Title Ethan Brown commented on PUP-6362 Re: Warning should be easily visible when Plugin Sync overwrites files from another Module I agree with Rob Reynolds here - this seems intractable on pluginsync. However, it is possible to present warnings during a puppet module install conducted on a master, where it should be able to duplicate paths in use across multiple modules. 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-5926) launchd service provider doesn't implement status override.
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-5926
launchd service provider doesn't implement status override.
Change By:
Eric Thompson
I'm seeing some odd behaviour when trying to override the status command of a service which seems to be being ignored.According to the docs, setting {{hasstatus}} to {{false}} and adding a custom command to the {{status}} attribute should allow me to fine tune how Puppet tries to determine if my service is running...{quote}If a service’s init script does not support any kind of status command, you should set hasstatus to false and either provide a specific command using the status attribute or expect that Puppet will look for the service name in the process table.{quote}and for {{status}}...{quote}Specify a status command manually. This command must return 0 if the service is running and a nonzero value otherwise.{quote}I've boiled my problem down to the following example code{code}service { 'fake_service': ensure=> running, start => '/bin/echo start command', status=> '/bin/true', hasstatus => false, } {code}The behaviour I would expect from this is that when evaluating the service, puppet will run {{ /bin/true }} to determine if the service is up, which will return 0, and then stop there since the service should always be deemed running. However when I run the above code I see that the status command is never run and puppet insists on querying the service through systemctl{code}Debug: Executing '/usr/bin/systemctl is-active fake_service'Debug: Executing '/bin/echo start command'Notice: /Stage[main]/Main/Service[fake_service]/ensure: ensure changed 'stopped' to 'running'{code}So far I've seen this on Puppet 4.3.1 (MacOS) and Puppet 3.8.4 (Redhat 7.1)
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-5926) launchd service provider doesn't implement status override.
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-5926 launchd service provider doesn't implement status override. Change By: Eric Thompson Assignee: Eric Thompson 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-5926) launchd service provider doesn't implement status override.
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-5926
launchd service provider doesn't implement status override.
Change By:
Eric Thompson
Acceptance Criteria:
service { 'fake_service': ensure=> running, start => '/bin/echo start command', status=> '/bin/true', hasstatus => false, } should say running. not changed 'stopped' to 'running'
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-5926) launchd service provider doesn't implement status override.
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-5926 launchd service provider doesn't implement status override. Change By: Eric Thompson Assignee: qa Eric Thompson 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-4617) puppet cert list should display long names for extensions
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4617 puppet cert list should display long names for extensions Change By: Eric Thompson Release Notes Summary: cert list now displays long names for extensions 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-4617) puppet cert list should display long names for extensions
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4617 puppet cert list should display long names for extensions Change By: Eric Thompson Release Notes: New Feature 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-4617) puppet cert list should display long names for extensions
Title: Message Title Eric Thompson commented on PUP-4617 Re: puppet cert list should display long names for extensions validated on rhel7 at stable puppet agent SHA: ab8106c06ce0fe5f41c3aff3f62ecec233c586c7 Last login: Fri Dec 4 12:55:37 2015 from 10.32.128.239 [root@pqo92adku4aj9ee ~]# puppet cert print $(hostname -f) Certificate: Data: Version: 3 (0x2) Serial Number: 2 (0x2) [...] X509v3 extensions: Netscape Comment: .(Puppet Ruby/OpenSSL Internal Certificate
Jira (PDB-2751) FOSS CLI acceptance testing
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2751 FOSS CLI acceptance testing Issue Type: Bug Assignee: Unassigned Created: 2016/05/26 3:45 PM Priority: Normal Reporter: Andrew Roetker We should figure out how we want to test the FOSS version of the CLI wrt to acceptance tests. We might want to consider making a library of shared pre-suite functions or something with the main PuppetDB repo. We should have periodic and on-merge tests at the very least. And if we don't add PR testing, we should make it very easy to run the tests from the pooler. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2750) Add Windows and OSX support (and test it) for the FOSS CLI
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2750 Add Windows and OSX support (and test it) for the FOSS CLI Issue Type: Bug Assignee: Unassigned Created: 2016/05/26 3:42 PM Priority: Normal Reporter: Andrew Roetker We'll be adding OSX and Windows testing and support for the pe version of our CLI, we should do the same for FOSS and get some testing. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2749) Align CLI supported platforms with PuppetDB
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2749 Align CLI supported platforms with PuppetDB Issue Type: Bug Assignee: Unassigned Created: 2016/05/26 3:40 PM Priority: Normal Reporter: Andrew Roetker We should make sure the CLI supports all the OSs that PuppetDB supports and make sure we're building on those platforms and maybe one day testing against those platforms. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-4617) puppet cert list should display long names for extensions
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4617 puppet cert list should display long names for extensions Change By: Eric Thompson Assignee: qa Eric Thompson 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-2748) puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2748 puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken Issue Type: Bug Affects Versions: PDB CLI 1.0.0 Assignee: Unassigned Created: 2016/05/26 2:59 PM Priority: Normal Reporter: Andrew Roetker The puppet-agent 1.5 relies on a version of leatherman which is missing some functions that were used by the C++ puppetdb-cli in puppet-client-tools 1.0, we need to bump the version of leatherman used by the CLI and bump the dependency of the puppet-agent package we rely on to be >=1.5. We should also circulate an email about semantic versioning of puppet-agent and leatherman for projects using puppet-agent as a runtime. Add Comment
Jira (PUP-6354) Enum entries are not unique.
Title: Message Title Henrik Lindberg commented on PUP-6354 Re: Enum entries are not unique. Language specification has been updated with a note that when iterating over an Enum, the values are lexiographically sorted, and made into a unique set. 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-6362) Warning should be easily visible when Plugin Sync overwrites files from another Module
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6362 Warning should be easily visible when Plugin Sync overwrites files from another Module Change By: Rob Reynolds Scrum Team: Client Platform 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-6362) Warning should be easily visible when Plugin Sync overwrites files from another Module
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6362 Warning should be easily visible when Plugin Sync overwrites files from another Module Change By: Rob Reynolds Labels: plugin 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-6362) Warning should be easily visible when Plugin Sync overwrites files from another Module
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6362 Warning should be easily visible when Plugin Sync overwrites files from another Module Change By: Rob Reynolds Component/s: Types and Providers Component/s: Modules 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-6362) Warning should be easily visible when Plugin Sync overwrites files from another Module
Title: Message Title Rob Reynolds commented on PUP-6362 Re: Warning should be easily visible when Plugin Sync overwrites files from another Module I think this has the potential to be difficult to implement, because how do you know when you are overwriting something different and when you are just updating an older version of the same thing? Other than graphing all things moving in the current run and then providing warnings when there are collisions... 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-4904) puppet describe -s ssh_authorized_key output is really bad
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4904
puppet describe -s ssh_authorized_key output is really bad
Change By:
Henrik Lindberg
Acceptance Criteria:
{{puppet describe -s ssh_authorized_key}} should not output garbage.
Story Points:
1
Release Notes Summary:
The command puppet describe -s ssh_authorized_keyproduced garbage output because of long lines of text.
Sprint:
Language 2016-06-15
Scrum Team:
Language
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-4904) puppet describe -s ssh_authorized_key output is really bad
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4904 puppet describe -s ssh_authorized_key output is really bad Change By: Henrik Lindberg Fix Version/s: PUP 4.5.2 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-6362) Warning should be easily visible when Plugin Sync overwrites files from another Module
Title: Message Title Erick Banks created an issue Puppet / PUP-6362 Warning should be easily visible when Plugin Sync overwrites files from another Module Issue Type: Improvement Assignee: Unassigned Created: 2016/05/26 1:41 PM Priority: Normal Reporter: Erick Banks The Windows team discovered that using the Powershell module and the DSC module together caused Plugin Sync to overwrite the powershell_manager file causing one of the modules to fail after the sync. Since we only test modules in isolation and our users can write modules that can have file collisions, there should be clear warning to the end user when these kinds of overwrites happen. Identified possible scenarios: file-name collisions (including fact file-names) and fact name collisions. Add Comment
Jira (PUP-6358) Set strict_variables = true, if strict = error is set
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6358 Set strict_variables = true, if strict = error is set Change By: Henrik Lindberg Sprint: Language 2016-06-15 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-6358) Set strict_variables = true, if strict = error is set
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6358 Set strict_variables = true, if strict = error is set Change By: Henrik Lindberg Story Points: 1 Scrum Team: 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-6358) Set strict_variables = true, if strict = error is set
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6358 Set strict_variables = true, if strict = error is set Change By: Henrik Lindberg Fix Version/s: PUP 4.5.2 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-6358) Set strict_variables = true, if strict = error is set
Title: Message Title Henrik Lindberg commented on PUP-6358 Re: Set strict_variables = true, if strict = error is set The current behavior is: if strict_variables is true, an error is raised if strict_variables is false, the strict defines if undefined variables is an error or not (it does not change the setting though). It should probably also modify the setting - now it only modifies the severity of the unknown variable error. 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-6361) Validate and error if a class or define is given a name starting with ::
Title: Message Title
Peter Huene commented on PUP-6361
Re: Validate and error if a class or define is given a name starting with ::
The native compiler validates the class name during scanning the AST for definitions (effectively a validation, although it's currently tied into the definition scanner):
class foo {
class ::bar {
}
}
Notice: compiling for node 'peterhu-osx' with environment 'production'.
Error: .../production/manifests/site.pp:2:11: node 'peterhu-osx: '::bar' is not a valid class name.
class ::bar {
^
Notice: compilation failed with 1 error and 0 warnings.
Jira (PDB-2524) Display replication status in the built-in PDB dashboard
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2524 Display replication status in the built-in PDB dashboard Change By: Susan McNerney Low effort, nice to have for phase 1. Should HA team do this? or PDB do this? 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-2524) Display replication status in the built-in PDB dashboard
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2524 Display replication status in the built-in PDB dashboard Change By: Susan McNerney Low effort, nice to have for phase 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 (PDB-2524) Display replication status in the built-in PDB dashboard
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2524 Display replication status in the built-in PDB dashboard Change By: Susan McNerney Sprint: HA 2016-06-15 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-6356) puppet-agent suite tests fail: Invalid resource type test_custom_type
Title: Message Title Rob Braden commented on PUP-6356 Re: puppet-agent suite tests fail: Invalid resource type test_custom_type Yep, just passed and is in the process of promoting to PE, so this can be resolved 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-6361) Validate and error if a class or define is given a name starting with ::
Title: Message Title Henrik Lindberg commented on PUP-6361 Re: Validate and error if a class or define is given a name starting with :: Description updated. We will add a validation rule that definitions cannot use leading ::. This will flag this problem where the definition is. 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-6356) puppet-agent suite tests fail: Invalid resource type test_custom_type
Title: Message Title Kenn Hussey commented on PUP-6356 Re: puppet-agent suite tests fail: Invalid resource type test_custom_type Rob Braden any update on whether this fix cleared up the issues with CI? 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-6361) Validate and error if a class or define is given a name starting with ::
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6361
Validate and error if a class or define is given a name starting with ::
Ping Peter Huene (for native side).
Change By:
Henrik Lindberg
Acceptance Criteria:
That {code}class ::foo { }define ::foo { }{code}Both leads to an error being raised.
Story Points:
1
Release Notes Summary:
Naming a class or a define with a leading :: (making the name absolute) lead to not being able to use that class/define. Now, such names are treated as illegal.
Sprint:
Language 2016-06-15
Scrum Team:
Language
Release Notes:
Bug Fix
Add Comment
Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6361
Validate and error if a class or define is given a name starting with ::
Change By:
Henrik Lindberg
UpdateIt is not allowed to use a a leading {{::}} (making a name absolute) when defining a class or a user defined resource type.Nested definitions are named with a leading namespace from its container. It is not allowed to break out of that naming convention, and it is meaningless to use {{::}} before top level definitions.Given that it also does not work to use definitions named with a leading {{::}} there is no backwards compatibility issue - only that error comes at compile time instead of when trying to use such a definition.Original If you create a class with a name that includes two colons, it appears (as it is difficult to ascertain) to generate a class with an illegal fully qualified name. You can then no longer reference the class because it is an illegal fully qualified name.{code}$ bundle exec puppet apply -e 'class ::passwd {} include passwd'Error: Evaluation Error: Error while evaluating a Function Call, Could not find class ::passwd for build03.nelson.va at line 1:19 on node build03.nelson.va$ bundle exec puppet apply -e 'class ::passwd {} include ::passwd'Error: Evaluation Error: Error while evaluating a Function Call, Could not find class ::passwd for build03.nelson.va at line 1:19 on node build03.nelson.va$ bundle exec puppet apply -e 'class ::passwd {} include passwd'Error: Could not parse for environment production: Illegal fully qualified name at line 1:29 on node build03.nelson.va$ bundle exec puppet apply -e 'class passwd {} include passwd'Notice: Compiled catalog for build03.nelson.va in environment production in 0.05 secondsNotice: Applied catalog in 0.01 seconds$ bundle exec puppet apply -e 'class passwd {} include ::passwd'Notice: Compiled catalog for build03.nelson.va in environment production in 0.05 secondsNotice: Applied catalog in 0.01 seconds$ bundle exec puppet --version4.5.0{code}I feel that attempting to define a class in a way that generates an illegal fully qualified name should generate an error during the definition, rather than during attempts to use it. This would be more clear to authors, earlier in their development process.
Add Comment
Jira (PUP-6361) Validate and error if a class of define is given a name starting with ::
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6361 Validate and error if a class of define is given a name starting with :: Change By: Henrik Lindberg Summary: Prepending Validate and error if a class definition's of define is given a name starting with double colons results in an illegal fully qualified name :: 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-6361) Validate and error if a class or define is given a name starting with ::
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6361 Validate and error if a class or define is given a name starting with :: Change By: Henrik Lindberg Summary: Validate and error if a class of or define is given a name starting with :: 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-6361) Prepending a class definition's name with double colons results in an illegal fully qualified name
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6361 Prepending a class definition's name with double colons results in an illegal fully qualified name Change By: Henrik Lindberg Fix Version/s: PUP 4.5.2 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-6361) Prepending a class definition's name with double colons results in an illegal fully qualified name
Title: Message Title Rob Nelson commented on PUP-6361 Re: Prepending a class definition's name with double colons results in an illegal fully qualified name I did not see other related issues, but you cannot search by colons. Only PUP-6220 looked remotely related, but only based on a comment about leading '::' being illegal. 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-6361) Prepending a class definition's name with double colons results in an illegal fully qualified name
Title: Message Title
Rob Nelson created an issue
Puppet / PUP-6361
Prepending a class definition's name with double colons results in an illegal fully qualified name
Issue Type:
Bug
Affects Versions:
PUP 4.5.0
Assignee:
Unassigned
Created:
2016/05/26 12:54 PM
Priority:
Normal
Reporter:
Rob Nelson
If you create a class with a name that includes two colons, it appears (as it is difficult to ascertain) to generate a class with an illegal fully qualified name. You can then no longer reference the class because it is an illegal fully qualified name.
$ bundle exec puppet apply -e 'class ::passwd {} include passwd'
Error: Evaluation Error: Error while evaluating a Function Call, Could not find class ::passwd for build03.nelson.va at line 1:19 on node build03.nelson.va
Jira (PUP-6358) Set strict_variables = true, if strict = error is set
Title: Message Title Henrik Lindberg commented on PUP-6358 Re: Set strict_variables = true, if strict = error is set Not sure if that works well in practice. I can imagine that you may not be prepared for handling all --strict checks even if you managed to get past --strict_variables. Eventually (Puppet 5.0.0) --strict_variables will always be in force. 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 Kevin Corcoran assigned an issue to Nathaniel Smith Puppet / PUP-6258 Update Puppet OID lists to add new authorized extensions Change By: Kevin Corcoran Assignee: Nathaniel Smith 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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Henrik Lindberg commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax When decided what to do - if there are removals, add a ticket for 5.0.0 Removal epic as well. 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-5909) Implement a PCore serializer for JSON Machine to Machine
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5909 Implement a PCore serializer for JSON Machine to Machine Change By: Henrik Lindberg 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-5908) Implement a PCore MsgPack Serializer
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5908 Implement a PCore MsgPack Serializer Change By: Henrik Lindberg 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-5908) Implement a PCore MsgPack Serializer
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5908 Implement a PCore MsgPack Serializer Change By: Henrik Lindberg Sprint: Language 2016-06-15 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-5909) Implement a PCore serializer for JSON Machine to Machine
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5909 Implement a PCore serializer for JSON Machine to Machine Change By: Henrik Lindberg Sprint: Language 2016-06-15 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-5909) Implement a PCore serializer for JSON Machine to Machine
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5909 Implement a PCore serializer for JSON Machine to Machine Change By: Henrik Lindberg Story Points: 2 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-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 Cesar 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." We have seen this problem as well. Are there any plans to fix it? 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 Unassigned Puppet / PUP-4742 Bring semantic_puppet library into Puppet 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 (PDB-2747) Services must start even if the database is not available yet
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-2747 Services must start even if the database is not available yet Issue Type: New Feature Assignee: Unassigned Created: 2016/05/26 7:44 AM Priority: Normal Reporter: Ryan Senior Services that use PostgreSQL need to tolerate the fact that the database might not be up yet when their service starts; to this end, they should incorporate the work from PE-14602 and restructure their service's init method accordingly. In particular, they need to defer DB migrations until after the database is up, rather than letting init fail report in their status endpoint whether the database is available or not Add Comment
Jira (PUP-6268) Display cert information when interacting with certs via `puppet cert` face
Title: Message Title Kevin Corcoran commented on PUP-6268 Re: Display cert information when interacting with certs via `puppet cert` face Thanks, Justin Stoller. I think we are on the same page. 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-6339) Hiera Data in Module give bad results when environment_timeout is unlimited
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6339 Hiera Data in Module give bad results when environment_timeout is unlimited Change By: Kenn Hussey Flagged: Impediment 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-2746) Remove clamq; use ActiveMQ directly
Title: Message Title Michal Ruzicka created an issue PuppetDB / PDB-2746 Remove clamq; use ActiveMQ directly Issue Type: Improvement Assignee: Unassigned Created: 2016/05/26 4:14 AM Priority: Normal Reporter: Michal Ruzicka PuppetDB has done that in PDB-1252 , we want to follow suite. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6120) Pip package provider doesn't honor config for custom PyPI repositories
Title: Message Title Jon Skarpeteig assigned an issue to Jon Skarpeteig Puppet / PUP-6120 Pip package provider doesn't honor config for custom PyPI repositories Change By: Jon Skarpeteig Assignee: qa Jon Skarpeteig 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.
