Jira (FACT-198) Rename uniqueid hostid
Title: Message Title Jason Antman assigned an issue to Unassigned I grabbed this one almost four years ago, and unfortunately haven't really touched Facter much since that era. I also can't speak for the requirement anymore, as I've only worked with masterless setups in the past 2-3 years. It's pretty clear that, unfortunately, I'm not going to be tackling this one. Branan Riley or Eric Sorenson would one of you be kind enough to see that this gets assigned/moved appropriately? I dare say it's been so long I don't even know what the proper Jira practices are these days. Facter / FACT-198 Rename uniqueid hostid Change By: Jason Antman Assignee: Jason Antman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1217) yum provider + package groups giving unnecessary errors
Title: Message Title Jason Antman assigned an issue to Unassigned I don't know who should get assignments for Types and Providers these days, if anyone, but this has been assigned to me for almost four years, and I haven't made a commit against puppet itself in about that long. I'm clearly not going to be fixing this one (if it's even still valid). It also no longer affects me. Sorry. Puppet / PUP-1217 yum provider + package groups giving unnecessary errors Change By: Jason Antman Assignee: Jason Antman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-213) Bolt plan help includes --nodes
Title: Message Title Alex Dreyer commented on BOLT-213 Re: Bolt plan help includes --nodes This runs into issues with OptionsParser. We don't know the mode until we parse options and therefore we have to add all options to a single parser. I can a few paths to explore in order of increasing complexity: 1. Modify the parser to remove unexpected options after parsing before printing help 2. Parse mode/action outside the parser and create the parser based on the mode/action 3. Generate help text outside OptionParser 4. Stop using OptionParser all together. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-246) Bolt should ignore editor backup files.
Title: Message Title Alex Dreyer commented on BOLT-246 Re: Bolt should ignore editor backup files. Edwin Wiles I can't replicate the behavior you reported. I get an error when I have a .py~ file. Can you try with the new bolt 0.12.0 release" Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-278) Bolt does not error on conflicting task files
Title: Message Title Alex Dreyer commented on BOLT-278 Re: Bolt does not error on conflicting task files I can't replicate this issue. I get the expected error: Error: Only one file can exists besides the .json file for task bolt_test::repeat in directory /Users/adreyer/src/task-modules/site/bolt_test/tasks on node alex.claveline Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-246) Bolt should ignore editor backup files.
Title: Message Title Edwin Wiles commented on BOLT-246 Re: Bolt should ignore editor backup files. That's definitely better than using the backup file. Many thanks! Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-246) Bolt should ignore editor backup files.
Title: Message Title Alex Dreyer commented on BOLT-246 Re: Bolt should ignore editor backup files. The specified behavior when multiple matching files with different extensions are found is for bolt to error rather than trying to decide which one to run. I've filed BOLT-278 for that Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-278) Bolt does not error on conflicting task files
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-278 Bolt does not error on conflicting task files Issue Type: Bug Assignee: Unassigned Created: 2017/12/27 9:40 AM Priority: Normal Reporter: Alex Dreyer Tasks should error when there are multiple task files matching a task name. This doesn't appear to be happening for emac backup files like init.sh~ Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-277) SSL default makes winrm harder to use
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-277 SSL default makes winrm harder to use Issue Type: Bug Assignee: Unassigned Created: 2017/12/27 9:25 AM Priority: Normal Reporter: Alex Dreyer Inline help still says "winrm://" default is 5985 ... its not anymore and is now 5986, so that should probably change accordingly The --insecure help note is not super helpful for Windows people - its necessary to switch to port 5985 when doing something like --node winrm://foo:b...@host.com ... but you'd never know that The error message without --insecure specified doesn't point users in the right direction - it just says basically "Connection Refused" on port 5986, which Windows users won't know what to do with IMHO Add Comment
Jira (PUP-8258) Cached catalogs settings are ignored if noop is set to true
Title: Message Title Matt Gartman commented on PUP-8258 Re: Cached catalogs settings are ignored if noop is set to true This is pretty critical to the workflow we are planning so that we can both control release of new code over an extended period of time but also address any configuration drift against the the existing code base while also keeping reports clean. Any thoughts on how quickly we can expect a resolution Eric Sorenson or at least some guesstimate on if this is weeks/months/quarters away? Thanks! Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Alex Dreyer Sprint: Bolt One Point Oh Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-213) Bolt plan help includes --nodes
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-213 Bolt plan help includes --nodes Change By: Alex Dreyer Sprint: Bolt One Point Oh Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-126) Support WinRM with Kerberos
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-126 Support WinRM with Kerberos Change By: Alex Dreyer Sprint: Bolt Adoption Blockers Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-264) Allow run-as configuration option for ssh transport
Title: Message Title Lucy Wyman assigned an issue to Unassigned Puppet Task Runner / BOLT-264 Allow run-as configuration option for ssh transport Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8296) puppet(foreman)server which cannot communicate with agent (vice-versa)
Title: Message Title marde meucheul updated an issue Puppet / PUP-8296 puppet(foreman)server which cannot communicate with agent (vice-versa) Change By: marde meucheul Priority: Normal Critical Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8296) puppet(foreman)server which cannot communicate with agent (vice-versa)
Title: Message Title
marde meucheul updated an issue
Puppet / PUP-8296
puppet(foreman)server which cannot communicate with agent (vice-versa)
Change By:
marde meucheul
Summary:
{brief summary of issue} puppet(foreman)server which cannot communicate with agent (vice-versa)
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8296) {brief summary of issue}
Title: Message Title
marde meucheul created an issue
Puppet / PUP-8296
{brief summary of issue}
Issue Type:
Bug
Affects Versions:
PUP 5.3.1, PUP 4.10.8
Assignee:
Unassigned
Created:
2017/12/27 3:51 AM
Environment:
a puppet server (foreman based) a node with an agent configured which cannot connect with the server for a mystic reason
Priority:
Normal
Reporter:
marde meucheul
hi People! I cannot integrate an agent to the server. This is mandatory to send reports from this agent. please help!
from the puppet(foreman)server angle : ```bash [root@foreman ludovic_palamede]# puppet cert generate slavepoc2.edc.carrefour.com -d Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Applying settings catalog for sections main, ssl, ca Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Evicting cache entry for environment 'production' Debug: Caching
Jira (PDB-3801) PuppetDB migration stuck (31) fact_values.
Title: Message Title Steve Traylen created an issue PuppetDB / PDB-3801 PuppetDB migration stuck (31) fact_values. Issue Type: Bug Affects Versions: PDB 4.4.0 Assignee: Unassigned Components: PuppetDB Created: 2017/12/27 1:17 AM Environment: Upgrade puppetdb 2.3.8 -> 4.4.0 CentOS 7 Postgres 9.6.2 35.7 K hosts. Priority: Normal Reporter: Steve Traylen Trying to test the schema update on a dump of current 2.3.8 puppetdb database. The migration appears to get stuck during 31. 2017-12-26 17:05:16,725 INFO [c.z.h.HikariDataSource] PDBWritePool - is starting.
