Jira (PUP-1153) Incorrect ordering of group and user resource purging
Title: Message Title
Josh Cooper commented on PUP-1153
Re: Incorrect ordering of group and user resource purging
Jesse Hathaway if you manage all users including system users and groups, then I would expect the following to just work:
user { 'root':
ensure => present,
password => ...,
require => Group['wheel'],
}
# other users here
group { 'wheel':
ensure =>present,
}
# other groups here
Jira (BOLT-1360) Evaluate including upgrades for bolt gem dependencies in bolt packages
Title: Message Title Cas Donoghue commented on BOLT-1360 Re: Evaluate including upgrades for bolt gem dependencies in bolt packages Link to the gems that currently could be updated. https://github.com/puppetlabs/puppet-runtime/pull/182#issuecomment-498442969 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311108.1559598816000.32329.1559599380467%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1360) Evaluate including upgrades for bolt gem dependencies in bolt packages
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1360 Evaluate including upgrades for bolt gem dependencies in bolt packages Issue Type: Improvement Assignee: Unassigned Created: 2019/06/03 2:53 PM Priority: Normal Reporter: Cas Donoghue Before the migration of defining bolt-specific gems in bolt-vanagon to puppet-runtime a script was used (with no defined frequency) to parse potential updates to the gem dependencies shipped with bolt. https://github.com/puppetlabs/bolt-vanagon/blob/master/generate.rb We should define some kind of goals or requirements for keeping gems components up to date. As of today I see about 17 gems with newer versions available. Add Comment
Jira (PUP-9564) Puppet upgrades debian packages with pending updates when setting them on hold
Title: Message Title Josh Cooper commented on PUP-9564 Re: Puppet upgrades debian packages with pending updates when setting them on hold Reopening this because CI is failing. Last passing puppet-agent#5.5.x is 775f8210268e6b4d86c4e63819cf1ed9fd3098f7 containing puppet#5d06d0b737, which includes all of the dpkg/held work and acceptance updates. Running the test in isolation fails. I think the test only started failing recently when the new version 1.0.1t-1+deb8u8 was released upstream: $ bundle exec rake ci:test:aio HOSTS=redhat7-64m-debian8-64a TESTS=tests/provider/package/dpkg_ensure_held_package_should_preserve_version.rb RELEASE_STREAM=puppet5 SHA=775f8210268e6b4d86c4e63819cf1ed9fd3098f7 ... Begin tests/provider/package/dpkg_ensure_held_package_should_preserve_version.rb dpkg ensure held package should preserve version if package is allready installed * Ensure held should lock to specific installed version snjlb1kd6994dsa.delivery.puppetlabs.net (snjlb1kd6994dsa.delivery.puppetlabs.net) 14:15:56$ dpkg -s openssl | sed -n -e 's/Version: //p' Warning: Skipping ip method to ssh to host as its value is not set. Refer to https://github.com/puppetlabs/beaker/tree/master/docs/how_to/ssh_connection_preference.md to remove this warning
Jira (PUP-9564) Puppet upgrades debian packages with pending updates when setting them on hold
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9564 Puppet upgrades debian packages with pending updates when setting them on hold Change By: Josh Cooper Fix Version/s: PUP 5.5.15 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300439.1552654564000.32220.1559596740883%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4390) Don't produce duplicate certname entries for certnames with special characters
Title: Message Title
Austin Blatt created an issue
PuppetDB / PDB-4390
Don't produce duplicate certname entries for certnames with special characters
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/06/03 1:29 PM
Priority:
Major
Reporter:
Austin Blatt
Using a certname with special characters, or that is too long, will result in a duplicate node entry. You can reproduce this error with a certname such as node_0 by submitting a factset first and then submitting a catalog. Example commands are below Replace facts
curl -X POST http://localhost:8080/pdb/cmd/v1 \
-H 'Content-Type:application/json' \
-d '{"command": "replace facts", "version": 5, "payload": { "certname": "host_0", "environment": "foo", "producer_timestamp": "2019-06-03T09:17:25-0700", "producer": "foo", "values": {} } }'
Replace catalog
curl -X POST http://localhost:8080/pdb/cmd/v1
Jira (PUP-9724) Use yum as default provider for Amazon platforms
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9724 Use yum as default provider for Amazon platforms Change By: Josh Cooper Fix Version/s: PUP 6.0.10 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310772.1559234728000.31981.1559587920391%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9724) Use yum as default provider for Amazon platforms
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9724
Use yum as default provider for Amazon platforms
Change By:
Josh Cooper
Current Behaviour:- Due to the fact that Amazon platforms do not have a default provider set, puppet will try to assume what to use which result in trying to install packages using the `gem` provider.Desired Behaviour:- Amazon platforms should use `yum` provider This issue was introduced in PUP-9198 when the {{yum}} provider changed from being the default for all redhat osfamilies to only those with OS versions 4-7, as redhat 8 switched to dnf. One unintended consequence was {{yum}} was no longer the default provider for amazon since it's {{osfamily}} is {{redhat}}, but its OS version is {{2017.03}}.
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
Jira (PUP-9724) Use yum as default provider for Amazon platforms
Title: Message Title Josh Cooper commented on PUP-9724 Re: Use yum as default provider for Amazon platforms Merged to 6.0.x in 84d01fd4b1c01dd985e93a855447387f2edc7bac 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310772.1559234728000.31960.1559587500405%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1153) Incorrect ordering of group and user resource purging
Title: Message Title Robert August Vincent II commented on PUP-1153 Re: Incorrect ordering of group and user resource purging Note that the accounts module now adds groups before users, and deletes users before groups. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.21655.1387320781000.31660.1559582581306%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9714) Add support for nested hiera interpolation
Title: Message Title Robert August Vincent II commented on PUP-9714 Re: Add support for nested hiera interpolation There needs to be a docs change, as well. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309648.1558477577000.31637.1559582280632%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9570) Catalog failure on first run due to pluginsync and environment switch
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9570 Catalog failure on first run due to pluginsync and environment switch Change By: Jorie Tappa 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300842.1553021716000.31600.1559580540866%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1341) Support version 4 terraform state files in terraform inventory plugin
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1341 Support version 4 terraform state files in terraform inventory plugin Change By: Cas Donoghue Assignee: Lucy Wyman 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310025.155865782.31579.1559579880235%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4389) Query for deactivated nodes
Title: Message Title
Austin Blatt commented on PDB-4389
Re: Query for deactivated nodes
Hi Maheswaran Shanmugam, you will need to add node_state = "inactive" to your query because deactivated is not null will not work on its own on nodes endpoint because by default the endpoint only includes active nodes. We likely need to improve our docs because it is difficult to find the proper query for deactivated nodes so I've included a few examples here. So the full query for all deactivated and expired nodes, would look like {{nodes[certname] { node_state = "inactive"} }} If you only want the deactivated nodes it'd look like nodes[certname] { node_state = "inactive" and deactivated is not null} Let me know if this fixes your issue.
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310994.155953334.31552.1559579520585%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1920) Facter 3.12 binary gem
Title: Message Title Matthias Baur commented on FACT-1920 Re: Facter 3.12 binary gem Hey Mihai Buzgau, so what's your proposed way to use Facter 3.x in CI pipelines? We can't just compile Facter every time, it takes way too long. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307434.1557141764000.31246.1559563320467%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
