Jira (PUP-9334) puppet agent apllies catalog successfully but daemon fails
Title: Message Title jagadish honnappa updated an issue Puppet / PUP-9334 puppet agent apllies catalog successfully but daemon fails Change By: jagadish honnappa *Puppet Version:puppet-server-3.8.7-1* *Puppet Server Version:puppet-server-3.8.7-1* *OS Name/Version:all RHEL*when we run "puppet agent -t" it applies catalog without any error/issue.whereas when daemon runs it fails with below errorNov 28 10:38:04 servername puppet-agent[2478]: Error connecting to puppet.master.servername:8140: Inappropriate ioctl for device - getaddrinfo Nov 28 10:38:04 servername puppet-agent[2478]: Unable to fetch my node definition, but the agent run will continue: Nov 28 10:38:04 servername puppet-agent[2478]: getaddrinfo: Name or service not known Nov 28 10:38:04 servername puppet-agent[2478]: (/File[/var/lib/puppet/facts.d]) Failed to generate additional resources using 'eval_generate': getaddrinfo: Name or service not known we use srv_domain we can see below error on all affected serverspuppet: /usr/share/ruby/net/http.rb:878: [BUG] rb_sys_fail(getaddrinfo) - errno == 0 tried to put server name instead of srv_domain... still same issue *Desired Behavior:**should run successfully even when daemon runs[puppet]* Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title Glenn Sarti commented on BOLT-459 Re: Reboot a target and wait for it to become available. Michael Smith Lucy Wyman Alex Dreyer Is this ticket resolved? 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3204) Find LDAP users and groups created mid-transaction.
Title: Message Title Jacob Henner commented on PUP-3204 Re: Find LDAP users and groups created mid-transaction. This is affecting my organization as well. Centrify authentication is enabled by the same run that attempts to set the permissions on several file resources, and extracts archives using the archive module with user/group specified. In both cases, the process will fail until the next run. We worked around the issue with a combination of chown execs and custom extract_command[s], but this is obviously undesirable. Trevor Vaughan and I discussed this in the community Slack today, and he's left a comment upstream at https://bugzilla.redhat.com/show_bug.cgi?id=132608, hopefully something comes of it. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2359) Add a umask option to set the agent's umask predictably
Title: Message Title Andrew Bramble commented on PUP-2359 Re: Add a umask option to set the agent's umask predictably Inability to set the agent umask is certainly a problem with package providers in particular which for which permission modes are not a first class concept. `gem install` and `pip install` and their providers are subject to the umask they're running under and this causes real problems when running an agent on a system with a very restrictive umask. Why is this a 'Wont 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 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-644) Collect analytics on catalogs applied with bolt.
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-644 Collect analytics on catalogs applied with bolt. Change By: Melissa Amos Release Notes: Not Needed Enhancement 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-939) Bolt from Homebrew throws errors on command run when using ed25519
Title: Message Title Nick Le Mouton commented on BOLT-939 Re: Bolt from Homebrew throws errors on command run when using ed25519 Not sure how to see the headers of those keys, but if I run `ssh-keygen -lf ` the output of the two keys looks similar 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4199) Puppet query - Issue with contents of arrays and type
Title: Message Title Erik Hansen updated an issue PuppetDB / PDB-4199 Puppet query - Issue with contents of arrays and type Change By: Erik Hansen Priority: Normal Major 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-939) Bolt from Homebrew throws errors on command run when using ed25519
Title: Message Title Michael Smith commented on BOLT-939 Re: Bolt from Homebrew throws errors on command run when using ed25519 Are there differences in the format of your private keys? Different headers for example. 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-939) Bolt from Homebrew throws errors on command run when using ed25519
Title: Message Title Nick Le Mouton commented on BOLT-939 Re: Bolt from Homebrew throws errors on command run when using ed25519 I tried it with a new ed25519 key and it seemed to work as expected. My old key seems to be causing issues, but works fine for ssh/scp etc etc. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4196) KahaDB has 1.7GB logs
Title: Message Title Rob Browning commented on PDB-4196 Re: KahaDB has 1.7GB logs I'm not certain, but I suspect this may another instance of https://tickets.puppetlabs.com/browse/PDB-3511 which should be fixed in the 4.2.3.x long term support (LTS) series (I think in 4.2.3.3) and in 4.3+ (since we stopped using activemq), but it's not fixed in 4.2.x releases after 4.2.3 because the fix was created for the LTS release later. If feasible, upgrading should prevent the problem from reoccurring, and after the upgrade to 4.3+ (would recommend 5.2), once the "mq-migrated" file has been created in the vardir, you're free to just delete the activemq/kahadb directories if they're still taking up much space. 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-996) Prettify (or support prettifying) JSON output when using --verbose
Title: Message Title
Reid Vandewiele updated an issue
Puppet Task Runner / BOLT-996
Prettify (or support prettifying) JSON output when using --verbose
Change By:
Reid Vandewiele
Right now, when you add {{--verbose}} to an invocation of Bolt it will print detailed information about what it's doing, often in the form of JSON objects.Oftentimes, it can be very difficult to make sense of this though since the JSON is printed without line breaks or indentation. That is, not prettified.{code}[reidmv@halcyon:~/src/puppet/] % bolt apply --nodes winrm://10.234.1.11 --user Administrator --password --no-ssl-verify -e 'notify { "hello": }' --verbosePlease enter your password:Loading modules from /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.3.0/bolt-modules:/Users/reidmv/.puppetlabs/bolt/modules:/Users/reidmv/.puppetlabs/bolt/site:/opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.3.0/modulesStarting: install puppet and gather facts on winrm://10.234.1.11Starting: task puppet_agent::version on winrm://10.234.1.11Running task puppet_agent::version with '{"_task"=>"puppet_agent::version"}' on ["winrm://10.234.1.11"]{"node":"winrm://10.234.1.11","status":"success","result":{"version":"6.0.2","source":"C:/Program Files/Puppet Labs/Puppet/VERSION"}}Finished: task puppet_agent::version with 0 failures in 2.47 secPuppet Agent 6.0.2 installed on winrm://10.234.1.11Starting: task apply_helpers::custom_facts on winrm://10.234.1.11Running task apply_helpers::custom_facts with '{"plugins"=>#, "_task"=>"apply_helpers::custom_facts"}' on ["winrm://10.234.1.11"]{"node":"winrm://10.234.1.11","status":"success","result":{"aio_agent_version":"6.0.2","architecture":"x64","dhcp_servers":{"Ethernet":"192.168.0.3","system":"192.168.0.3"},"dmi":{"manufacturer":"Seabios","product":{"name":"OpenStack Nova","serial_number":"3c2513f4-b791-4ce7-9b2f-558c71093ec7"}},"domain":"platform9.puppet.net","facterversion":"3.12.0","fqdn":"win-2012-0.platform9.puppet.net","hardwareisa":"x64","hardwaremodel":"x86_64","hostname":"win-2012-0","hypervisors":{"kvm":{"openstack":true}},"id":"WIN-2012-0\\Administrator","identity":{"privileged":true,"user":"WIN-2012-0\\Administrator"},"interfaces":"Ethernet","ipaddress":"192.168.0.5","ipaddress6":"fe80::402f:43bf:4d05:dc56%12","ipaddress6_Ethernet":"fe80::402f:43bf:4d05:dc56%12","ipaddress_Ethernet":"192.168.0.5","is_virtual":true,"kernel":"windows","kernelmajversion":"6.3","kernelrelease":"6.3.9600","kernelversion":"6.3.9600","macaddress":"FA:16:3E:3E:87:ED","macaddress_Ethernet":"FA:16:3E:3E:87:ED","manufacturer":"Seabios","memory":{"system":{"available":"2.56 GiB","available_bytes":2753695744,"capacity":"35.88%","total":"4.00 GiB","total_bytes":4294537216,"used":"1.44 GiB","used_bytes":1540841472}},"memoryfree":"2.56 GiB","memoryfree_mb":2626.12890625,"memorysize":"4.00
Jira (PDB-4199) Puppet query - Issue with contents of arrays and type
Title: Message Title
Erik Hansen created an issue
PuppetDB / PDB-4199
Puppet query - Issue with contents of arrays and type
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/11/28 2:05 PM
Labels:
maintenance
Priority:
Normal
Reporter:
Erik Hansen
There seems to be an issue with the contents of Arrays and interpreting the type when processing a query. For instance this query worked in 2016.4.13:
curl -X POST -H 'Content-Type:application/json' http://localhost:8080/pdb/query/v4/nodes -d '{"query": ["in", ["fact", "uptime_seconds"], ["array",["2.0","150.0", "30"]]]}'
However in 2018.1.4 it returns an error: "All values in array must be the same type." The example comes from documentation here: https://puppet.com/docs/puppetdb/6.0/api/query/v4/ast.html#array
Jira (PUP-9320) update documentation for generate function to clarify possible return values
Title: Message Title Jacob Helwig commented on PUP-9320 Re: update documentation for generate function to clarify possible return values PR merged to Puppet master branch in 4fc93dd032. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9247) Puppet pidlock checks only look for PID if it is running, not process name
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-9247 Puppet pidlock checks only look for PID if it is running, not process name Change By: Geoff Nichols Sprint: Platform OS 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9247) Puppet pidlock checks only look for PID if it is running, not process name
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-9247 Puppet pidlock checks only look for PID if it is running, not process name Change By: Geoff Nichols Team: Coremunity Platform OS 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4198) Investigate rampant (often tiny) temp file creation
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-4198
Investigate rampant (often tiny) temp file creation
Change By:
Rob Browning
It looks like this may be jsonb operator related, but not sure. We've observed it in at least two contexts, the (old) fact-path-gc query, and migration 66. In the former case, using a temp table side-stepped the issue, and in the latter a 2GB+ work-mem did. Let's poke around and see if we can figure out what's going on. In the migration case, this query may have been the culprit (was notable in the pg stat activity):{code:sql} update factsets fs set stable = (select json_object_agg(name, value) ...{code}[~gabe] has observed the migration problem.
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
Jira (PDB-4197) Update to clj-parent 2.4.0 for 6.1 release
Title: Message Title Robert Roland assigned an issue to Robert Roland PuppetDB / PDB-4197 Update to clj-parent 2.4.0 for 6.1 release Change By: Robert Roland Assignee: Robert Roland 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4198) Investigate rampant (often tiny) temp file creation
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4198 Investigate rampant (often tiny) temp file creation Issue Type: Task Assignee: Unassigned Created: 2018/11/28 11:32 AM Priority: Normal Reporter: Rob Browning It looks like this may be jsonb operator related, but not sure. We've observed it in at least two contexts, the (old) fact-path-gc query, and migration 66. In the former case, using a temp table side-stepped the issue, and in the latter a 2GB+ work-mem did. Let's poke around and see if we can figure out what's going on. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4197) Update to clj-parent 2.4.0 for 6.1 release
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4197 Update to clj-parent 2.4.0 for 6.1 release Issue Type: Task Assignee: Unassigned Created: 2018/11/28 11:22 AM Fix Versions: PDB 6.1.0 Priority: Normal Reporter: Rob Browning Puppetserver intends to move to 2.4.0 for the release, so let's go ahead, so we'll have time to vet the change. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9330) Unable to enfource SELinux attributes for files in /dev/shm
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9330 Unable to enfource SELinux attributes for files in /dev/shm Change By: Melissa Stone Labels: SELinux Team: Coremunity Sprint: Platform Core KANBAN Component/s: Types and Providers Component/s: Community 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
Jira (PUP-9330) Unable to enfource SELinux attributes for files in /dev/shm
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-9330 Unable to enfource SELinux attributes for files in /dev/shm Change By: Melissa Stone Assignee: Melissa Stone 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4164) Upgrade lein-parent
Title: Message Title Robert Roland assigned an issue to Robert Roland PuppetDB / PDB-4164 Upgrade lein-parent Change By: Robert Roland Assignee: Robert Roland 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-982) Create new plan executor application with /plan/run endpoint
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-982
Create new plan executor application with /plan/run endpoint
Change By:
Lucy Wyman
We'll need to create a new ruby application, similar to bolt-server.The application should have a '/plan/run' endpoint, which receives requests, starts executing the specified plan, and returns a status response.Requests should have the following format:* {{plan_name}} (required, string)* {{environment}} (string, default production)* {{job_id}} (required, string)* {{description}} (optional, string)* {{params}} (required, hash){code}{ "plan_name" : "canary", "environment": "production", "job_id": "123842", "description" : "Start the canary plan on node1 and node2", "params" : {"nodes" : ["node1.example.com", "node2.example.com"],"command" : "whoami","canary" : 1 }}{code}Response should be " {status: "running"} " or an error object
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this
Jira (PUP-9247) Puppet pidlock checks only look for PID if it is running, not process name
Title: Message Title Scott Garman assigned an issue to Scott Garman Puppet / PUP-9247 Puppet pidlock checks only look for PID if it is running, not process name Change By: Scott Garman Assignee: Scott Garman 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9312) puppet package provider fails when reading from registry
Title: Message Title Erick Banks updated an issue Puppet / PUP-9312 puppet package provider fails when reading from registry Change By: Erick Banks Sprint: Windows PupperCon 2018-11-16, Windows 2018-11-28 , Windows 2018-12-05 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9335) Puppet ssl application should use agent run mode
Title: Message Title Josh Cooper commented on PUP-9335 Re: Puppet ssl application should use agent run mode /cc Maggie Dreyer, Justin Stoller 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9335) Puppet ssl application should use agent run mode
Title: Message Title Josh Cooper created an issue Puppet / PUP-9335 Puppet ssl application should use agent run mode Issue Type: Bug Affects Versions: PUP 6.0.0 Assignee: Unassigned Created: 2018/11/28 9:44 AM Fix Versions: PUP 6.0.5 Priority: Normal Reporter: Josh Cooper If you override certname, server, or ca_server (or related port settings) in the [agent] section of puppet.conf, then the puppet ssl application will not resolve settings the same way that puppet agent does. For example, if you do: [agent] server = server.example.com Then puppet ssl submit_request will attempt to connect to the default puppet instead.
Jira (PUP-9335) Puppet ssl application should use agent run mode
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9335 Puppet ssl application should use agent run mode 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 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-997) puppet_agent::install doesn't match on RedhatEnterpriseServer platform
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-997 puppet_agent::install doesn't match on RedhatEnterpriseServer platform 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 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-997) puppet_agent::install doesn't match on RedhatEnterpriseServer platform
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-997 puppet_agent::install doesn't match on RedhatEnterpriseServer platform 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 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-982) Create new plan executor application with /plan/run endpoint
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-982 Create new plan executor application with /plan/run endpoint 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 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-8691) running agent fails with eval_generate error
Title: Message Title Josh Cooper commented on PUP-8691 Re: running agent fails with eval_generate error Mohiddin khan puppet agents will by default attempt to connect to the host named "puppet". Which is most likely what's happening here. Make sure to configure the server setting in the agent's puppet.conf. Also make sure it's in the main section. 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-997) puppet_agent::install doesn't match on RedhatEnterpriseServer platform
Title: Message Title
Lucy Wyman created an issue
Puppet Task Runner / BOLT-997
puppet_agent::install doesn't match on RedhatEnterpriseServer platform
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/11/28 7:41 AM
Priority:
Normal
Reporter:
Lucy Wyman
The agent install task will only match rhel platforms where facter returns Redhat, but redhat enterprise server returns RedhatEnterpriseServer. We should modify https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/52b5b6abc2d10fb8827edead34ef8ebe4adf1e29/tasks/install_shell.sh#L73 to accept either.
"result": {
"_output": "07:33:08 -0500 INFO: Version parameter not defined, assuming latest\n07:33:08 -0500 INFO: Downloading Puppet latest for RedHatEnterpriseServer...\n07:33:08 -0500 CRIT: Sorry RedHatEnterpriseServer is not supported yet!\n",
"_error": {
"kind": "puppetlabs.tasks/task-error",
"issue_code": "TASK_ERROR",
Jira (PUP-9334) puppet agent apllies catalog successfully but daemon fails
Title: Message Title
jagadish honnappa updated an issue
Puppet / PUP-9334
puppet agent apllies catalog successfully but daemon fails
Change By:
jagadish honnappa
*Puppet Version:puppet-server-3.8.7-1* *Puppet Server Version:puppet-server-3.8.7-1* *OS Name/Version:all RHEL*when we run "puppet agent -t" it applies catalog without any error/issue.whereas when daemon runs it fails with below errorNov 28 10:38:04 servername puppet-agent[2478]: Error connecting to puppet.master.servername:8140: Inappropriate ioctl for device - getaddrinfoNov 28 10:38:04 servername puppet-agent[2478]: Unable to fetch my node definition, but the agent run will continue:Nov 28 10:38:04 servername puppet-agent[2478]: getaddrinfo: Name or service not knownNov 28 10:38:04 servername puppet-agent[2478]: (/File[/var/lib/puppet/facts.d]) Failed to generate additional resources using 'eval_generate': getaddrinfo: Name or service not known we use srv_domaintried to put server name instead of srv_domain... still same issue *Desired Behavior:**should run successfully even when daemon runs[puppet]* *Actual Behavior:*Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.Examples: Run puppet agent with --test --trace --debugRelevant sections of {{/var/log/puppetlabs/puppetserver/puppetserver.log}} or any applicable logs from the same directory.For more detailed information turn up the server logs by upping the log level in the server's logback.xmlRelevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig)For memory issues with server heap dumps are also helpful.
Add Comment
Jira (PUP-9323) Resolve Deferred values on demand instead of at catalog read time
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9323 Resolve Deferred values on demand instead of at catalog read time Change By: Henrik Lindberg Fix Version/s: PUP 6.1.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 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-9323) Resolve Deferred values on demand instead of at catalog read time
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-9323 Resolve Deferred values on demand instead of at catalog read time Change By: Henrik Lindberg Assignee: Henrik Lindberg 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2089) Error messages did not store in last_run_summary.yaml when config failed.
Title: Message Title Anton Fomenko commented on PUP-2089 Re: Error messages did not store in last_run_summary.yaml when config failed. Any chances of this being fixed. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9334) puppet agent allies catalog successfully but daemon fails
Title: Message Title jagadish honnappa created an issue Puppet / PUP-9334 puppet agent allies catalog successfully but daemon fails Issue Type: Bug Assignee: Unassigned Components: Puppet Server Created: 2018/11/28 2:08 AM Priority: Normal Reporter: jagadish honnappa Puppet Version:puppet-server-3.8.7-1 Puppet Server Version:puppet-server-3.8.7-1 OS Name/Version:all RHEL when we run "puppet agent -t" it applies catalog without any error/issue. whereas when daemon runs it fails with below error Nov 28 10:38:04 servername puppet-agent[2478]: Error connecting to puppet.master.servername:8140: Inappropriate ioctl for device - getaddrinfo Nov 28 10:38:04 servername puppet-agent[2478]: Unable to fetch my node definition, but the agent run will continue: Nov 28 10:38:04 servername puppet-agent[2478]: getaddrinfo: Name or service not known Nov 28 10:38:04 servername puppet-agent[2478]: (/File[/var/lib/puppet/facts.d]) Failed to generate additional resources using 'eval_generate': getaddrinfo: Name or service not known we use srv_domain tried to put server name instead of srv_domain... still same issue Desired Behavior: should run successfully even when daemon runs[puppet] Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful.
Jira (PUP-9328) puppet can't recognize Include syntax in yum.conf
Title: Message Title Fu Chen updated an issue Puppet / PUP-9328 puppet can't recognize Include syntax in yum.conf Change By: Fu Chen Affects Version/s: PUP 6.0.4 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. For more options, visit https://groups.google.com/d/optout.
