Jira (PUP-7808) puppet resource <...> --to_yaml mishandles structured resource values
Title: Message Title Josh Cooper commented on PUP-7808 Re: puppet resource <...> --to_yaml mishandles structured resource values Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/0cfcb63c4599ee50e1a664c850e46d281f2bf68d 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.203387.1501606043000.98755.1568426820799%40Atlassian.JIRA.
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-2487 Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Change By: Jarret Lavallee CS Priority: Normal Needs Priority 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.119255.1456852336000.98617.1568416261131%40Atlassian.JIRA.
Jira (PDB-4373) PDB has issues upgrading to versions later than 6.1 on centos6
Title: Message Title Joshua Partlow commented on PDB-4373 Re: PDB has issues upgrading to versions later than 6.1 on centos6 Thanks! 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.309068.155804266.98566.1568415120373%40Atlassian.JIRA.
Jira (PDB-4373) PDB has issues upgrading to versions later than 6.1 on centos6
Title: Message Title Austin Blatt commented on PDB-4373 Re: PDB has issues upgrading to versions later than 6.1 on centos6 Joshua Partlow This has now been promoted into Lovejoy as of 2019.2.0-rc8-263-gbaa6ea2 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.309068.155804266.98512.1568412660654%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is overridden by http_proxy environment variable
Title: Message Title Jean Bond updated an issue Puppet / PUP-9990 no_proxy config setting is overridden by http_proxy environment variable Change By: Jean Bond Labels: proxy resolved-issue-added 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.322755.1567086003000.98460.1568411160467%40Atlassian.JIRA.
Jira (PUP-9991) `puppet module uninstall` does not work on FIPS
Title: Message Title Jean Bond updated an issue Puppet / PUP-9991 `puppet module uninstall` does not work on FIPS Change By: Jean Bond Labels: resolved-issue-added 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.323058.1567203304000.98422.1568410623404%40Atlassian.JIRA.
Jira (PUP-7808) puppet resource <...> --to_yaml mishandles structured resource values
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7808 puppet resource <...> --to_yaml mishandles structured resource values Change By: Josh Cooper Fix Version/s: PUP 6.4.z Fix Version/s: PUP 6.10.0 Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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.co
Jira (PUP-7808) puppet resource <...> --to_yaml mishandles structured resource values
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-7808 puppet resource <...> --to_yaml mishandles structured resource values Change By: Josh Cooper Assignee: Josh Cooper 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.203387.1501606043000.98405.1568410502422%40Atlassian.JIRA.
Jira (PUP-7808) puppet resource <...> --to_yaml mishandles structured resource values
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7808 puppet resource <...> --to_yaml mishandles structured resource values Change By: Josh Cooper Sprint: 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.203387.1501606043000.98407.1568410502435%40Atlassian.JIRA.
Jira (PUP-10014) Unvendor deep_merge
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10014 Unvendor deep_merge Change By: Josh Cooper Puppet vendors the deep_merge gem version 1.0.1. Puppet also implements deep_merge logic (https://github.com/puppetlabs/puppet/blob/ ca796215b95825f22b0ea30f56a27af181eda53a 34b208f04f7415f9a99bf6eafd6d101b303b920d /lib/puppet/ parser vendor / scope load_deep_merge .rb# L821-L838 L1 ). And there are other places where we should deeply merging objects.This ticket is to update calls sites to use the deep_merge gem, and unvendor the gem. It will need to be added as a runtime dependency to .gemspec and ext/project_data.yaml. Also add to puppet-runtime as a shared gem (so it's useable by puppet-agent and puppetserver). 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...@googlegr
Jira (PDB-4455) Add support for syncing catalog inputs
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4455 Add support for syncing catalog inputs Change By: Austin Blatt 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.317965.1563991774000.98361.1568409480832%40Atlassian.JIRA.
Jira (PDB-4455) Add support for syncing catalog inputs
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4455 Add support for syncing catalog inputs Change By: Austin Blatt Fix Version/s: PDB 6.6.0 Fix Version/s: PDB 6.7.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.317965.1563991774000.98356.1568409480800%40Atlassian.JIRA.
Jira (PDB-4455) Add support for syncing catalog inputs
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4455 Add support for syncing catalog inputs Change By: Austin Blatt Fix Version/s: PDB 6.6.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.317965.1563991774000.98351.1568409480749%40Atlassian.JIRA.
Jira (PUP-10018) The module tool won't solve some dependencies without --force or --ignore-dependencies
Title: Message Title
John Bollinger updated an issue
Puppet / PUP-10018
The module tool won't solve some dependencies without --force or --ignore-dependencies
Change By:
John Bollinger
*Puppet Version: 6.8.1* *Puppet Server Version: 6.5.0* *OS Name/Version: Red Hat Enterprise Linux Server 7.4*The module tool refuses to perform valid module upgrades under some circumstances, unless the {{\-\-force}} or {{\-\-ignore\-dependencies}} option is applied. Even {{\-\-ignore\-dependencies}} does not suffice in some cases. Specifically, it seems unwilling to perform an upgrade across a major version of the specified module if that requires an upgrade even of the minor version of one of that module's dependencies. Alternatively, the tool's objection might be to performing a set of upgrades that are valid as a group, but which cannot be broken down into a sequence of separate, individually-valid upgrades.The particular case in which I experienced this can be reproduced like so: # Start with a clean install of Puppet 6.8.1 and puppetserver 6.5.0 (I used the Puppet, Inc. RPMs, installed via yum). # Install version 6.3.0 of puppetlabs-apt via the module tool # Install version 2.1.2 of puppetlabs-puppet_agent via the module tool # Attempt to upgrade puppetlabs-puppet_agent to version 2.2.0 via the module tool (fails on unresolvable dependencies) # Attempt to upgrade puppetlabs-apt to version 7.1.0 via the module tool (fails on unresolvable dependencies)One should not need to use {{\-\-force}} or {{\-\-ignore\-dependencies}} to upgrade from one set of module versions in which all dependencies are satisfied to another set of module versions in which all dependencies are satisfied.*Desired Behavior:*The module tool should be willing to perform upgrades such as those described without using {{\-\-force}} or {{\-\-ignore\-dependencies}}. In particular, it should be willing to perform any combination of minor-version upgrades in service to an upgrade of the module named on the command line, so long as it results in a final state in which all dependencies are satisfied. Use of {{\-\-force}} or {{\-\-ignore\-dependencies}} is not desirable here because it does not automatically solve dependencies, and it can (and often does) produce a situation in which dependencies indeed are not fully satisfied.It would be acceptable, albeit not ideal for this purpose, to require use of a new, different command-line argument.*Actual Behavior:*Here's an example of the observed behavior. Specific module versions are expressed via {{\-\-version}} options to ensure reproducibility. The target versions for the upgrade commands reflect the latest versions of the modules involved as of the time of this report, and at this time, the upgrade failures can also be reproduced without specifying target module versions._*Preparing the environment ...*_{{# puppet module list}} {{/etc/puppetlabs/code/environments/production/modules (no modules installed)}} {{/etc/puppetlabs/code/modules (no modules installed)}} {{/opt/puppetlabs/puppet/m
Jira (PUP-10018) The module tool won't solve some dependencies without --force or --ignore-dependencies
Title: Message Title
John Bollinger updated an issue
Puppet / PUP-10018
The module tool won't solve some dependencies without --force or --ignore-dependencies
Change By:
John Bollinger
*Puppet Version: 6.8.1* *Puppet Server Version: 6.5.0* *OS Name/Version: Red Hat Enterprise Linux Server 7.4*The module tool refuses to perform valid module upgrades under some circumstances, unless the {{\-\-force}} or {{\-\-ignore\-dependencies}} option is applied. Even {{\-\-ignore\-dependencies}} does not suffice in some cases. Specifically, it seems unwilling to perform an upgrade across a major version of the specified module if that requires an upgrade even of the minor version of one of that module's dependencies. Alternatively, the tool's objection might be to performing a set of upgrades that are valid as a group, but which cannot be broken down into a sequence of separate, individually-valid upgrades.The particular case in which I experienced this can be reproduced like so: # Start with a clean install of Puppet 6.8.1 and puppetserver 6.5.0 (I used the Puppet, Inc . RPMs, installed via yum). # Install version 6.3.0 of puppetlabs-apt via the module tool # Install version 2.1.2 of puppetlabs-puppet_agent via the module tool # Attempt to upgrade puppetlabs-puppet_agent to version 2.2.0 via the module tool (fails on unresolvable dependencies) # Attempt to upgrade puppetlabs-apt to version 7.1.0 via the module tool (fails on unresolvable dependencies)One should not need to use {{\-\-force}} or {{\-\-ignore\-dependencies}} to upgrade from one set of module versions in which all dependencies are satisfied to another set of module versions in which all dependencies are satisfied.*Desired Behavior:*The module tool should be willing to perform upgrades such as those described without using {{\-\-force}} or {{\-\-ignore\-dependencies}}. In particular, it should be willing to perform any combination of minor-version upgrades in service to an upgrade of the module named on the command line, so long as it results in a final state in which all dependencies are satisfied. Use of {{\-\-force}} or {{\-\-ignore\-dependencies}} is not desirable here because it does not automatically solve dependencies, and it can (and often does) produce a situation in which dependencies indeed are not fully satisfied.It would be acceptable, albeit not ideal for this purpose, to require use of a new, different command-line argument.*Actual Behavior:*Here's an example of the observed behavior. Specific module versions are expressed via {{\-\-version}} options to ensure reproducibility. The target versions for the upgrade commands reflect the latest versions of the modules involved as of the time of this report, and at this time, the upgrade failures can be reproduced without specifying target module versions._*Preparing the environment ...*_{{# puppet module list}} {{/etc/puppetlabs/code/environments/production/modules (no modules installed)}} {{/etc/puppetlabs/code/modules (no modules installed)}} {{/opt/puppetlabs/puppet/modu
Jira (PUP-10018) The module tool won't solve some dependencies without --force or --ignore-dependencies
Title: Message Title
John Bollinger updated an issue
Puppet / PUP-10018
The module tool won't solve some dependencies without --force or --ignore-dependencies
Change By:
John Bollinger
*Puppet Version: 6.8.1* *Puppet Server Version: 6.5.0* *OS Name/Version: Red Hat Enterprise Linux Server 7.4*The module tool refuses to perform valid module upgrades under some circumstances, unless the {{\-\-force}} or {{\-\-ignore\-dependencies}} option is applied. Even {{\-\-ignore\-dependencies}} does not suffice in some cases. Specifically, it seems unwilling to perform an upgrade across a major version of the specified module if that requires an upgrade even of the minor version of one of that module's dependencies. Alternatively, the tool's objection might be to performing a set of upgrades that are valid as a group, but which cannot be broken down into a sequence of separate, individually-valid upgrades.The particular case in which I experienced this can be reproduced like so: # Start with a clean install of Puppet and puppetserver version 6.8.1 and puppetserver 6 . 5.0. # Install version 6.3.0 of puppetlabs-apt via the module tool # Install version 2.1.2 of puppetlabs-puppet_agent via the module tool # Attempt to upgrade puppetlabs-puppet_agent to version 2.2.0 via the module tool (fails on unresolvable dependencies) # Attempt to upgrade puppetlabs-apt to version 7.1.0 via the module tool (fails on unresolvable dependencies)One should not need to use {{\-\-force}} or {{\-\-ignore\-dependencies}} to upgrade from one set of module versions in which all dependencies are satisfied to another set of module versions in which all dependencies are satisfied.*Desired Behavior:*The module tool should be willing to perform upgrades such as those described without using {{\-\-force}} or {{\-\-ignore\-dependencies}}. In particular, it should be willing to perform any combination of minor-version upgrades in service to an upgrade of the module named on the command line, so long as it results in a final state in which all dependencies are satisfied. Use of {{\-\-force}} or {{\-\-ignore\-dependencies}} is not desirable here because it does not automatically solve dependencies, and it can (and often does) produce a situation in which dependencies indeed are not fully satisfied.It would be acceptable, albeit not ideal for this purpose, to require use of a new, different command-line argument.*Actual Behavior:*Here's an example of the observed behavior. Specific module versions are expressed via {{\-\-version}} options to ensure reproducibility. The target versions for the upgrade commands reflect the latest versions of the modules involved as of the time of this report, and at this time, the upgrade failures can be reproduced without specifying target module versions._*Preparing the environment ...*_{{# puppet module list}} {{/etc/puppetlabs/code/environments/production/modules (no modules installed)}} {{/etc/puppetlabs/code/modules (no modules installed)}} {{/opt/puppetlabs/puppet/modules (no modules install
Jira (PUP-10018) The module tool won't solve some dependencies without --force or --ignore-dependencies
Title: Message Title
John Bollinger updated an issue
Puppet / PUP-10018
The module tool won't solve some dependencies without --force or --ignore-dependencies
Change By:
John Bollinger
*Puppet Version: 6.8.1* *Puppet Server Version: 6. 8 5 . 1 0 * *OS Name/Version: Red Hat Enterprise Linux Server 7.4*The module tool refuses to perform valid module upgrades under some circumstances, unless the {{\-\-force}} or {{\-\-ignore\-dependencies}} option is applied. Even {{\-\-ignore\-dependencies}} does not suffice in some cases. Specifically, it seems unwilling to perform an upgrade across a major version of the specified module if that requires an upgrade even of the minor version of one of that module's dependencies. Alternatively, the tool's objection might be to performing a set of upgrades that are valid as a group, but which cannot be broken down into a sequence of separate, individually-valid upgrades.The particular case in which I experienced this can be reproduced like so: # Start with a clean install of Puppet and puppetserver version 6.8.1. # Install version 6.3.0 of puppetlabs-apt via the module tool # Install version 2.1.2 of puppetlabs-puppet_agent via the module tool # Attempt to upgrade puppetlabs-puppet_agent to version 2.2.0 via the module tool (fails on unresolvable dependencies) # Attempt to upgrade puppetlabs-apt to version 7.1.0 via the module tool (fails on unresolvable dependencies)One should not need to use {{\-\-force}} or {{\-\-ignore\-dependencies}} to upgrade from one set of module versions in which all dependencies are satisfied to another set of module versions in which all dependencies are satisfied.*Desired Behavior:*The module tool should be willing to perform upgrades such as those described without using {{\-\-force}} or {{\-\-ignore\-dependencies}}. In particular, it should be willing to perform any combination of minor-version upgrades in service to an upgrade of the module named on the command line, so long as it results in a final state in which all dependencies are satisfied. Use of {{\-\-force}} or {{\-\-ignore\-dependencies}} is not desirable here because it does not automatically solve dependencies, and it can (and often does) produce a situation in which dependencies indeed are not fully satisfied.It would be acceptable, albeit not ideal for this purpose, to require use of a new, different command-line argument.*Actual Behavior:*Here's an example of the observed behavior. Specific module versions are expressed via {{\-\-version}} options to ensure reproducibility. The target versions for the upgrade commands reflect the latest versions of the modules involved as of the time of this report, and at this time, the upgrade failures can be reproduced without specifying target module versions._*Preparing the environment ...*_{{# puppet module list}} {{/etc/puppetlabs/code/environments/production/modules (no modules installed)}} {{/etc/puppetlabs/code/modules (no modules installed)}} {{/opt/puppetlabs/puppet/modules (no modules installed)}}{{# puppet modul
Jira (FACT-1919) blank/negative facter cache due to timed out EC2 metadata
Title: Message Title Jean Bond updated an issue Facter / FACT-1919 blank/negative facter cache due to timed out EC2 metadata Change By: Jean Bond Labels: resolved-issue-added 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.307267.1556898834000.98179.1568402880486%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Jean Bond updated an issue Puppet / PUP-10016 Systemd provider is not correctly selected as the service provider if puppet is run as non root Change By: Jean Bond Labels: resolved-issue-added 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.324178.1568121391000.98181.1568402880494%40Atlassian.JIRA.
Jira (PDB-4491) Add/update CODEOWNERS in a few repos
Title: Message Title Molly Waggett commented on PDB-4491 Re: Add/update CODEOWNERS in a few repos Friendly reminder on this! We will archive your repos on Monday, Sept 23 if this isn't done! 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.322396.1566932988000.98115.1568401860221%40Atlassian.JIRA.
Jira (PUP-10019) file resource checks source even if the file exists and replace is false
Title: Message Title
Thomas Kishel created an issue
Puppet / PUP-10019
file resource checks source even if the file exists and replace is false
Issue Type:
Bug
Affects Versions:
PUP 6.4.3
Assignee:
Unassigned
Created:
2019/09/13 11:42 AM
Priority:
Minor
Reporter:
Thomas Kishel
Puppet Version: 6.4.3 and presumably others Puppet Server Version: NA OS Name/Version: NA Desired Behavior: Skip the use of source if the file exists and replace is false. Actual Behavior:
[root@pe-201911-master-ha ~]# cat a.pp
file { '/tmp/test.txt':
ensure => present,
replace => false,
source => "/tmp/source.txt",
Jira (PUP-9792) Merge of lookup_options not working
Title: Message Title Henrik Lindberg commented on PUP-9792 Re: Merge of lookup_options not working In order to use top scope variables in your hiera.yaml and get the correct answer from puppet lookup CLI, you must use the --evaluate option. 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.313541.1561115342000.97883.1568396640212%40Atlassian.JIRA.
Jira (PUP-6022) Typing local variables does not work - results in Error: This Type-Name has no effect
Title: Message Title Henrik Lindberg commented on PUP-6022 Re: Typing local variables does not work - results in Error: This Type-Name has no effect @john Not quite - typing variables have never been supported - parameters can be typed though (as explained above). 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.120438.145747609.97859.1568396520530%40Atlassian.JIRA.
Jira (PDB-4455) Add support for syncing catalog inputs
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4455 Add support for syncing catalog inputs Change By: Zachary Kent Fix Version/s: PDB n/a 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.317965.1563991774000.97832.1568396160644%40Atlassian.JIRA.
Jira (PDB-4480) Create the catalog-inputs query endpoint
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4480 Create the catalog-inputs query endpoint Change By: Zachary Kent Fix Version/s: PDB 6.6.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.320756.1565732125000.97823.1568396100767%40Atlassian.JIRA.
Jira (PDB-4455) Add support for syncing catalog inputs
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4455 Add support for syncing catalog inputs Change By: Zachary Kent Fix Version/s: PDB n/a 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.317965.1563991774000.97829.1568396100797%40Atlassian.JIRA.
Jira (PDB-4373) PDB has issues upgrading to versions later than 6.1 on centos6
Title: Message Title Austin Blatt commented on PDB-4373 Re: PDB has issues upgrading to versions later than 6.1 on centos6 The clojure projects are still blocked on jar-jar failures, so nothing as of yet. It will be up before the Platform release goes out, as this is also what's holding up the Platform release. 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.309068.155804266.97813.1568395860488%40Atlassian.JIRA.
Jira (PDB-4373) PDB has issues upgrading to versions later than 6.1 on centos6
Title: Message Title Joshua Partlow commented on PDB-4373 Re: PDB has issues upgrading to versions later than 6.1 on centos6 Hi Austin, do you know what build of pdb this would be in now? 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.309068.155804266.97796.1568395320402%40Atlassian.JIRA.
Jira (PDB-4373) PDB has issues upgrading to versions later than 6.1 on centos6
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4373 PDB has issues upgrading to versions later than 6.1 on centos6 Change By: Austin Blatt 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.309068.155804266.97702.1568394663190%40Atlassian.JIRA.
Jira (PDB-2634) PQL & Hashes: Provide hash projection capability for facts & resource params
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-2634 PQL & Hashes: Provide hash projection capability for facts & resource params Change By: Austin Blatt Fix Version/s: PDB 6.6.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.127261.1461089739000.97730.1568394663319%40Atlassian.JIRA.
Jira (PDB-2634) PQL & Hashes: Provide hash projection capability for facts & resource params
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-2634 PQL & Hashes: Provide hash projection capability for facts & resource params Change By: Austin Blatt Fix Version/s: PDB 6.7.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.127261.1461089739000.97759.1568394663450%40Atlassian.JIRA.
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Thomas Kishel commented on PUP-10017 Re: Collapse dependency failures into Class level failures A (let's say) suppress_inherited_dependency_failures option would affect the logic here: https://github.com/puppetlabs/puppet/blob/5.5.x/lib/puppet/transaction.rb#L285 https://github.com/puppetlabs/puppet/blob/5.5.x/lib/puppet/transaction.rb#L398 When suppress_inherited_dependency_failures is true ... if a resource has a parent if the parent is a class if the class has a dependency relationship if the dependent is a failed resource (or the dependent is a class containing a failed resource) mark the class as failed (and mark the resource as failed) report (just once) that we are skipping the containing class of the resource suppress the report that we are skipping the resource Use case when enabled: given a failure in a resource that is required by a class, a user would see (one) class failure in the report, and could perform a puppet run without suppress_inherited_dependency_failures to identify the resources in the class that were skipped, if necessary. But since the solution to the dependency failure is to resolve the failure in the dependent resource, that would only be valuable for auditing everything that was skipped: the user's attention should be focused on the failed resource (in the example, File['/impossible/xxx.txt']).
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Thomas Kishel commented on PUP-10017 Re: Collapse dependency failures into Class level failures Implementing this should also address the high volume of skips associated with resources using the schedule metaparameter when the run is outside the schedule window. 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.324379.1568220393000.97613.1568392800169%40Atlassian.JIRA.
Jira (PUP-10018) The module tool won't solve some dependencies without --force or --ignore-dependencies
Title: Message Title
John Bollinger updated an issue
Puppet / PUP-10018
The module tool won't solve some dependencies without --force or --ignore-dependencies
Change By:
John Bollinger
*Puppet Version: 6.8.1* *Puppet Server Version: 6.8.1* *OS Name/Version: Red Hat Enterprise Linux Server 7.4*The module tool refuses to perform valid module upgrades under some circumstances, unless the {{ \ - \ -force}} or {{ \ - \ -ignore \ -dependencies}} option is applied. Even {{ \ - \ -ignore \ -dependencies}} does not suffice in some cases. Specifically, it seems unwilling to perform an upgrade across a major version of the specified module if that requires an upgrade even of the minor version of one of that module's dependencies. Alternatively, the tool's objection might be to performing a set of upgrades that are valid as a group, but which cannot be broken down into a sequence of separate, individually-valid upgrades.The particular case in which I experienced this can be reproduced like so: # Start with a clean install of Puppet and puppetserver version 6.8.1. # Install version 6.3.0 of puppetlabs-apt via the module tool # Install version 2.1.2 of puppetlabs-puppet_agent via the module tool # Attempt to upgrade puppetlabs-puppet_agent to version 2.2.0 via the module tool (fails on unresolvable dependencies) # Attempt to upgrade puppetlabs-apt to version 7.1.0 via the module tool (fails on unresolvable dependencies)One should not need to use {{ \ - \ -force}} or {{ \ - \ -ignore \ -dependencies}} to upgrade from one set of module versions in which all dependencies are satisfied to another set of module versions in which all dependencies are satisfied.*Desired Behavior:*The module tool should be willing to perform upgrades such as those described without using {{ \ - \ -force}} or {{ \ - \ -ignore \ -dependencies}}. In particular, it should be willing to perform any combination of minor-version upgrades in service to an upgrade of the module named on the command line, so long as it results in a final state in which all dependencies are satisfied. Use of {{ \ - \ -force}} or {{ \ - \ -ignore \ -dependencies}} is not desirable here because it does not automatically solve dependencies, and it can (and often does) produce a situation in which dependencies indeed are not fully satisfied.It would be acceptable, albeit not ideal for this purpose, to require use of a new, different command-line argument.*Actual Behavior:*Here's an example of the observed behavior. Specific module versions are expressed via {{ \ - \ -version}} options to ensure reproducibility. The target versions for the upgrade commands reflect the latest versions of the modules involved as of the time of this report, and at this time, the upgrade failures can be reproduced without specifying target module versions._*Preparing the environment ...*_{{# puppet module list}} {{/etc/puppetlabs/code/environments/production/modules (no modules installed)}} {{/etc/puppetlabs/code/modules (no modules installed)}} {{/opt/puppetlabs/puppet/module
Jira (PUP-10018) The module tool won't solve some dependencies without --force or --ignore-dependencies
Title: Message Title John Bollinger created an issue Puppet / PUP-10018 The module tool won't solve some dependencies without --force or --ignore-dependencies Issue Type: Bug Affects Versions: PUP 6.8.1 Assignee: Unassigned Components: PMT Created: 2019/09/13 9:16 AM Priority: Normal Reporter: John Bollinger Puppet Version: 6.8.1 Puppet Server Version: 6.8.1 OS Name/Version: Red Hat Enterprise Linux Server 7.4 The module tool refuses to perform valid module upgrades under some circumstances, unless the -force or ignore-dependencies option is applied. Even -ignore-dependencies does not suffice in some cases. Specifically, it seems unwilling to perform an upgrade across a major version of the specified module if that requires an upgrade even of the minor version of one of that module's dependencies. Alternatively, the tool's objection might be to performing a set of upgrades that are valid as a group, but which cannot be broken down into a sequence of separate, individually-valid upgrades. The particular case in which I experienced this can be reproduced like so: Start with a clean install of Puppet and puppetserver version 6.8.1. Install version 6.3.0 of puppetlabs-apt via the module tool Install version 2.1.2 of puppetlabs-puppet_agent via the module tool Attempt to upgrade puppetlabs-puppet_agent to version 2.2.0 via the module tool (fails on unresolvable dependencies) Attempt to upgrade puppetlabs-apt to v
Jira (PDB-4503) (docs) documentation for puppetdb_query function
Title: Message Title Heston Hoffman updated an issue PuppetDB / PDB-4503 (docs) documentation for puppetdb_query function Change By: Heston Hoffman Labels: docs-pdb feedback-form-docs-site 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.324581.1568320726000.97379.1568390880390%40Atlassian.JIRA.
Jira (PUP-2887) IPv6 failover using srv records doesn't work as expected
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2887 IPv6 failover using srv records doesn't work as expected Change By: Josh Cooper Sprint: Coremunity Hopper 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.41163.140440062.97355.1568390520271%40Atlassian.JIRA.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9480 puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Change By: Josh Cooper Component/s: 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.295251.154953565.97348.1568390400635%40Atlassian.JIRA.
Jira (PUP-2887) IPv6 failover using srv records doesn't work as expected
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2887 IPv6 failover using srv records doesn't work as expected Change By: Josh Cooper Component/s: 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.41163.140440062.97336.1568390340430%40Atlassian.JIRA.
Jira (PUP-10013) Update minitar version and call new fsync=false option
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10013 Update minitar version and call new fsync=false option Change By: Josh Cooper Sprint: Coremunity Grooming 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.323877.1567788493000.97266.1568389440185%40Atlassian.JIRA.
Jira (PUP-10013) Update minitar version and call new fsync=false option
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10013 Update minitar version and call new fsync=false option Change By: Josh Cooper Fix Version/s: PUP 5.5.z 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.323877.1567788493000.97263.1568389380633%40Atlassian.JIRA.
Jira (FACT-1996) Invalidate resolver cache once Facter run in over
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-1996 Invalidate resolver cache once Facter run in over Change By: Bogdan Irimie Assignee: Bogdan Irimie 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.321897.156645883.97184.1568387040078%40Atlassian.JIRA.
Jira (FACT-2021) Fix rake task for generating fact
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2021 Fix rake task for generating fact Change By: Bogdan Irimie Assignee: Bogdan Irimie 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.324654.1568385206000.97169.1568385240302%40Atlassian.JIRA.
Jira (FACT-2021) Fix rake task for generating fact
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2021 Fix rake task for generating fact Issue Type: Bug Assignee: Unassigned Created: 2019/09/13 7:33 AM Priority: Normal Reporter: Bogdan Irimie 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.324654.1568385206000.97
Jira (FACT-2019) puppet agent -t --debug resolves fact, without --debug it doesn't
Title: Message Title Athanasios Douitsis commented on FACT-2019 Re: puppet agent -t --debug resolves fact, without --debug it doesn't Okay, I think I found the bug. https://github.com/puppetlabs/leatherman/pull/305 Using the debug flag was slightly altering the process timing, so the signal was not arriving in time to wreak havoc. Without the debug flag, it was able to cause mischief in a more consistent way. 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.324466.1568292552000.97125.1568381040083%40Atlassian.JIRA.
Jira (FACT-2020) Fix gem interface
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2020 Fix gem interface Change By: Bogdan Irimie Assignee: Bogdan Irimie 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.324645.1568375125000.97075.1568375160299%40Atlassian.JIRA.
Jira (FACT-2020) Fix gem interface
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2020 Fix gem interface Issue Type: Bug Assignee: Unassigned Created: 2019/09/13 4:45 AM Priority: Normal Reporter: Bogdan Irimie to_hash should return a hash with the results value should return the value of the specified fact Add Comment This message was sent by Atlassian JIRA (v7.7.1#
Jira (FACT-2019) puppet agent -t --debug resolves fact, without --debug it doesn't
Title: Message Title
Athanasios Douitsis commented on FACT-2019
Re: puppet agent -t --debug resolves fact, without --debug it doesn't
...and, running on the client the command facter os yields: {{{}} {{ architecture => "amd64",}} {{ family => "FreeBSD",}} {{ hardware => "amd64",}} {{ name => "FreeBSD"}} } and the release key is missing. But if I run facter os --debug yields: {{{}} architecture => "amd64", family => "FreeBSD", hardware => "amd64", name => "FreeBSD", {{ release => {}} full => "11.2-RELEASE-p14", major => "11", minor => "2-RELEASE-p14" {{ }}} } I checked with dwatch and both cases (with debug and without) execute the same /bin/freebsd-version command. So, in a nutshell, without the debug flag the release nested key is somehow lost. This is evidently a bug in facter.
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.324466.1568292552000.97052.1568374020406%40Atlassian.JIRA.
Jira (PUP-6022) Typing local variables does not work - results in Error: This Type-Name has no effect
Title: Message Title john commented on PUP-6022 Re: Typing local variables does not work - results in Error: This Type-Name has no effect I came across this issue while investigating a different problem and just wanted to clarify. first, thanks Henrik Lindberg for the great explanation however i believe the following needs clarifying Puppet 4.x does not support typing variables. Type aliases where introduced in puppet 4.4 so i think this should read "Puppet < 4.4.0 does not support typing variables. 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.120438.145747609.97046.1568372220165%40Atlassian.JIRA.
Jira (FACT-1992) autofs mountpoints being mounted by facter
Title: Message Title Gabriel Nagy updated an issue Facter / FACT-1992 autofs mountpoints being mounted by facter Change By: Gabriel Nagy Fix Version/s: FACT 3.13.z Fix Version/s: FACT 3.11.z 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.321294.156596424.97037.1568371860148%40Atlassian.JIRA.
Jira (FACT-1992) autofs mountpoints being mounted by facter
Title: Message Title
Gabriel Nagy updated an issue
Facter / FACT-1992
autofs mountpoints being mounted by facter
Change By:
Gabriel Nagy
Release Notes Summary:
When Facter stats a mountpoint to get the size and available space, it causes mountpoints of type {{autofs}} to be automatically mounted, which is not the intended behavior.Automounts are now skipped by Facter when resolving mountpoints.
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.321294.156596424.97032.1568371682309%40Atlassian.JIRA.
Jira (FACT-2019) puppet agent -t --debug resolves fact, without --debug it doesn't
Title: Message Title
Athanasios Douitsis commented on FACT-2019
Re: puppet agent -t --debug resolves fact, without --debug it doesn't
Just to clarify, using the debug flag on the client side, I get: Debug: Facter: fact "os" has resolved to { architecture => "amd64", family => "FreeBSD", hardware => "amd64", name => "FreeBSD", release => { full => "11.2-RELEASE-p14", major => "11", minor => "2-RELEASE-p14" {{ }}} }. Which means the fact works correctly with regards to getting the info out of the operating system. Furthermore, other nodes which use older puppet versions such as 4, work correctly. Since the debug flag at the client alters the behaviour, I'd say this is a bug not of the puppetmaster but of the client. Furthermore, I've been playing with some notice messages on the side of the puppetmaster to understand what's being transmitted by the buggy client to the master. Here's what comes across without the debug flag: os is a Struct[\{'architecture' => String, 'family' => String, 'hardware' => String, 'name' => String}] and here is what comes across with the debug flag: {{os is a Struct[{'architecture' => String, 'family' => String, 'hardware' => String, 'name' => String, 'release' => Struct[ {'full' => String, 'major' => String, 'minor' => String} ]}]}} So as you can see, when running without the debug flag, the nested Struct (the release key) gets swallowed somewhere along the way.
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 re
Jira (FACT-2003) Create fact formatter that supports multiple formats
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2003 Create fact formatter that supports multiple formats Change By: Bogdan Irimie 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.322748.1567078267000.96946.1568362320086%40Atlassian.JIRA.
