Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used
Title: Message Title Charlie Sharpsteen commented on PUP-7814 Re: HTTPS file sources with non-puppet-trusted certs can't be used Aha, that makes a lot of sense. to that. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.203766.1501710671000.45884.1565136540487%40Atlassian.JIRA.
Jira (PDOC-286) Break down PDOC-262 description into individual issues
Title: Message Title Jesse Scott created an issue Puppet Strings / PDOC-286 Break down PDOC-262 description into individual issues Issue Type: Task Assignee: Unassigned Created: 2019/08/06 4:56 PM Priority: Normal Reporter: Jesse Scott Step one of resolving these issues is breaking down all the individual bugs here into their own tickets. It may end up being that some of the resulting tickets are duplicates of one another but we can figure that out as we triage them. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used
Title: Message Title Josh Cooper commented on PUP-7814 Re: HTTPS file sources with non-puppet-trusted certs can't be used Oh sorry, I'm not suggesting we continue with the workaround. The two proposed actions above would eliminate the need to do that, as puppet would be able to load CA certs from additional locations instead of trying to "push" CA certs into locations puppet already knows about. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.203766.1501710671000.45836.1565135821342%40Atlassian.JIRA.
Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used
Title: Message Title Charlie Sharpsteen commented on PUP-7814 Re: HTTPS file sources with non-puppet-trusted certs can't be used In my opinion, adding stuff to /opt/puppetlabs/puppet/ssl is currently an unsupported workaround. I think it would make a great official solution to this problem, but it needs: Documentation. Persistence through upgrades. Test coverage. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.203766.1501710671000.45811.1565135340317%40Atlassian.JIRA.
Jira (PDOC-285) Infer missing docs types from arguments
Title: Message Title Jesse Scott assigned an issue to Glenn Sarti Puppet Strings / PDOC-285 Infer missing docs types from arguments Change By: Jesse Scott Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318762.1564488282000.45794.1565134860329%40Atlassian.JIRA.
Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used
Title: Message Title
Josh Cooper commented on PUP-7814
Re: HTTPS file sources with non-puppet-trusted certs can't be used
I tested this and confirmed the following when using an https file source:
Connections to non-puppet SSL servers, such as source => 'https://github.com/path/to', succeed if the root CA cert is in CA bundle in the puppet-agent package. It resides in /opt/puppetlabs/puppet/ssl/{cert.pem,certs}, and comes from https://github.com/puppetlabs/puppet-ca-bundle.
Connections to non-puppet SSL servers fail if the CA cert is only in the system CA bundle, such as /etc/pki/ca-trust/source/anchors. This is common for enterprise customers that have a root CA not issued from a trusted third party like VeriSign, etc.
Connections to puppet SSL servers fail since puppet's CA cert is not in /opt/puppetlabs/puppet/ssl/cert.pem. This is the issue Charlie Sharpsteen mentioned above.
The current workaround is to add the missing root CA to /opt/puppetlabs/puppet/ssl/cert.pem or the /opt/puppetlabs/puppet/ssl/certs directory. In the latter case, the /opt/puppetlabs/puppet/bin/c_rehash command must be executed so openssl can load the cert. As mentioned elsewhere, this needs to be done after each puppet-agent upgrade. I propose we do the following:
Add a puppet setting for the system cert store directory. By default, the setting would be nil. If set to a directory, then call Net::HTTP#ca_path= with the directory containing certificates in PEM format, such as /etc/ssl/certs. The cert rehashing process should occur outside of puppet, such as when the ca-certificates package is updated. This would fix case 2 above.
When using https file sources, always trust the puppet CA and the puppet-agent CA bundle. This would fix case 3 above.
Add Comment
Jira (PDB-4471) Expose catalog inputs query endpoints via PQL
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4471 Expose catalog inputs query endpoints via PQL Issue Type: New Feature Assignee: Unassigned Created: 2019/08/06 3:34 PM Priority: Normal Reporter: Austin Blatt Current, we've only implemented AST support for the catalog inputs query endpoints. It would be nice to maintain as many features as possible that are available from PQL since it is more user-friendly. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1469) SPIKE: Support remote state for terraform inventory plugin
Title: Message Title Lucy Wyman assigned an issue to Unassigned Puppet Task Runner / BOLT-1469 SPIKE: Support remote state for terraform inventory plugin Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316121.1562857319000.45618.1565129760171%40Atlassian.JIRA.
Jira (PUP-5109) Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems
Title: Message Title Josh Cooper assigned an issue to Kris Bosland Puppet / PUP-5109 Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems Change By: Josh Cooper Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.95553.144084808.45583.1565128741077%40Atlassian.JIRA.
Jira (PUP-5109) Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5109 Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems Change By: Josh Cooper Sprint: Coremunity Hopper Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.95553.144084808.45591.1565128741116%40Atlassian.JIRA.
Jira (PDB-4456) Add support for import/export for "replace catalog inputs"
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4456 Add support for import/export for "replace catalog inputs" Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.317966.1563991828000.45451.1565126160319%40Atlassian.JIRA.
Jira (BOLT-1476) Kerberos - Fix the winrm gem and OMI server incompatibility
Title: Message Title
Ethan Brown updated an issue
Puppet Task Runner / BOLT-1476
Kerberos - Fix the winrm gem and OMI server incompatibility
Change By:
Ethan Brown
TravisCI Kerberos specs are currently disabled because the winrm gem and OMI server don't interoperate correctly when using Kerberos authentication.BOLT-1475 describes setting up a new development environment container to reproduce the problem / setup the system for better debugging. This ticket is about debugging / resolving the actual problem, which requires building OMI server from source and testing it in the dev environment. Problems typically manifest with a stack trace like {noformat}root@linuxdev:/# ./bolt-kerberos-test.sh Started on omiserver.bolt.test...Finished on omiserver.bolt.test: STDOUT:boltSuccessful on 1 node: winrm://omiserver.bolt.test:5985Ran on 1 node in 0.87 secondsStarted on omiserver.bolt.test...Finished on omiserver.bolt.test: STDOUT:boltSuccessful on 1 node: winrm://omiserver.bolt.test:5986Ran on 1 node in 0.93 secondsAnalytics opt-out is set, analytics will be disabledCould not read inventory file: /root/.puppetlabs/bolt/inventory.yamlDid not find config for winrm://omiserver.bolt.test:5985 in inventorySkipping submission of 'command_run' screenview because analytics is disabledStarted with 100 max thread(s)Starting: command 'whoami' on winrm://omiserver.bolt.test:5985Skipping submission of 'Transport initialize' event because analytics is disabledRunning command 'whoami' on ["winrm://omiserver.bolt.test:5985"]Started on omiserver.bolt.test...Running command 'whoami' on winrm://omiserver.bolt.test:5985Closed session "\xB5" from ASCII-8BIT to UTF-8 /root/bolt/lib/bolt/result.rb:124:in `encode' /root/bolt/lib/bolt/result.rb:124:in `to_json' /root/bolt/lib/bolt/result.rb:124:in `to_json' /root/bolt/lib/bolt/executor.rb:226:in `with_node_logging' /root/bolt/lib/bolt/executor.rb:236:in `block (2 levels) in run_command' /root/bolt/lib/bolt/executor.rb:103:in `block (3 levels) in queue_execute' /root/bolt/.bundle/gems/ruby/2.5.0/gems/concurrent-ruby-1.1.5/lib/concurrent/executor/ruby_thread_pool_executor.rb:348:in `run_task' /root/bolt/.bundle/gems/ruby/2.5.0/gems/concurrent-ruby-1.1.5/lib/concurrent/executor/ruby_thread_pool_executor.rb:337:in `block (3 levels) in create_worker' /root/bolt/.bundle/gems/ruby/2.5.0/gems/concurrent-ruby-1.1.5/lib/concurrent/executor/ruby_thread_pool_executor.rb:320:in `loop' /root/bolt/.bundle/gems/ruby/2.5.0/gems/concurrent-ruby-1.1.5/lib/concurrent/executor/ruby_thread_pool_executor.rb:320:in `block (2 levels) in create_worker' /root/bolt/.bundle/gems/ruby/2.5.0/gems/concurrent-ruby-1.1.5/lib/concurrent/executor/ruby_thread_pool_executor.rb:319:in `catch' /root/bolt/.bundle/gems/ruby/2.5.0/gems/concurrent-ruby-1.1.5/lib/concurrent/executor/ruby_thread_pool_executor.rb:319:in `block in create_worker' /root/bolt/.bundle/gems/ruby/2.5.0/gems/logging-2.2.2/lib/logging/diagnostic_context.rb:474:in `block in create_with_logging_context'Failed on omiserver.bolt.test: �
Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Thomas Kishel commented on PUP-6382 Re: Add "Automatic (delayed start)" as option for Service Resource on Windows Maybe ... # Service config codes # https://docs.microsoft.com/en-us/windows/win32/api/winsvc/nf-winsvc-changeserviceconfig2w SERVICE_CONFIG_DESCRIPTION = 0x0001 SERVICE_CONFIG_FAILURE_ACTIONS = 0x0002 SERVICE_CONFIG_DELAYED_AUTO_START = 0x0003 SERVICE_CONFIG_FAILURE_ACTIONS_FLAG = 0x0004 SERVICE_CONFIG_SERVICE_SID_INFO = 0x0005 SERVICE_CONFIG_REQUIRED_PRIVILEGES_INFO = 0x0006 SERVICE_CONFIG_PRESHUTDOWN_INFO = 0x0007 SERVICE_CONFIG_TRIGGER_INFO = 0x0008 SERVICE_CONFIG_PREFERRED_NODE = 0x0009 SERVICE_CONFIG_LAUNCH_PROTECTED = 0x0012
Jira (BOLT-1451) Automatically call apply_prep before `resources` step in YAML plans
Title: Message Title
Cas Donoghue updated an issue
Puppet Task Runner / BOLT-1451
Automatically call apply_prep before `resources` step in YAML plans
Change By:
Cas Donoghue
Currently, if the user needs to {{apply_prep}} before a {{resources}} step in a YAML plan, they need to have an {{eval}} step that calls it. This is a bit unnatural in a YAML plan and requires some more knowledge before successfully using the {{resources}} step.We should figure out some way to automatically call {{apply_prep}} on the user's behalf, potentially either the first time a resources step is encountered or every time a resources step is encountered. We could also add a parameter to the resources step to toggle whether or not to apply_prep beforehand. UPDATE:Ideally we would be able to track whether apply_prep is necessary for each time. As a starting point we will just implement the easier solution which appears to be to just call apply_prep each time. As we learn more about how to apply_prep smarter we can improve.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1451) Automatically call apply_prep before `resources` step in YAML plans
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1451 Automatically call apply_prep before `resources` step in YAML plans Change By: Cas Donoghue Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315003.1562084948000.45007.1565117700334%40Atlassian.JIRA.
Jira (PUP-9585) Do not output password for user type if it is marked Sensitive
Title: Message Title Kris Bosland updated an issue Puppet / PUP-9585 Do not output password for user type if it is marked Sensitive Change By: Kris Bosland Release Notes Summary: User providers will not output exec command lines with passwords during debugging level logging. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302109.1553793067000.44980.1565116800472%40Atlassian.JIRA.
Jira (PUP-9914) v6.7.0 Breaks camptocamp-postfix
Title: Message Title Nirupama Mantha updated an issue Puppet / PUP-9914 v6.7.0 Breaks camptocamp-postfix Change By: Nirupama Mantha Fix Version/s: PUP 6.7.1 Fix Version/s: PUP 6.7.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.317861.1563928891000.44932.1565116321019%40Atlassian.JIRA.
Jira (BOLT-1504) Update gems and modules shipped with bolt
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1504 Update gems and modules shipped with bolt Change By: Cas Donoghue Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.319673.1565031563000.44776.1565115240333%40Atlassian.JIRA.
Jira (BOLT-1504) Update gems and modules shipped with bolt
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1504 Update gems and modules shipped with bolt Change By: Cas Donoghue Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.319673.1565031563000.44774.1565115180433%40Atlassian.JIRA.
Jira (PDB-4370) Adjust storage to accommodate catalog inputs
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4370 Adjust storage to accommodate catalog inputs Change By: Austin Blatt Fix Version/s: PDB 6.8.0 Fix Version/s: PDB 6.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308641.1557869051000.44757.1565114700587%40Atlassian.JIRA.
Jira (PDB-4372) Store catalog inputs when they are (optionally) received by submit catalog
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4372 Store catalog inputs when they are (optionally) received by submit catalog Change By: Austin Blatt Fix Version/s: PDB 6.8.0 Fix Version/s: PDB 6.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308643.1557869418000.44751.1565114700553%40Atlassian.JIRA.
Jira (PDB-4470) Add catalog-input-contents endpoint
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4470 Add catalog-input-contents endpoint Issue Type: Bug Assignee: Unassigned Created: 2019/08/06 10:55 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (BOLT-1502) Do not rely on wrapper script for run-as with stdin task input
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1502 Do not rely on wrapper script for run-as with stdin task input Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.319291.1564682997000.44554.1565109960576%40Atlassian.JIRA.
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1466 Inventory configuration precedence is confusing Change By: Lucy Wyman Labels: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315922.1562780625000.44522.1565109480638%40Atlassian.JIRA.
Jira (PUP-9585) Do not output password for user type if it is marked Sensitive
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9585 Do not output password for user type if it is marked Sensitive Change By: Josh Cooper Fix Version/s: PUP 6.0.z Fix Version/s: PUP 5.5.z Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 Fix Version/s: PUP 6.0.11 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to
Jira (BOLT-1451) Automatically call apply_prep before `resources` step in YAML plans
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1451 Automatically call apply_prep before `resources` step in YAML plans Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315003.1562084948000.44486.1565109121410%40Atlassian.JIRA.
Jira (BOLT-1451) Automatically call apply_prep before `resources` step in YAML plans
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1451 Automatically call apply_prep before `resources` step in YAML plans Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315003.1562084948000.44484.1565109121380%40Atlassian.JIRA.
Jira (PUP-9585) Do not output password for user type if it is marked Sensitive
Title: Message Title Josh Cooper commented on PUP-9585 Re: Do not output password for user type if it is marked Sensitive Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/bc7b9de55162b496751f95b9993c0d2acf59a9de Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302109.1553793067000.44479.1565108820525%40Atlassian.JIRA.
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Branan Riley commented on PUP-9041 Re: AIX nim provider can't be used on a NIM master Our nim master is part of our production infra, so I wouldn't want to try to test anything there. In the past we'd talked about setting up one of our POWER machines as a "bare metal" test environment just for stuff like this, but we never made any progress there. I'm unsure what our AIX hardware allocation looks like right now and whether that's still something feasible (/cc Ken Johnson). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.267945.153332494.3.1565107680719%40Atlassian.JIRA.
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Gabriel Nagy commented on PUP-9041 Re: AIX nim provider can't be used on a NIM master Erik Hansen, Sean McDonald, Branan Riley, is there a way we can acceptance test this? we only have nim clients on nspooler. I did a rudimentary fix for this but I'm not sure how to test it on a nim master Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.267945.153332494.44298.1565103840465%40Atlassian.JIRA.
Jira (FACT-1978) Facter 2.5.5 fails to detect Amazon Linux 2 (AMI amzn2-ami-hvm-2.0.20190618-x86_64-gp2)
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1978 Facter 2.5.5 fails to detect Amazon Linux 2 (AMI amzn2-ami-hvm-2.0.20190618-x86_64-gp2) Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318955.1564566972000.44264.1565099760764%40Atlassian.JIRA.
Jira (FACT-1978) Facter 2.5.5 fails to detect Amazon Linux 2 (AMI amzn2-ami-hvm-2.0.20190618-x86_64-gp2)
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1978 Facter 2.5.5 fails to detect Amazon Linux 2 (AMI amzn2-ami-hvm-2.0.20190618-x86_64-gp2) Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318955.1564566972000.44266.1565099760779%40Atlassian.JIRA.
Jira (PUP-9465) group resource type misunderstands/misuses libuser
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9465 group resource type misunderstands/misuses libuser Change By: Mihai Buzgau Team: Platform OS Night's Watch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.293306.1548368109000.44260.1565099700614%40Atlassian.JIRA.
Jira (PUP-9465) group resource type misunderstands/misuses libuser
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9465 group resource type misunderstands/misuses libuser Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.293306.1548368109000.44256.1565099700566%40Atlassian.JIRA.
Jira (FACT-1977) Create FacterNG skeleton
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-1977 Create FacterNG skeleton Change By: Sebastian Miclea Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318945.1564552155000.44172.1565097240312%40Atlassian.JIRA.
Jira (FACT-1957) Create class hierarchy that accommodates nested facts
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-1957 Create class hierarchy that accommodates nested facts Change By: Sebastian Miclea Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.317049.1563427805000.44174.1565097240321%40Atlassian.JIRA.
Jira (PUP-9937) Docker Image - wrong version
Title: Message Title Dennis commented on PUP-9937 Re: Docker Image - wrong version Hello Morgan Rhodes, we some issues. We run our Puppetserver + PuppetDB in k8s. One time, because of an outage, we had to start the old VM,s which still exist. I migrated the pgsqI database back an tried to start the PuppetDB and got the following error: java.lang.IllegalStateException: Your PuppetDB database contains a schema migration numbered 70, but this version of PuppetDB does not recognize that version. So I installed also the snapshot and it was working, but I think, this should not happen. So in my opinion, if you tag a Docker image with a specific software version, it should contain that version and nothing else. For snapshots we should use something like: puppet/puppetserver:6-snapshot-latest -> puppet/puppetserver:6.5.1.SNAPSHOT.2019.08.01T1736 Also I remember there was an issue with r10k too (RK-342). BR Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
