Jira (PUP-6168) Runtime3Loader initiates load that updates loader, then tries to update again
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-6168 Runtime3Loader initiates load that updates loader, then tries to update again Issue Type: Bug Assignee: Thomas Hallgren Created: 2016/04/13 1:37 AM Fix Versions: PUP 4.5.0 Priority: Blocker Reporter: Thomas Hallgren The Runtime3TypeLoader#find method will delegate to the known_resource_types of the current environment. This might lead to new code being brought in, parsed, and evaluated. and that evaluation might instantiate the very resource type that was first queried. The instantiation updates the Runtime3TypeLoader. Consequently, when the known_resource_types returns the entry, it's already stored in the loader and the loaders attempt to now store it again, results in a 'Attempt to redefine entity' exception. Add Comment
Jira (PUP-6159) OSX Passwords not setting under Puppet 4.4.1
Title: Message Title Kyle Fieldus updated an issue Puppet / PUP-6159 OSX Passwords not setting under Puppet 4.4.1 Change By: Kyle Fieldus Summary: OSX Passwords not setting under Puppet 4 and OSX .4.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 (PUP-6159) OSX Passwords not setting under Puppet 4 and OSX
Title: Message Title
Kyle Fieldus updated an issue
Puppet / PUP-6159
OSX Passwords not setting under Puppet 4 and OSX
Change By:
Kyle Fieldus
Managing the passwords for local users under OSX 10.9, 10.10 and 10.11 under puppet 4.4.1 fails when setting the salt, iterations and password. Steps to re-create:Used the following command to generate a user definition and saved it to test.pp{code}puppet resource user test >> test.pp{code}{code:puppet}user { 'test': ensure => 'present', comment=> 'test', gid=> '20', groups => ['com.apple.sharepoint.group.2'], home => '/Users/test', iterations => '46948', password => '9690da8dd8f90f6e3fed4f267c86110e29d75e8448efdacdee9bd5cc20f81a563c9e6c6c328694fac80910ba99508cc373525ac592b87fbec0ac1a1e26a51f01873c25f2450aa78e09c8498df0f11fa930c3f655e7aeed6bc61e8475ca84297b3a2273d31974ddd232e872d9b66be82d0246d094d60155c93c6b7a27ba1aa390', salt => '62133b77a7aeecf506ffe99d064b3f8c068344de0a619a573a871f2fd6fe9eaf', shell => '/bin/bash', uid=> '503',}{code}When running puppet apply on the following above definition I get the following errors:{code}Error: "\x96" on UTF-8Error: /Stage[main]/Main/User[test]/password: change from [old password hash redacted] to [new password hash redacted] failed: "\x96" on UTF-8Error: "\xA7" on UTF-8Error: /Stage[main]/Main/User[test]/salt: change from 6f13b4510093e89a0098eff8ee5d4bae3e1314ebf31064c101cd886ad8c2fab6 to 62133b77a7aeecf506ffe99d064b3f8c068344de0a619a573a871f2fd6fe9eaf failed: "\xA7" on UTF-8Error: "\xD2" followed by "\x01" on UTF-8Error: /Stage[main]/Main/User[test]/iterations: change from 43290 to 46948 failed: "\xD2" followed by "\x01" on UTF-8{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Richard Pijnenburg commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection We backported the PR from Marc Fournier to our Puppet 3.8.5 install and still shows the same issue with Puppet Server 1.1.3 We also increased the `idle-timeout-milliseconds` which had no impact either. 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-6168) Runtime3Loader initiates load that updates loader, then tries to update again
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-6168
Runtime3Loader initiates load that updates loader, then tries to update again
Change By:
Thomas Hallgren
The {{Runtime3TypeLoader#find}} method will delegate to the {{known_resource_types}} of the current environment. This might lead to new code being brought in, parsed, and evaluated. and that evaluation might instantiate the very resource type that was first queried. The instantiation updates the {{Runtime3TypeLoader}}. Consequently, when the {{known_resource_types}} returns the entry, it's already stored in the loader and the loaders attempt to now store it again, results in a 'Attempt to redefine entity' exception. This regression was introduced in PUP-6028 which has not yet been released.
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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Marc Fournier commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection Richard Pijnenburg nb: this patch was about TCP keepalives, not HTTP Keepalive. And the goal was to force the agent to fail eventually. So I'm not really sure how it relates to this issue. 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-6168) Runtime3Loader initiates load that updates loader, then tries to update again
Title: Message Title Henrik Lindberg commented on PUP-6168 Re: Runtime3Loader initiates load that updates loader, then tries to update again merged to master: 1ad715a 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-6168) Runtime3Loader initiates load that updates loader, then tries to update again
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6168 Runtime3Loader initiates load that updates loader, then tries to update again Change By: Henrik Lindberg Release Notes Summary: bug in not yet released feature Release Notes: Not Needed 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-6169) Feature Request: Deprecation Logs
Title: Message Title Rob Nelson created an issue Puppet / PUP-6169 Feature Request: Deprecation Logs Issue Type: New Feature Affects Versions: PUP 4.4.1 Assignee: Unassigned Components: Puppet Server, PuppetDB Created: 2016/04/13 4:43 AM Priority: Normal Reporter: Rob Nelson Problem When a user updates puppet components (server, agent, puppetdb, etc.), a number of new features and options are typically made available, in addition to the default location of some files being changed. Older features, options, and file locations (collectively 'features' for simplicity) are considered deprecated, to be removed in some future version. Alerting the user of this is challenging for a few reasons. 1. Deprecation messages in puppet runs are noisy and most users disable them as quickly as possible, never to be seen again. 2. Moving the messages to the component's log results in a bunch of needles being added to the needlestack. 3. At the time of deprecation, it is usually impossible to determine what future version will have no longer support the deprecated feature, or when that version will be released, so users cannot plan for a timely removal of the feature. 4. When u
Jira (PUP-6167) Default Tuple type constructed with "max" of 0 instead of "infinity".
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6167 Default Tuple type constructed with "max" of 0 instead of "infinity". Change By: Thomas Hallgren 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-6167) Default Tuple type constructed with "max" of 0 instead of "infinity".
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6167 Default Tuple type constructed with "max" of 0 instead of "infinity". Change By: Thomas Hallgren Scope Change Category: Found Scope Change Reason: Easy fix, and I had everything current due to other fixes in the same area. Sprint: Language Triage 2016-04-20 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-6167) Default Tuple type constructed with "max" of 0 instead of "infinity".
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6167 Default Tuple type constructed with "max" of 0 instead of "infinity". Change By: Thomas Hallgren Fix Version/s: PUP 4.5.0 Fix Version/s: PUP 4.4.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 (NPUP-39) Conform to Puppet's `assignable?` logic.
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Native Puppet / NPUP-39 Conform to Puppet's `assignable?` logic. Change By: Thomas Hallgren 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-5928) Add pattern matching to Runtime Type
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-5928 Add pattern matching to Runtime Type Change By: John Duarte 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-6149) Parameterized Collection type is incorrectly constructed
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6149 Parameterized Collection type is incorrectly constructed Change By: John Duarte 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-6156) Access operator is not implemented for Iterator type
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6156 Access operator is not implemented for Iterator type Change By: John Duarte 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-6155) Access operator is not implemented for Iterable type
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6155 Access operator is not implemented for Iterable type Change By: John Duarte 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-6136) newparam(:downgrade) for package type
Title: Message Title Matt Schuchard commented on PUP-6136 Re: newparam(:downgrade) for package type Starting to have second thoughts about this. Implementing this for yum/dnf and rpm is easy, but I started for apt and I can grab the current installed version, but then I cannot simply if should < version because I would have to write a version compare function like in yum. Stepping back and looking at this makes it seem like this would require a huge effort for current installed version parsing and version comparing for each provider. 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-5928) Add pattern matching to Runtime Type
Title: Message Title John Duarte updated an issue Puppet / PUP-5928 Add pattern matching to Runtime Type Change By: John Duarte 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 (PUP-5928) Add pattern matching to Runtime Type
Title: Message Title John Duarte updated an issue Puppet / PUP-5928 Add pattern matching to Runtime Type Change By: John Duarte QA Risk Assessment: Low 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-5928) Add pattern matching to Runtime Type
Title: Message Title John Duarte updated an issue Puppet / PUP-5928 Add pattern matching to Runtime Type Change By: John Duarte QA Risk Assessment Reason: Covered by unit test 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-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Priscilla Piedra commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Hi Wyatt Alt ! Thanks for your help! To answer your questions: 1) have you been on 2.3.8 for a long time or have you recently upgraded: We have like two months using 2.3.8 version, before we had 2.2.2 2) did this start occurring suddenly or has it been going on for a while This problem appeared suddenly... like two weeks ago. 3) if suddenly, do any of the fact names I listed above correspond in an obvious way to recent changes? No, the facts are the same, there is no a recent change on them. 4) Do you use a single PDB + postgres/single master or is your PDB/postgres setup more complicated than that? We use a single postgres master, but for each PM we have puppetdb installed (we have 10 pms) 5) (unlikely) does anyone ever perform manual deletions on this database? Manual deletions no, but it is configured on each PDB report-ttl = 14d I sent to your email the output of the log. Thanks again!! 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-6170) launchd provider in 3.8.6 fails on Mac OS X 10.7,10.8
Title: Message Title Bruce Lysik created an issue Puppet / PUP-6170 launchd provider in 3.8.6 fails on Mac OS X 10.7,10.8 Issue Type: Bug Affects Versions: PUP 3.8.6 Assignee: Unassigned Created: 2016/04/13 8:32 AM Environment: Mac OS X 10.7 and 10.8 with stock ruby. Priority: Normal Reporter: Bruce Lysik Trying to install puppet 3.8.6 gem on Mac OS X 10.7 and 10.8. launchd provider fails like so: $ sudo puppet resource service --trace --debug Debug: Runtime environment: run_mode=user, ruby_version=1.8.7, puppet_version=3.8.6 Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not exist Debug: Puppet::Type::Service::ProviderDaemontools: file /usr/bin/svc does not exist Debug: Puppet::Type::Service::ProviderUpstart: 0 confines (of 2) were true Debug: Puppet::Type::Service::ProviderRedhat: file /sbin/service does not exist Debug: Puppet::Type::Service::ProviderDebian: file /usr/sbin/update-rc.d does not exist Debug: Puppet::Type::Service::ProviderSystemd: file systemctl does not exist Debug: Puppet::Type::Service::
Jira (PUP-6170) launchd provider in 3.8.6 fails on Mac OS X 10.7,10.8
Title: Message Title Bruce Lysik updated an issue Puppet / PUP-6170 launchd provider in 3.8.6 fails on Mac OS X 10.7,10.8 Change By: Bruce Lysik Labels: osx 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-6102) A type alias that has an alias name of a built-in type should be illegal
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6102 A type alias that has an alias name of a built-in type should be illegal Change By: John Duarte Assignee: qa John Duarte 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-6102) A type alias that has an alias name of a built-in type should be illegal
Title: Message Title John Duarte updated an issue Puppet / PUP-6102 A type alias that has an alias name of a built-in type should be illegal Change By: John Duarte 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 (PUP-6102) A type alias that has an alias name of a built-in type should be illegal
Title: Message Title John Duarte updated an issue Puppet / PUP-6102 A type alias that has an alias name of a built-in type should be illegal Change By: John Duarte QA Risk Assessment: Medium 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-1387) Google Cloud instances are not recognised as virtual on Windows
Title: Message Title John Duarte updated an issue Facter / FACT-1387 Google Cloud instances are not recognised as virtual on Windows Change By: John Duarte 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-1387) Google Cloud instances are not recognised as virtual on Windows
Title: Message Title John Duarte updated an issue Facter / FACT-1387 Google Cloud instances are not recognised as virtual on Windows Change By: John Duarte QA Risk Assessment: Low 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-6106) Puppet gem does not find vendored rgen gem
Title: Message Title Michael Stahnke updated an issue Puppet / PUP-6106 Puppet gem does not find vendored rgen gem Change By: Michael Stahnke Scrum Team: Release Engineering 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-6171) puppet apply user.pp (which just contains a user resource) fails on mac os x
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6171 puppet apply user.pp (which just contains a user resource) fails on mac os x Change By: Kylo Ginsberg Sprint: Client Triage 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-6171) puppet apply user.pp (which just contains a user resource) fails on mac os x
Title: Message Title Kylo Ginsberg moved an issue Puppet / PUP-6171 puppet apply user.pp (which just contains a user resource) fails on mac os x Change By: Kylo Ginsberg Affects Version/s: puppet-agent 1.4.1 Affects Version/s: puppet-agent 1.4.0 Affects Version/s: PUP 4.4.0 Workflow: Release Engineering Scrum Team Workflow Key: PA PUP - 269 6171 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6171) puppet apply user.pp (which just contains a user resource) fails on mac os x
Title: Message Title Kylo Ginsberg commented on PUP-6171 Re: puppet apply user.pp (which just contains a user resource) fails on mac os x Moving to PUP project (seems likely to be in puppet proper), and putting in our Client Triage sprint. 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-5588) Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times
Title: Message Title Glenn Sarti commented on PUP-5588 Re: Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times Ethan Brown 's FR found a different duplication error where root certificates appeared to be loading twice. https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/monkey_patches.rb#L136 This is not due to a bug, but is "by design". A certificate store used in https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/monkey_patches.rb#L136 is a logical store, not physical. The logical is made up multiple physical stores, merged together to look like one. https://blogs.msdn.microsoft.com/muaddib/2013/10/18/understanding-and-managing-the-certificate-stores-used-for-smart-card-logon/ To create an "apparent" duplicate certificate do the following; 1. Open regedit and browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\ROOT\Certificates 2. Export one the certificates to C:\DupeCert.reg 3. Edit C:\DupeCert.reg in Notepad and change "HKEY_LOCAL_MACHINE" to "HKEY_CURRENT_USER". Save the file 4. Import C:\DupeCert.reg into the registry. This now means the certificate is in both the Machine and User ROOT registry certificate stores and appears as a duplicate But this doesn't explain why the ruby code doesn't catch the duplicate. It should do as part of "...instance.to_a.uniq" https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/monkey_patches.rb#L132 According to http://ruby-doc.org/core-2.2.0/Array.html#method-i-uniq ruby uses the .hash function for comparison. After adding some logging at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/monkey_patches.rb#L134 the following was found; For the same PEM content of a cert, the .hash value kept changing! Certificate PEM -BEGIN CERTIFICATE- MIIDDDCCAfSgAwIBAgIDAQAgMA0GCSqGSIb3DQEBBQUAMD4xCzAJBgNVBAYTAlBM MRswGQYDVQQKExJVbml6ZXRvIFNwLiB6IG8uby4xEjAQBgNVBAMTCUNlcnR1bSBD QTAeFw0wMjA2MTExMDQ2MzlaFw0yNzA2MTExMDQ2MzlaMD4xCzAJBgNVBAYTAlBM
Jira (PUP-6166) Authorization Certificate Extensions
Title: Message Title Reid Vandewiele updated an issue Puppet / PUP-6166 Authorization Certificate Extensions Change By: Reid Vandewiele Scrum Team: Puppet Server 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-236) Facter RPM should not require virt-what
Title: Message Title Branan Riley commented on FACT-236 Re: Facter RPM should not require virt-what Michael Smith I think we can close this one 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-1375) Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes
Title: Message Title Sean Griffin updated an issue Facter / FACT-1375 Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes Change By: Sean Griffin Attachment: pup-6124-route-test-script 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-1375) Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes
Title: Message Title Sean Griffin updated an issue Facter / FACT-1375 Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes Change By: Sean Griffin Release Notes Summary: Before this fix, 'facter ipaddress' could return the address of the wrong network interface when there are routes for 0.0.0.0, with non-zero subnet mask, in addition to the default route. The correct ip address is the address of the interface associated with the interface on the route table entry for the default gateway. 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-5588) Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times
Title: Message Title Glenn Sarti commented on PUP-5588 Re: Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times Submitted PR 4879 with updated unit tests and 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 (PUP-6166) Authorization Certificate Extensions
Title: Message Title Eric Sorenson commented on PUP-6166 Re: Authorization Certificate Extensions This mechanism needs to be different from our existing certificate extensions due to the need to prevent authorization-granting certificates from being accidentally signed. I don't understand this, or at least to the extent that I understand what you're saying I disagree with 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-6166) Authorization Certificate Extensions
Title: Message Title Karen Van der Veer assigned an issue to Nathaniel Smith Puppet / PUP-6166 Authorization Certificate Extensions Change By: Karen Van der Veer Assignee: Nathaniel Smith Sub-team: jade 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-5588) Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times
Title: Message Title Glenn Sarti assigned an issue to Ethan Brown Puppet / PUP-5588 Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times Change By: Glenn Sarti Assignee: Ethan Brown 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-1375) Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes
Title: Message Title Sean Griffin assigned an issue to Unassigned Facter / FACT-1375 Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes 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-5825) systemd service provider always enables service in chroot
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-5825 systemd service provider always enables service in chroot 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-236) Facter RPM should not require virt-what
Title: Message Title Michael Smith updated an issue Facter / FACT-236 Facter RPM should not require virt-what Change By: Michael Smith Affects Version/s: FACT 1.7.4 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-236) Facter RPM should not require virt-what
Title: Message Title Michael Smith updated an issue Facter / FACT-236 Facter RPM should not require virt-what Change By: Michael Smith Fix Version/s: FACT 1.7.4 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-6166) Authorization Certificate Extensions
Title: Message Title Chris Barker commented on PUP-6166 Re: Authorization Certificate Extensions The concern is that currently there is no way to warn or notify a user they are signing certificates with ssl extensions. Which means in the instance of TK-293, someone could request what appears to be an agent certificate, but contains ssl extensions that conform to the whitelist access policies for PuppetDB. By adding a new set of extensions (authorization extensions), we don't have to change the autosigning behavior or configuration for the previous extensions to prevent that above issue - Puppet already flags and wont autosign certificates that contain extensions outside of the predefined space. This also prevents collisions for users who may already be using ssl extensions heavily in their environment, since this is a new subset of extensions in a new namespace (puppetlabs.1.3) vs the ones that were used before. 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-6169) Feature Request: Deprecation Logs
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6169 Feature Request: Deprecation Logs Change By: Karen Van der Veer Scrum Team: Puppet Server 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-6166) Authorization Certificate Extensions
Title: Message Title Eric Sorenson commented on PUP-6166 Re: Authorization Certificate Extensions OK that makes more sense, I read through the whole conversation on TK-293 and understand why everyone landed here. The ticket description just presents it as axiomatic and my brain bounced off the statement 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-6106) Puppet gem does not find vendored rgen gem
Title: Message Title Rob Nelson commented on PUP-6106 Re: Puppet gem does not find vendored rgen gem FYI Kylo Ginsberg and I discovered this is a really unique corner case, where we have a CentOS 6 node with Ruby 1.8.7 at the system level. The rspec tests are done with bundle, and we've hijacked the PE binary at /opt/puppet/bin/bundle to run those tests. Bundled vs system vs whatever gems conflict due to order of loading. I'm hoping Kylo can provide more specifics, for any others who run into this corner case. Our fix will be to accelerate our migration to CentOS 7 and Ruby 2.0.0 and stop hijacking the AIO binaries which make things wonky. 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 (NPUP-40) REPL: replace readline dependency with editline (libedit)
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-40 REPL: replace readline dependency with editline (libedit) Issue Type: Bug Affects Versions: NPUP 0.1.0 Assignee: Unassigned Created: 2016/04/13 11:13 AM Fix Versions: NPUP 0.1.0 Priority: Major Reporter: Peter Huene For licensing reasons, the currently optional GNU readline dependency should be replaced with the BSD-licensed editline library. Add Comment
Jira (NPUP-40) REPL: replace readline dependency with editline (libedit)
Title: Message Title Peter Huene assigned an issue to Peter Huene Native Puppet / NPUP-40 REPL: replace readline dependency with editline (libedit) Change By: Peter Huene Assignee: Peter Huene 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-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Wyatt Alt commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Priscilla Piedra Thanks – the postgres logs you gave me show that the reason the deletion is failing is not a foreign key constraint violation, but this: 2016-04-12 15:26:28 GMT puppetdb puppetdb_rw ERROR: stack depth limit exceeded 2016-04-12 15:26:28 GMT puppetdb puppetdb_rw HINT: Increase the configuration parameter "max_stack_depth" (currently 2048kB), after ensuring the platform's stack depth limit is adequate. can you check ulimit -s and change postgres's max_stack_depth parameter to be a megabyte or so less (this will require a postgres restart)? My ulimit is reporting kilobytes, so if it's the same for you make sure to make the appropriate conversion. My guess is that once you've ended up in the situation you're in, it can only get worse. There's a good chance that if raising max_stack_depth allows the delete to succeed you can then lower it again if needed. The configuration parameter is documented here: http://www.postgresql.org/docs/9.5/static/runtime-config-resource.html If the delete still fails, I'd like to see the same postgres logs with the new failure. In that event we'll probably need to clear those facts out manually via a truncate or targeted delete. It's still an open question how you exceeded the stack depth originally – nothing you've reported so far indicates anything else out of the ordinary.
Jira (PUP-6137) Name anonymous Object when bound to a type name.
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6137 Name anonymous Object when bound to a type name. Change By: John Duarte Assignee: qa John Duarte 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-1385) Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2
Title: Message Title Michael Smith commented on FACT-1385 Re: Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2 Requires a Leatherman release; that can be done whenever we're ready to work on this ticket. 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-5353) Statically-enabled systemd service is treated like SysV init scripts - enabled each run.
Title: Message Title Michael Smith commented on PUP-5353 Re: Statically-enabled systemd service is treated like SysV init scripts - enabled each run. The conclusion on puppet-dev seems to have coalesced around: The systemd provider should report static status as enabled. This seems mostly consistent with how systemctl is-enabled reports it (exit status 0) and is consistent with chkconfig. If you try to disable a static service, it should do nothing, and log a message about managing the enable flag of a static service having no effect. Whether that message should be warning or debug is inconclusive; I think we'll opt for debug for now. 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-6137) Name anonymous Object when bound to a type name.
Title: Message Title John Duarte updated an issue Puppet / PUP-6137 Name anonymous Object when bound to a type name. Change By: John Duarte QA Risk Assessment: Medium Low 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-6149) Parameterized Collection type is incorrectly constructed
Title: Message Title John Duarte updated an issue Puppet / PUP-6149 Parameterized Collection type is incorrectly constructed Change By: John Duarte QA Risk Assessment: Medium 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-6149) Parameterized Collection type is incorrectly constructed
Title: Message Title John Duarte updated an issue Puppet / PUP-6149 Parameterized Collection type is incorrectly constructed Change By: John Duarte 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 (PUP-6149) Parameterized Collection type is incorrectly constructed
Title: Message Title John Duarte commented on PUP-6149 Re: Parameterized Collection type is incorrectly constructed Validated using puppet-agent at sha af76506 containing puppet at sha 1ab4f1f on Debian 8 amd64. Results as per the defined acceptance criteria. root@ie6mpkcm9t8cea7:~# cat /opt/puppetlabs/puppet/VERSION 1.4.1.359.gaf76506 root@ie6mpkcm9t8cea7:~# puppet apply -e 'notice(Collection[5, 5] > Tuple[Integer, 0, 10])' Notice: Scope(Class[main]): false Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6149) Parameterized Collection type is incorrectly constructed
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6149 Parameterized Collection type is incorrectly constructed Change By: John Duarte Assignee: qa John Duarte 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-6137) Name anonymous Object when bound to a type name.
Title: Message Title
John Duarte commented on PUP-6137
Re: Name anonymous Object when bound to a type name.
Using puppet-agent at sha af76506 containing puppet at sha 1ab4f1f - Object takes name from type
~# puppet apply -e 'type Vehicle = Object[ {attributes => { regid => Integer } }]; notice Vehicle'
Notice: Scope(Class[main]): Object[{name => 'Vehicle', attributes => {'regid' => Integer}}]
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-6169) Feature Request: Deprecation Logs
Title: Message Title Henrik Lindberg commented on PUP-6169 Re: Feature Request: Deprecation Logs Worth mentioning here is that we do (since some time back) have the ability to write logs in JSON which enables slicing and dicing of the information in a structured way. This structured logging can also preserve issue-codes which makes it easier to correlate and group logged issues. Catalog Preview is using this technique with performing a catalog diff. One possible alternative workflow is to set --strict to off. When getting ready to upgrade, run compilation with catalog preview and --strict warning (or even error). Fix issues until clean, then switch to new version. While this does not have a separate log for deprecations I think it achieves the same, and in a better way as the catalog preview tool aggregates and correlates errors and warnings. We expect all deprecations (and extra validations that will be standard in the next version) to be behind the --strict setting. Ping Eric Sorenson 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-6169) Feature Request: Deprecation Logs
Title: Message Title Henrik Lindberg assigned an issue to Eric Sorenson Puppet / PUP-6169 Feature Request: Deprecation Logs Change By: Henrik Lindberg Assignee: Eric Sorenson 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-5105) Add a ci:test:aio_per_commit Rake target for reduced acceptance suite
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-5105 Add a ci:test:aio_per_commit Rake target for reduced acceptance suite Change By: William Hopper Assignee: William Hopper 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-5105) Add a ci:test:aio_per_commit Rake target for reduced acceptance suite
Title: Message Title William Hopper updated an issue Puppet / PUP-5105 Add a ci:test:aio_per_commit Rake target for reduced acceptance suite Change By: William Hopper Scope Change Category: Adopted Scope Change Reason: Using this ticket as the PUP placeholder for RE-6554, which I am currently working on Sprint: Client Triage 2016-04-20 (Bigga Bugs) 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 (NPUP-39) Conform to Puppet's `assignable?` logic.
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Native Puppet / NPUP-39 Conform to Puppet's `assignable?` logic. Change By: Thomas Hallgren 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 (NPUP-39) Conform to Puppet's `assignable?` logic.
Title: Message Title Thomas Hallgren commented on NPUP-39 Re: Conform to Puppet's `assignable?` logic. Merged to master at 9013300. 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-6106) Puppet does not find vendored rgen gem when using PE 3.x ruby
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6106 Puppet does not find vendored rgen gem when using PE 3.x ruby Change By: Kylo Ginsberg Summary: Puppet gem does not find vendored rgen gem when using PE 3.x ruby 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-6106) Puppet does not find vendored rgen gem when using PE 3.x ruby
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6106 Puppet does not find vendored rgen gem when using PE 3.x ruby Change By: Kylo Ginsberg The summary is true generically when using a PE 3.x ruby to run a version of puppet because of how PE 3.x packages ruby and puppet-required gems like rgen. However, it becomes an active problem when using it to run (or run rspec-puppet against) puppet version 4.4 or greater, because starting in puppet 4.4, puppet uses an rgen method not available in the version of rgen provided by the PE 3.x ruby.-Original description below:The puppet gem requires the rgen gem for lookup(). This is likely to show up with rspec-puppet when using the puppet gem as "~> 4.0" or "~> 4.4.0". See https://github.com/rodjek/rspec-puppet/issues/377#issuecomment-202979614 for more details from [~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-6106) Puppet does not find vendored rgen gem when using PE 3.x ruby
Title: Message Title
Kylo Ginsberg updated an issue
Puppet / PUP-6106
Puppet does not find vendored rgen gem when using PE 3.x ruby
Change By:
Kylo Ginsberg
The summary is true generically when using a PE 3.x ruby to run a version of puppet because of how PE 3.x packages ruby and puppet-required gems like rgen. However, it becomes an active problem when using it to run (or run rspec-puppet against) puppet version 4.4 or greater, because starting in puppet 4.4, puppet uses an rgen method , {{eContents}}, not available in the version of rgen provided by the PE 3.x ruby.-Original description below:The puppet gem requires the rgen gem for lookup(). This is likely to show up with rspec-puppet when using the puppet gem as "~> 4.0" or "~> 4.4.0". See https://github.com/rodjek/rspec-puppet/issues/377#issuecomment-202979614 for more details from [~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-6106) Puppet does not find vendored rgen gem when using PE 3.x ruby
Title: Message Title Kylo Ginsberg commented on PUP-6106 Re: Puppet does not find vendored rgen gem when using PE 3.x ruby Rob Nelson I added an explanatory comment and also updated the summary and description with an eye to describing the problem for future issue searchers. I'll close this as Not a Bug, but please re-open if that doesn't make sense for any reason. And thanks for all your help debugging this one! 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-6106) Puppet gem does not find vendored rgen gem
Title: Message Title
Kylo Ginsberg commented on PUP-6106
Re: Puppet gem does not find vendored rgen gem
This problem arose because PE 3.x's ruby includes rgen 0.6.5 (but not bundled as a gem, so doesn't show in, say, gem list). Puppet itself vendors a newer version of rgen (0.7.0 as I write), but the puppet-vendored gems are {{load}}ed after anything found in the system ruby (or bundled gems, etc). In short the PE-provided version of rgen will take priority.
This has long been the case, but in puppet 4.4.x, the puppet code started using an rgen method which is present in 0.7.0 but not in 0.6.5. So as of puppet 4.4, using a PE 3.x ruby to test (or run) puppet code will fail as described in the linked rspec-puppet issue.
Using a system ruby, as Rob describes in the comment above, or using a ruby manager such as rbenv or rvm, none of which will have included an rgen gem, will avoid this issue.
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-5353) Statically-enabled systemd service is treated like SysV init scripts - enabled each run.
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-5353 Statically-enabled systemd service is treated like SysV init scripts - enabled each run. Change By: William Hopper Assignee: William Hopper 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-6168) Runtime3Loader initiates load that updates loader, then tries to update again
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6168 Runtime3Loader initiates load that updates loader, then tries to update again Change By: Henrik Lindberg Acceptance Criteria: This fixes a problem that was found by acceptance tests installing PDB. If acceptance tests pass, this fix is accepted. 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-1389) Facter.rb regression when called from MCO
Title: Message Title Michael Smith commented on FACT-1389 Re: Facter.rb regression when called from MCO Failed CI, looks like it doesn't work quite right on Linux (probably because we don't set path). 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 QA Risk Assessment: Medium 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-5802) Yum provider incorrectly computes epoch for RPM package versions
Title: Message Title Michael Smith updated an issue Puppet / PUP-5802 Yum provider incorrectly computes epoch for RPM package versions Change By: Michael Smith 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-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-5998) [Spike] Rehabilitate Groups
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5998 [Spike] Rehabilitate Groups Change By: Kylo Ginsberg Sprint: Client 2016-05- 04 18 (Freeze) 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-4634) Add some timings/metrics in report
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4634 Add some timings/metrics in report Change By: Eric Thompson QA Risk Assessment: Medium 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-4634) Add some timings/metrics in report
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4634 Add some timings/metrics in report Change By: Kylo Ginsberg Story Points: 3 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-6172) Add static node config for huawei switch
Title: Message Title Stan Duffy created an issue Puppet / PUP-6172 Add static node config for huawei switch Issue Type: Task Assignee: Stan Duffy Created: 2016/04/13 3:39 PM Environment: CI Pipeline Priority: Normal Reporter: Stan Duffy Because the Huawei Switch being used for testing is a Physical Switch, we will need to have static node config file for the acceptance tests. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha
Jira (PUP-4039) package resource doesn't find new packages in yum repo
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4039 package resource doesn't find new packages in yum repo Change By: Kylo Ginsberg Sprint: Client Triage CI.next 2016-05-04 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-4634) Add some timings/metrics in report
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4634 Add some timings/metrics in report Change By: Eric Thompson QA Highest Test Level: Acceptance 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-4634) Add some timings/metrics in report
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4634 Add some timings/metrics in report Change By: Eric Thompson Acceptance Criteria: report should have three new Info timings:Info: Caching catalog for puppetagent in 0.02 secondsInfo: Convert Catalog in 0.06 secondsInfo: Sent report in 0.09 seconds 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-5025) Package resource showing notice when ensure attribute contains Epoch tag
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5025 Package resource showing notice when ensure attribute contains Epoch tag Change By: Eric Thompson 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 (PUP-5025) Package resource showing notice when ensure attribute contains Epoch tag
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5025 Package resource showing notice when ensure attribute contains Epoch tag Change By: Eric Thompson QA Risk Assessment: Low Medium 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-5025) Package resource showing notice when ensure attribute contains Epoch tag
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5025 Package resource showing notice when ensure attribute contains Epoch tag Change By: Eric Thompson 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 (PUP-6097) YUM/APT package providers require architecture as part of package version
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6097 YUM/APT package providers require architecture as part of package version Change By: Eric Thompson QA Highest Test Level: Acceptance QA Risk Assessment: Medium 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-6097) YUM/APT package providers require architecture as part of package version
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6097 YUM/APT package providers require architecture as part of package version Change By: Eric Thompson 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 (PUP-3916) File type downloads file content twice when diffs are enabled and file is updated
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3916 File type downloads file content twice when diffs are enabled and file is updated Change By: Kylo Ginsberg Sprint: Client Triage 2016-05-18 (Freeze) 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 (HI-509) Add static node config for huawei switch
Title: Message Title Stan Duffy created an issue Hiera / HI-509 Add static node config for huawei switch Issue Type: Task Assignee: Stan Duffy Created: 2016/04/13 3:53 PM Environment: CI Pipeline Priority: Normal Reporter: Stan Duffy Because the Huawei Switch being used for testing is a Physical Switch, we will need to have static node config file for the acceptance tests. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b
Jira (FACT-1354) Facter ec2_userdata handles binary data incorrectly
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1354 Facter ec2_userdata handles binary data incorrectly Change By: Kylo Ginsberg Sprint: Client Triage 2016-05-18 (Freeze) 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-6097) YUM/APT package providers require architecture as part of package version
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6097 YUM/APT package providers require architecture as part of package version Change By: Eric Thompson Acceptance Criteria: when a package contains an epoch on system's package manager, it must not be required by puppet to ensure it:ensure => 1.4.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 (FACT-1373) Facter with external fact containing a facter call fork-bombs the node
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1373 Facter with external fact containing a facter call fork-bombs the node Change By: Kylo Ginsberg 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 (PUP-6000) Puppet slowing down after calling Puppet.initialize_settings multiple times
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6000 Puppet slowing down after calling Puppet.initialize_settings multiple times Change By: Kylo Ginsberg Sprint: Client Triage 2016-05-04 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-6000) Puppet slowing down after calling Puppet.initialize_settings multiple times
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6000 Puppet slowing down after calling Puppet.initialize_settings multiple times Change By: Kylo Ginsberg 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 (PUP-6171) puppet apply user.pp (which just contains a user resource) fails on mac os x
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6171 puppet apply user.pp (which just contains a user resource) fails on mac os x Change By: Kylo Ginsberg Sprint: Client Triage 2016-05-04 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 Kylo Ginsberg updated an issue Puppet / PUP-6159 OSX Passwords not setting under Puppet 4.4.1 Change By: Kylo Ginsberg Sprint: Client Triage 2016-05-04 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.
