Jira (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Rene van der Linden commented on FACT-1244 Re: xenu vs. xen0 difference not recognized by Puppet Currection: PE 3.3.2 actually makes use of Facter 1.7.5 (and not as 2x as reported before) Output from Xen Hypervisor* Red Hat Enterprise Linux Server release 5.11 (Tikanga) facter -v 1.7.5 facter --debug virtual xen0 facter --debug xendomains host1,host2,host3,etc Output from a Xen Virtual* Red Hat Enterprise Linux Server release 5.11 (Tikanga) facter -v 1.7.5 facter --debug virtual xenu facter --debug xendomains Found no suitable resolves of 1 for xendomains value for xendomains is still nil Add Comment
Jira (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Rene van der Linden commented on FACT-1244 Re: xenu vs. xen0 difference not recognized by Puppet PE 2015.2.1 facter -v 3.1.0 (commit fc7614d6ba81845757ba7318269fad2b2da08da3) facter --debug virtual 661078 INFO puppetlabs.facter - executed with command line: --debug virtual. 662471 INFO leatherman.ruby:124 - ruby loaded from "/opt/puppetlabs/puppet/lib/libruby.so.2.1.0". 672009 INFO leatherman.ruby:145 - using ruby version 2.1.6 719985 INFO puppetlabs.facter - requested queries: virtual. 720190 DEBUG puppetlabs.facter - fact "facterversion" has resolved to "3.1.0". 721072 DEBUG puppetlabs.facter - searching "/opt/puppetlabs/facter/facts.d" for external facts. 721325 DEBUG puppetlabs.facter - skipping external facts for "/etc/facter/facts.d": No such file or directory 721537 DEBUG puppetlabs.facter - searching "/etc/puppetlabs/facter/facts.d" for external facts. ... lines removed ... 725496 DEBUG puppetlabs.facter - loading all custom facts. 725667 DEBUG puppetlabs.facter - resolving virtualization facts. 725834 DEBUG puppetlabs.facter - resolving desktop management interface facts. 725978 DEBUG puppetlabs.facter - /sys/class/dmi cannot be accessed: using dmidecode to query DMI information. 726181 DEBUG leatherman.execution:87 - executing command: /usr/sbin/dmidecode 729364 DEBUG | - # dmidecode 2.12 729544 DEBUG | - SMBIOS 2.4 present. 729663 DEBUG | - 72 structures occupying 2032 bytes. 729759 DEBUG | - Table at 0x000EE000. 729888 DEBUG | - Handle 0x, DMI type 0, 24 bytes 730012 DEBUG | - BIOS Information 730134 DEBUG | - Vendor: HP 730271 DEBUG | - Version: P56 730392 DEBUG | - Release Date: 05/02/2011 730508 DEBUG | - Address: 0xF 730625 DEBUG | - Runtime Size: 64 kB 730720 DEBUG | - ROM Size: 4096 kB 730828 DEBUG | - Characteristics: 730947 DEBUG | - PCI is supported 731045 DEBUG | - PNP is supported 731139 DEBUG | - BIOS is upgradeable 731256 DEBUG | - BIOS shadowing is allowed 731367 DEBUG | - ESCD support is available 731487 DEBUG | - Boot from CD is supported 731668 DEBUG | - Selectable boot is supported 731823 DEBUG | - EDD is supported 731937 DEBUG | - 5.25"/360 kB floppy services are supported (int 13h) 732032 DEBUG | - 5.25"/1.2 MB floppy services are supported (int 13h) 732214 DEBUG | - 3.5"/720 kB floppy services are supported (int 13h) 732334 DEBUG | - Print screen service is supported (int 5h) 732431 DEBUG | - 8042 keyboard services are supported (int 9h) 732553 DEBUG | - Serial services are supported (int 14h) 732665 DEBUG | - Printer services are supported (int 17h) 732765 DEBUG | - CGA/mono video services are supported (int 10h) 732882 DEBUG | - ACPI is supported 732960 DEBUG | - USB legacy is supported 733068 DEBUG | - BIOS boot specification is supported 733182 DEBUG | - Function key-initiated network boot is supported 733314 DEBUG | - Targeted content distribution is supported 733434 DEBUG | - Handle 0x0100, DMI type 1, 27 bytes 733535 DEBUG | - System Information 733651 DEBUG | - Manufacturer: HP 733780 DEBUG | - Product Name: ProLiant DL380 G5 733902 DEBUG | - Version: Not Specified 734014 DEBUG | - Serial Number: 734116 DEBUG | - UUID: 3435-3234-435A-4337-345A 734216 DEBUG | - Wake-up Type: Power Switch 734315 DEBUG | - SKU Number: 43352x-xxx 734430 DEBUG | - Family: ProLiant 734563 DEBUG | - Handle 0x0300, DMI type 3, 17 bytes 734652 DEBUG | - Chassis Information 734763 DEBUG | - Manufacturer: HP 734879 DEBUG | - Type: Rack Mount Chassis 734976 DEBUG | - Lock: Not Present 735062 DEBUG | - Version: Not Specified 735172 DEBUG | - Serial Number: x 735286 DEBUG | - Asset Tag: 735408 DEBUG | - Boot-up State: Unknown 735538 DEBUG | - Power Supply State: Unknown 735633 DEBUG | - Thermal State: Unknown 735745 DEBUG | - Security Status: Unknown 735848 DEBUG | - OEM In
Jira (PUP-5082) Ensure that only export, consume, and require relationships can be used with capability resources.
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5082 Ensure that only export, consume, and require relationships can be used with capability resources. Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5083) Fail env catalog compilation if there are unfulfilled dependencies
Title: Message Title Thomas Hallgren commented on PUP-5083 Re: Fail env catalog compilation if there are unfulfilled dependencies The PR that is up now will also assert that no two components exports the same capres. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5213) cannot assign multiple application components to a single node
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5213 cannot assign multiple application components to a single node Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5213) cannot assign multiple application components to a single node
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5213 cannot assign multiple application components to a single node Change By: Thomas Hallgren Sprint: Language Triage 2015-10-14 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5213) cannot assign multiple application components to a single node
Title: Message Title Thomas Hallgren commented on PUP-5213 Re: cannot assign multiple application components to a single node I suspect that this was fixed by PUP-5079 . I get the error if I use an old version where it's not included. I'm not able to reproduce it with what's on master today. Ryan Coleman, can you test with a more recent version and see if the problem persists? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5089) classes should be allowable as application components
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5089 classes should be allowable as application components Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5089) classes should be allowable as application components
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5089 classes should be allowable as application components Change By: Thomas Hallgren Sprint: Language 2015-10- 28 14 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5309) Yum package provider: ensure => latest fails when kernel is updated but not current
Title: Message Title Joshuatly Tee created an issue Puppet / PUP-5309 Yum package provider: ensure => latest fails when kernel is updated but not current Issue Type: Bug Affects Versions: PUP 4.2.2 Assignee: Unassigned Created: 2015/10/05 6:26 AM Environment: PE 2015.2.1, RHEL 7.0 Priority: Normal Reporter: Joshuatly Tee Similar to PUP-4497 , puppet fail to run when there are kernel upgrade that didnt get apply: # yum check-update Loaded plugins: product-id, rhnplugin, subscription-manager
Jira (PUP-5310) password-disclosure-when-changing-a-users-password fails on AIX
Title: Message Title John Duarte created an issue Puppet / PUP-5310 password-disclosure-when-changing-a-users-password fails on AIX Issue Type: Bug Affects Versions: PUP 4.2.3 Assignee: Unassigned Created: 2015/10/05 7:00 AM Environment: AIX 5.3 Priority: Normal Reporter: John Duarte Puppet acceptance test Case tests/ticket_6857_password-disclosure-when-changing-a-users-password.rb fails with the following: Test Case tests/ticket_6857_password-disclosure-when-changing-a-users-password.rb reported: #
Jira (PUP-5311) aix_package_provider test fails on AIX
Title: Message Title John Duarte created an issue Puppet / PUP-5311 aix_package_provider test fails on AIX Issue Type: Bug Affects Versions: PUP 4.3.0 Assignee: Unassigned Created: 2015/10/05 7:02 AM Environment: AIX 5.3 Priority: Normal Reporter: John Duarte Puppet acceptance test Case tests/aix/aix_package_provider.rb fails with the following: Test Case tests/aix/aix_package_provider.rb reported: # Expected /aix package provider is unable to downgrade packages/ to match "\e[mNotice: Compiled catalog for pe-aix-53-acceptance.delivery.puppetlabs.net in environment production in 1.54 seconds\e[0m\n\e[0;32mInfo: Applying configuration version '1443972941'
Jira (PUP-5312) concurrent_catalog_requests test fails on AIX
Title: Message Title John Duarte created an issue Puppet / PUP-5312 concurrent_catalog_requests test fails on AIX Issue Type: Bug Affects Versions: PUP 4.3.0 Assignee: Unassigned Created: 2015/10/05 7:04 AM Priority: Normal Reporter: John Duarte Puppet acceptance test Case tests/concurrency/ticket_2659_concurrent_catalog_requests.rb fails with the following: Test Case tests/concurrency/ticket_2659_concurrent_catalog_requests.rb reported: # Expected /< HTTP\/1.* 200/ to match "sleep: 0509-020 Specify time as a positive integer.\nCurling: https://oxgwrmrqdurja2p.delivery.puppetlabs.net:8140/puppet/v3/catalog/pe-aix-53-acceptance.delivery.puppetlabs.net?environment=production\ncurl: A file or directory in the path name does not exist.\n848050 Completed\n".
Jira (PUP-5313) user resource should_create_with_gid test fails on AIX
Title: Message Title John Duarte created an issue Puppet / PUP-5313 user resource should_create_with_gid test fails on AIX Issue Type: Bug Affects Versions: PUP 4.3.0 Assignee: Unassigned Created: 2015/10/05 7:06 AM Environment: AIX 5.3 Priority: Normal Reporter: John Duarte Puppet acceptance test Case tests/resource/user/should_create_with_gid.rb fails with the following: Test Case tests/resource/user/should_create_with_gid.rb reported: # expected gid 208 but got:
Jira (PUP-5314) user should_manage_shell test fails on AIX
Title: Message Title John Duarte created an issue Puppet / PUP-5314 user should_manage_shell test fails on AIX Issue Type: Bug Affects Versions: PUP 4.3.0 Assignee: Unassigned Created: 2015/10/05 7:08 AM Environment: AIX 5.3 Priority: Normal Reporter: John Duarte Puppet acceptance test case tests/resource/user/should_manage_shell.rb fails with the following Test Case tests/resource/user/should_manage_shell.rb reported: # didn't set the user shell for pl339772
Jira (FACT-1227) Facter returns exit code 1 when using "--puppet" option
Title: Message Title Charlie Sharpsteen commented on FACT-1227 Re: Facter returns exit code 1 when using "--puppet" option I bisected the custom facts shipped with PE that get pluginsynced to /opt/puppetlabs/puppet/cache/lib/facter, and I believe I've isolated to the problem to the pe_version fact: Facter.add("pe_version") do setcode do pe_ver = Facter.value("puppetversion").match(/Puppet Enterprise (\d+\.\d+\.\d+)/) pe_ver[1] if pe_ver end end The issue is that the puppetversion fact was removed in Facter 3, so pe_version attempts to call match on nil, which fails. This appears to result in the exit code of 1 and can be re-produced with the following fact: Facter.add('exit_test') do setcode do
Jira (FACT-780) Running 'facter --puppet' produced no warning/debug messages
Title: Message Title Charlie Sharpsteen commented on FACT-780 Re: Running 'facter --puppet' produced no warning/debug messages I'm re-opening this since we did re-introduce the - puppet flag with FACT- . Running Facter 3.1.0 with -puppet still results in truncated debug output: # facter --version 3.1.0 (commit fc7614d6ba81845757ba7318269fad2b2da08da3) # # facter -p -d > /dev/null 2015-10-05 16:29:07.245505 INFO puppetlabs.facter - executed with command line: -p -d. 2015-10-05 16:29:07.246623 INFO leatherman.ruby:124 - ruby loaded from "/opt/puppetlabs/puppet/lib/libruby.so.2.1.0". 2015-10-05 16:29:07.250679 INFO leatherman.ruby:145 - using ruby version 2.1.6 2015-10-05 16:29:07.269468 INFO puppetlabs.facter - resolving all facts. 2015-10-05 16:29:07.269552 DEBUG
Jira (FACT-780) Running 'facter --puppet' produced no warning/debug messages
Title: Message Title Charlie Sharpsteen updated an issue Facter / FACT-780 Running 'facter --puppet' produced no warning/debug messages Change By: Charlie Sharpsteen Affects Version/s: FACT 3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1227) Facter returns exit code 1 when using "--puppet" option
Title: Message Title Charlie Sharpsteen commented on FACT-1227 Re: Facter returns exit code 1 when using "--puppet" option I've also re-opened FACT-780, which concerns the lack of debug output when --puppet is in use. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5082) Ensure that only export, consume, and require relationships can be used with capability resources.
Title: Message Title Henrik Lindberg commented on PUP-5082 Re: Ensure that only export, consume, and require relationships can be used with capability resources. merged to master at: 9e0fe2c Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5083) Fail env catalog compilation if there are unfulfilled dependencies
Title: Message Title Henrik Lindberg commented on PUP-5083 Re: Fail env catalog compilation if there are unfulfilled dependencies merged to master at: b285a43 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5213) cannot assign multiple application components to a single node
Title: Message Title Henrik Lindberg assigned an issue to Ryan Coleman Puppet / PUP-5213 cannot assign multiple application components to a single node Change By: Henrik Lindberg Assignee: Thomas Hallgren Ryan Coleman Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1247) Facter does not correctly compile on Ubuntu Vivid because the java dependencies are not correctly specified.
Title: Message Title Melissa Stone assigned an issue to qa Facter / FACT-1247 Facter does not correctly compile on Ubuntu Vivid because the java dependencies are not correctly specified. Change By: Melissa Stone Status: Ready for CI Test Assignee: Melissa Stone qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1247) Facter does not correctly compile on Ubuntu Vivid because the java dependencies are not correctly specified.
Title: Message Title Melissa Stone commented on FACT-1247 Re: Facter does not correctly compile on Ubuntu Vivid because the java dependencies are not correctly specified. It looks like this has passed ci Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5016) SysV init script managed by 'init' provider instead of 'debian' provider on Debian8
Title: Message Title William Hopper updated an issue Puppet / PUP-5016 SysV init script managed by 'init' provider instead of 'debian' provider on Debian8 Change By: William Hopper Comment: I've done some digging on the proposed solution of making the debian provider the default on all debians, and found the issue that's currently preventing it from working.In {{Puppet::type.defaultprovider}}, when we come across two default providers we pick the one with the highest specificity score (from {{Puppet::Provider.specificity}}). In this case, systemd wins out over the debian provider, which means the debian provider is tossed back into the 'suitable' list, behind the init provider. Thus, init gets chosen before debian.All of that being said, is adding a second default provider the best approach for this issue? Or should we make our systemd provider smarter for debian? Two defaults seems pretty odd. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5016) SysV init script managed by 'init' provider instead of 'debian' provider on Debian8
Title: Message Title William Hopper commented on PUP-5016 Re: SysV init script managed by 'init' provider instead of 'debian' provider on Debian8 Notes for FR: due to an upstream bug in Ubuntu (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807) sysvinit services like Apache2 will throw an error when enabling. Puppet will see this and also throw an error, but the service will be enabled correctly anyway. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Rachel Kelly updated an issue Facter / FACT-1244 xenu vs. xen0 difference not recognized by Puppet Change By: Rachel Kelly Reporter: Rachel Kelly Rene van der Linden Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1227) Facter returns exit code 1 when using "--puppet" option
Title: Message Title Peter Huene commented on FACT-1227 Re: Facter returns exit code 1 when using "--puppet" option Nice work tracking down a constrained repro! The exception should be caught and an error message (optionally with traceback) should be displayed. This happens when we use a custom fact outside of --puppet so there must be some strange interaction going on that causes the process to exit. I'll take a look at this. We should file a bug for puppetversion missing when - puppet is passed. Puppet sets that fact when it runs normally, so users should expect it to be present when Facter is run with -puppet. Regardless, not gracefully handling this exception is the pressing issue. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1227) Facter returns exit code 1 when using "--puppet" option
Title: Message Title Peter Huene commented on FACT-1227 Re: Facter returns exit code 1 when using "--puppet" option Here's what the pe_version fact does without --puppet: 2015-10-05 10:31:15.385928 DEBUG puppetlabs.facter - custom fact "puppetversion" was not found. 2015-10-05 10:31:15.386067 ERROR puppetlabs.facter - error while resolving custom fact "pe_version": undefined method `match' for nil:NilClass backtrace: /Users/peterhuene/src/facter/release/bar/foo.rb:3:in `block (2 levels) in ' -e:1:in `call' 2015-10-05 10:31:15.386327 DEBUG puppetlabs.facter - fact "pe_version" resolved to null and will not be added. Clearly the exception isn't propagating as expected when Puppet is in the picture. Add Comment
Jira (FACT-1227) Facter returns exit code 1 when using "--puppet" option
Title: Message Title Peter Huene commented on FACT-1227 Re: Facter returns exit code 1 when using "--puppet" option It'll resolve in Puppet, just not facter --puppet. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1243) el acceptance test does not support Scientific or Oracle
Title: Message Title Josh Cooper assigned an issue to qa Facter / FACT-1243 el acceptance test does not support Scientific or Oracle Change By: Josh Cooper Status: Ready for CI Test Assignee: Josh Cooper qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1243) el acceptance test does not support Scientific or Oracle
Title: Message Title Josh Cooper commented on FACT-1243 Re: el acceptance test does not support Scientific or Oracle puppet-agent commit aa3c0a3 passed CI, includes facter e25b2d2, resolving issue /cc Eric Thompson, Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5295) assigning undef/NULL value to class parameters via Hiera doesn't work reliably
Title: Message Title Henrik Lindberg commented on PUP-5295 Re: assigning undef/NULL value to class parameters via Hiera doesn't work reliably The semantics of giving undef as an argument to a resource (class or other) is that the result is the default value of that parameter. This works the same way in the puppet language and when using automatic data binding. Thus, the only way to set an undef is to have it be undef by default. e.g. class foo(Optional[String[1]] $x = undef ) { ... While some users desire it to work the same way as you expected it to work - there are also many that expect the result of giving an undef value to select the default value. (We had a small riot the last time we tried to change this). So, it actually works both reliably and according to specification/expectations, and I doubt this is something that will be changed. It is also consistent the way it is now - irrespective of setting value explicitly myval=>undef, explictly set via looking it up myval=>hiera('myval'), or letting data binding set it - puppet now treats an undef value the same way (it sets the default). As you figured out, the "undef means pick default" only applies at the top level parameter values, and not for values inside arrays or hashes. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (FACT-1239) Tests fail on AIX
Title: Message Title Branan Riley commented on FACT-1239 Re: Tests fail on AIX Preprocessed versions of passing and failing tests look identical to me. That leaves it down to a) a side effect somewhere in how Catch tests are evaluated or b) some sort of code gen issue. Neither of these is going to be a "quick fix". Michael Stahnke Can we just not run the unit tests on AIX for now? This is getting very expensive to investigate, and I don't think we should block shipping on it. If we'd rather run the tests I can probably #ifdef the files that are failing, but I have no way of knowing if this bug will sneak back in to another test sometime - just trying to disable the ones fialing "right now" would leave the AIX build fragile. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1239) Tests fail on AIX
Title: Message Title Michael Stahnke commented on FACT-1239 Re: Tests fail on AIX Sure. (I actually thought were already disabled). Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1227) Facter returns exit code 1 when using "--puppet" option
Title: Message Title Joshua Partlow commented on FACT-1227 Re: Facter returns exit code 1 when using "--puppet" option The pe_version fact is not used in PE 2015.2.1, instead we use pe_server_version. The pe_version and is_pe facts have a complicated life in post aio world: FM-2902 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1239) Tests fail on AIX
Title: Message Title Branan Riley commented on FACT-1239 Re: Tests fail on AIX OK, I actually finally tracked down where in libstdc++ terminate is being called. It appears that there's some sort of sporadic unwinding error causing libstdc++ to terminate the process at the throw site. This is obviously a G++ bug somewhere, but whether it's in codegen or the unwinding library is well beyond my expertise. We could try rebuilding with SJLJ exceptions (which means new GCC build! yay!) - they're slower, but less complex and less reliant on libstdc++ having to be smart about the stack. I'll kick a GCC build that's configured for them and if it works we can discuss the impacts of another compiler build and slower exceptions. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1245) Fix failing AIX tests - facter 3.1.0 (commit 1a39ed205c3c34cc66a73731c4d910a3fb3a42db)
Title: Message Title Josh Cooper commented on FACT-1245 Re: Fix failing AIX tests - facter 3.1.0 (commit 1a39ed205c3c34cc66a73731c4d910a3fb3a42db) John Duarte it looks like all changes are in, could you verify this on AIX? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5285) Systemd service provider only handles .service units, when others can be useful
Title: Message Title Greg Sutcliffe commented on PUP-5285 Re: Systemd service provider only handles .service units, when others can be useful There are definitely others, "socket" leaps to mind, which gives xinetd-style service activation on port connection (in other words, what you'd do with TFTP). I like the idea of adding a new attribute to the service provider where systemd is concerned, and have that default to "service". We probably also want to append it to the systemctl calls, so that you get "systemctl enable foo.service" rather than "systemctl enable foo" which would guard against Ed's point. My puppet coding skills are somewhat rusty but I can have a go at a PR, unless Ed wants to do it... Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5295) assigning undef/NULL value to class parameters via Hiera doesn't work reliably
Title: Message Title Christoph Bihler commented on PUP-5295 Re: assigning undef/NULL value to class parameters via Hiera doesn't work reliably uhm, I think I'm not getting something: according to docs of datatype Default and as far as I understand the intention of this datatype/keyword, it was created explicitly to solve the problem of not being able to set undef when a default is already defined. In fact, it's even described that way here word by word. I don't wanna be impolite, but I think the behaviour you're describing and I am experiencing contradicts the idea of all this and in fact IS a bug that has to be fixed, no matter if there are people out there, who expect something else. As well, fixing most of the manifests out there would be pretty easy by exchanging undef with default. I can feel with you that changing this would lead to "small riots" and might cause some work but IMHO this is just caused by environments in which code is buggy or respectively simply not clean. Is it suitable to keep a bug, just because fixing it would cause some work? plz, think about this again Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1248) Hidden fact serialnumber is displayed by default on AIX
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1248 Hidden fact serialnumber is displayed by default on AIX Change By: Kylo Ginsberg Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1248) Hidden fact serialnumber is displayed by default on AIX
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1248 Hidden fact serialnumber is displayed by default on AIX Change By: Kylo Ginsberg Sprint: Client 2015-10-28 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1245) Fix failing AIX tests - facter 3.1.0 (commit 1a39ed205c3c34cc66a73731c4d910a3fb3a42db)
Title: Message Title Kylo Ginsberg commented on FACT-1245 Re: Fix failing AIX tests - facter 3.1.0 (commit 1a39ed205c3c34cc66a73731c4d910a3fb3a42db) AFAICT we still need a fix for FACT-1248. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5148) Get pre-suites working for Huawei 6 (PowerPC) for Puppet
Title: Message Title Michael Stahnke updated an issue Puppet / PUP-5148 Get pre-suites working for Huawei 6 (PowerPC) for Puppet Change By: Michael Stahnke Sprint: RE 2015- 10 11 - 21 04 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1200) Get pre-suites working for Huawei 6 (PowerPC) for Facter
Title: Message Title Michael Stahnke updated an issue Facter / FACT-1200 Get pre-suites working for Huawei 6 (PowerPC) for Facter Change By: Michael Stahnke Sprint: RE 2015- 10 11 - 21 04 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1245) Fix failing AIX tests - facter 3.1.0 (commit 1a39ed205c3c34cc66a73731c4d910a3fb3a42db)
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1245 Fix failing AIX tests - facter 3.1.0 (commit 1a39ed205c3c34cc66a73731c4d910a3fb3a42db) Change By: John Duarte Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2014) (maint) Lint fixes
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2014 (maint) Lint fixes Issue Type: Bug Assignee: Unassigned Created: 2015/10/05 1:42 PM Priority: Normal Reporter: gepetto-bot This patch fixes some of the lint warnings/errors we've been getting on the forge. In some cases I've fixed real bugs also, in particular double quotes/single quotes in cases, which would have broken variable interpolation. Signed-off-by: Ken Barber Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (FACT-1245) Fix failing AIX tests - facter 3.1.0 (commit 1a39ed205c3c34cc66a73731c4d910a3fb3a42db)
Title: Message Title John Duarte commented on FACT-1245 Re: Fix failing AIX tests - facter 3.1.0 (commit 1a39ed205c3c34cc66a73731c4d910a3fb3a42db) Kylo Ginsberg since this ticket is about fixing the problems with the tests, I think we can close this ticket when the facter_with_invalid_locale and facts/ruby tests are shown to pass. The verify_facts test will be expected to fail and can be tracked by FACT-1248. tl;dr I don't think FACT-1248 is a blocker for this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1239) Tests fail on AIX
Title: Message Title Branan Riley commented on FACT-1239 Re: Tests fail on AIX It looks like GCC doesn't want to build with --enable-sjlj-exceptiosn... it's possible there's another option related to it that I need to pass, but this is a dead-end at the moment :/ Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2014) (maint) Lint fixes
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-2014 (maint) Lint fixes Change By: Kenneth Barber Assignee: Kenneth Barber Scope Change Category: Adopted Scope Change Reason: Just noticed we had some lint bugs Story Points: 1 Sprint: PuppetDB 2015-10-07 Scrum Team: PuppetDB Fix Version/s: PDB module-5.0.x Component/s: Module Add Comment
Jira (PUP-5016) SysV init script managed by 'init' provider instead of 'debian' provider on Debian8
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5016 SysV init script managed by 'init' provider instead of 'debian' provider on Debian8 Change By: Kylo Ginsberg Fix Version/s: PUP 4.2.3 Fix Version/s: PUP 4.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5016) SysV init script managed by 'init' provider instead of 'debian' provider on Debian8
Title: Message Title Kylo Ginsberg commented on PUP-5016 Re: SysV init script managed by 'init' provider instead of 'debian' provider on Debian8 William Hopper can you add a Release Notes Summary field, and update the Release Notes field also? Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5016) SysV init script managed by 'init' provider instead of 'debian' provider on Debian8
Title: Message Title William Hopper updated an issue Puppet / PUP-5016 SysV init script managed by 'init' provider instead of 'debian' provider on Debian8 Change By: William Hopper Release Notes Summary: In Debian 8 and Ubuntu 15.04, Systemd was introduced as the default service manager. However, many packages and services still utilize older SysVInit scripts to manage services, necessitating the systemd-sysv-init compatibility layer.This layer confused Puppet into improperly managing SysVInit services on these platforms. The final outcome of this ticket is that Puppet now falls back to the Debian service provider when managing a service without a Systemd unit file. All services should be enable-able, which they were not before due to Puppet incorrectly falling back to the Init provider. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1245) Fix failing AIX tests - facter 3.1.0 (commit 1a39ed205c3c34cc66a73731c4d910a3fb3a42db)
Title: Message Title Kylo Ginsberg commented on FACT-1245 Re: Fix failing AIX tests - facter 3.1.0 (commit 1a39ed205c3c34cc66a73731c4d910a3fb3a42db) Thanks for clarifying. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1614) anonymize path and value independently for structured facts
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1614 anonymize path and value independently for structured facts Change By: Wyatt Alt Sprint: PuppetDB 2015-10- 21 07 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1614) anonymize path and value independently for structured facts
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1614 anonymize path and value independently for structured facts Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1614) anonymize path and value independently for structured facts
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1614 anonymize path and value independently for structured facts Change By: Wyatt Alt Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1614) anonymize path and value independently for structured facts
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1614 anonymize path and value independently for structured facts Change By: Wyatt Alt Scope Change Category: Adopted Scope Change Reason: had some time Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5316) puppet agent paths test should be skipped on non-AIO test runs
Title: Message Title William Hopper created an issue Puppet / PUP-5316 puppet agent paths test should be skipped on non-AIO test runs Issue Type: Bug Assignee: Unassigned Created: 2015/10/05 2:40 PM Priority: Normal Reporter: William Hopper acceptance/tests/ensure_puppet-agent_paths.rb fails when run through ci:test:git. This test should only be run through ci:test:aio. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5317) Master should return 74 when puppet user doesn't exist
Title: Message Title William Hopper created an issue Puppet / PUP-5317 Master should return 74 when puppet user doesn't exist Issue Type: Bug Assignee: Unassigned Created: 2015/10/05 2:43 PM Priority: Normal Reporter: William Hopper Previously, when trying to run a master and the puppet user didn't exist, we exited with 74. In commit 144ea123965, a change was made to more gracefully handle failing, but raised a Puppet::Error instead of exiting with 74 as before. This causes puppet_manages_own_configuration_in_robust_manner.rb to fail. We should return to the previous behavior. Add Comment This message was sent by Atlassian JIRA (v6.4.11#6
Jira (PUP-5287) install_options capability on Solaris provider "sun" & "pkg" - clone
Title: Message Title Rachel Kelly updated an issue Puppet / PUP-5287 install_options capability on Solaris provider "sun" & "pkg" - clone Change By: Rachel Kelly Summary: install_options capability on Solaris provider "sun" & "pkg" - clone Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5287) install_options capability on Solaris provider "sun" & "pkg" - clone
Title: Message Title Rachel Kelly updated an issue Puppet / PUP-5287 install_options capability on Solaris provider "sun" & "pkg" - clone Change By: Rachel Kelly In this particular situation, there are several Puppet setups which they are trying to use the install_options functionality of the "sun" provider & "pkg" providers on Solaris. Puppet supports sun /pkg , but it does not, it appears, support all its pieces as install_options is not available. Clients want this because they are deploying packages to their Solaris agents and when they try to use install_options, it adds it to the command in double quotes, rendering the command ineffective.Potentially tangentially they also need to know how to put a file in a puppet repo (central repository) for it to be found without using source?Please let me know what other information you need on this. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5295) assigning undef/NULL value to class parameters via Hiera doesn't work reliably
Title: Message Title Henrik Lindberg commented on PUP-5295 Re: assigning undef/NULL value to class parameters via Hiera doesn't work reliably You are right in that the default value (of type Default) can be made to differentiate between the two cases, but there is no language support for it yet. For this to be (IMHO 'cleaned up') we need to face the minor riot at some point and also add the ability to produce a literal default in hiera (or we we are stuck with the ambiguity if NULL in Yaml means "use the default", or "set undef". I am reluctant to make this change in the data binding alone - hence closing this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2015) (maint) Remove outdated service from bootstrap.cfg
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2015 (maint) Remove outdated service from bootstrap.cfg Issue Type: Bug Assignee: Unassigned Created: 2015/10/05 3:12 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.
Jira (PUP-5318) install_repos_on fails when master VM has agent role and agent VM is windows.
Title: Message Title Alice Nodelman moved an issue Puppet / PUP-5318 install_repos_on fails when master VM has agent role and agent VM is windows. Change By: Alice Nodelman Workflow: Quality Engineering Scrum Team Workflow Key: BKR PUP - 567 5318 Project: Beaker Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5318) install_repos_on fails when master VM has agent role and agent VM is windows.
Title: Message Title Alice Nodelman assigned an issue to Unassigned Puppet / PUP-5318 install_repos_on fails when master VM has agent role and agent VM is windows. Change By: Alice Nodelman Assignee: Alice Nodelman Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5318) install_repos_on fails when master VM has agent role and agent VM is windows.
Title: Message Title Alice Nodelman commented on PUP-5318 Re: install_repos_on fails when master VM has agent role and agent VM is windows. Transitioning to become puppet bug. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5317) Master should return 74 when puppet user doesn't exist
Title: Message Title William Hopper updated an issue Puppet / PUP-5317 Master should return 74 when puppet user doesn't exist Change By: William Hopper Previously, when trying to run a master and the puppet user didn't exist, we exited with {{74}}.In commit 144ea123965, a change was made to more gracefully handle failing, but raised a {{Puppet::Error}} instead of exiting with 74 as before. This causes {{puppet_manages_own_configuration_in_robust_manner.rb}} to fail.We should return go back to the previous behavior exiting with {{74}} . Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5287) install_options capability on Solaris provider "sun" & "pkg" - clone
Title: Message Title Rachel Kelly updated an issue Puppet / PUP-5287 install_options capability on Solaris provider "sun" & "pkg" - clone Change By: Rachel Kelly In this particular situation, there are several Puppet setups which they are trying to use the install_options functionality of the "sun" & "pkg" providers on Solaris. Puppet supports sun/pkg, but it does not, it appears, support all its pieces as install_options is not available. Clients want this because they are When deploying packages to their Solaris agents and when they try trying to use install_options, it adds it to the command in double quotes, rendering the command ineffective. The addition of install_options will also enable manipulation of boot environments as they are generated. Potentially tangentially they also need to know how to put a file in a puppet repo (central repository) for it to be found without using source?Please let me know what other information you need on this. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2003) facts GC can exceed jdbc max message size if too many paths are deleted
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2003 facts GC can exceed jdbc max message size if too many paths are deleted Change By: Wyatt Alt Fix Version/s: PDB 2.3.x Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5287) install_options capability on Solaris provider "sun" & "pkg" - clone
Title: Message Title Peter Huene updated an issue Puppet / PUP-5287 install_options capability on Solaris provider "sun" & "pkg" - clone Change By: Peter Huene Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2003) facts GC can exceed jdbc max message size if too many paths are deleted
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2003 facts GC can exceed jdbc max message size if too many paths are deleted Change By: Wyatt Alt Affects Version/s: PDB 3.0.2 Affects Version/s: PDB 2.3.x Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2006) Move dual-db facts test to posgresql
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2006 Move dual-db facts test to posgresql Change By: Kenneth Barber Fix Version/s: PDB 3.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1430) puppetlabs-puppetdb should be able to manage /etc/sysconfig/puppetdb
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1430 puppetlabs-puppetdb should be able to manage /etc/sysconfig/puppetdb Change By: Kenneth Barber Fix Version/s: PDB module-5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1614) anonymize path and value independently for structured facts
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1614 anonymize path and value independently for structured facts Change By: Wyatt Alt Fix Version/s: PDB 3.1.x Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2012) Adjust PDB extensions to use available-postgres-configs, etc.
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2012 Adjust PDB extensions to use available-postgres-configs, etc. Change By: Kenneth Barber Fix Version/s: PDB 3.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1997) Repeatable PDB benchmarks
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1997 Repeatable PDB benchmarks Change By: Kenneth Barber Fix Version/s: PDB 3.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5085) Test that produced/consumed resources depend on the producer/consumer
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-5085 Test that produced/consumed resources depend on the producer/consumer Change By: Eric Thompson Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5287) install_options capability on Solaris provider "sun" & "pkg" - clone
Title: Message Title William Hopper commented on PUP-5287 Re: install_options capability on Solaris provider "sun" & "pkg" - clone Possibly related (though my Solaris foo is weak): commit 2e63e307b (from way, way back in 2012) refactored install_options in the sun provider. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5009) Fix "git" acceptance tests for fedora-22
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5009 Fix "git" acceptance tests for fedora-22 Change By: Josh Cooper Summary: Fix "git" acceptance tests for fedora-22 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-997) Add Ubuntu 14.04/trusty to acceptance testing
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-997 Add Ubuntu 14.04/trusty to acceptance testing Change By: Kenneth Barber Sprint: PuppetDB 2015-10-21 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2016) PuppetDB 2.3.8 Release
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2016 PuppetDB 2.3.8 Release Issue Type: Task Assignee: Wyatt Alt Created: 2015/10/05 5:02 PM Priority: Normal Reporter: Wyatt Alt See https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You receive
Jira (PDB-2019) Update documentation indexes for new major release
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2019 Update documentation indexes for new major release Issue Type: Sub-task Assignee: Unassigned Created: 2015/10/05 5:03 PM Priority: Normal Reporter: Wyatt Alt The current documentation indexes need to be updated for a final release. The main index needs the release to be moved into the stable section, and the index for this release needs the pre-release meesage removed. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-2017) Is checklist current
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2017 Is checklist current Issue Type: Sub-task Assignee: Unassigned Created: 2015/10/05 5:03 PM Priority: Normal Reporter: Wyatt Alt Do sub-tickets here match steps in https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process? And do those steps need updating for any recent tooling changes? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-2027) Push tag
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2027 Push tag Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/10/05 5:03 PM Priority: Normal Reporter: Wyatt Alt Push the tag made earlier up to the main public repo for the branch in question. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You rec
Jira (PDB-2028) Update the downloads page
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2028 Update the downloads page Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/10/05 5:03 PM Priority: Normal Reporter: Wyatt Alt Update the downloads page with the public download locations and new version information. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-2029) Send out announcements
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2029 Send out announcements Issue Type: Sub-task Assignee: Unassigned Created: 2015/10/05 5:03 PM Priority: Normal Reporter: Wyatt Alt Send out the release notes in the release format on puppet-users, puppet-dev and puppet-announce. Obtain a bit.ly link to such a thing from marketing and twitter it out, and send a PSA message to IRC channels #puppet and #puppet-dev. Update our hipchat channel with the new link. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-2024) Smoke test packages
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2024 Smoke test packages Issue Type: Sub-task Assignee: Unassigned Created: 2015/10/05 5:03 PM Priority: Normal Reporter: Wyatt Alt Procedure may vary by project and point in the release cycle. Ask around. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-2018) Update changelog/release notes
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2018 Update changelog/release notes Issue Type: Sub-task Assignee: Unassigned Created: 2015/10/05 5:03 PM Priority: Normal Reporter: Wyatt Alt Update the changelog/release notes in documentation/changes.md Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-2025) Go/no-go meeting
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2025 Go/no-go meeting Issue Type: Sub-task Assignee: Unassigned Created: 2015/10/05 5:03 PM Priority: Normal Reporter: Wyatt Alt Should include: dev, docs, product, qa, releng Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-2020) Ensure tests are passing
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2020 Ensure tests are passing Issue Type: Sub-task Assignee: Unassigned Created: 2015/10/05 5:03 PM Priority: Normal Reporter: Wyatt Alt All tests (spec, acceptance) should be passing on all platforms. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-2023) Tag the release and create packages
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2023 Tag the release and create packages Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/10/05 5:03 PM Priority: Normal Reporter: Wyatt Alt Developer provides the SHA Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because
Jira (PDB-2021) Is there a bug targeted at the release for every commit?
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2021 Is there a bug targeted at the release for every commit? Issue Type: Sub-task Assignee: Unassigned Created: 2015/10/05 5:03 PM Priority: Normal Reporter: Wyatt Alt Ensure that all commits in git between the last and current release have corresponding tickets pointing at this release. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-2030) Push changes to pe-puppetdb branch
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2030 Push changes to pe-puppetdb branch Issue Type: Sub-task Assignee: Unassigned Created: 2015/10/05 5:04 PM Priority: Normal Reporter: Wyatt Alt These changes will need to be pushed to the relevant branch for pe-puppetdb Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-2022) Is there a commit for every bug targeted at the release?
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2022 Is there a commit for every bug targeted at the release? Issue Type: Sub-task Assignee: Unassigned Created: 2015/10/05 5:03 PM Priority: Normal Reporter: Wyatt Alt Ensure that all tickets targetted at this release have corresponding commits in git. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-2026) Packages pushed
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2026 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/10/05 5:03 PM Priority: Normal Reporter: Wyatt Alt Distribute the packages previously built into their public places. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received t
Jira (PDB-2031) Close all resolved tickets and release version in Jira
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2031 Close all resolved tickets and release version in Jira Issue Type: Sub-task Assignee: Unassigned Created: 2015/10/05 5:04 PM Priority: Normal Reporter: Wyatt Alt Ensure all tickets that were previously resolved are marked now as closed. Ensure the version in Jira is released. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5317) Master should return 74 when puppet user doesn't exist
Title: Message Title William Hopper updated an issue Puppet / PUP-5317 Master should return 74 when puppet user doesn't exist Change By: William Hopper Scope Change Category: Adopted Scope Change Reason: Discovered while investigating git acceptance failures Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5317) Master should return 74 when puppet user doesn't exist
Title: Message Title William Hopper updated an issue Puppet / PUP-5317 Master should return 74 when puppet user doesn't exist Change By: William Hopper Sprint: AM 2015-10-07 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1925) PQL: Update prototype so it reflects latest query design & decisions
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1925 PQL: Update prototype so it reflects latest query design & decisions Change By: Kenneth Barber Sprint: PuppetDB 2015- 10 11 - 21 4 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.