Jira (PUP-3664) Invalid metadata.json in module root causes Error 400
Title: Message Title Hunter Haugen commented on PUP-3664 Re: Invalid metadata.json in module root causes Error 400 If the module is a plugin-only module (ie, does not have manifests that are declared) then the erroneous metadata.json would not raise an error. The module will be silently ignored by pluginsync instead. The error WILL be raised for puppet module list though. It would be nice if the puppet master's pluginsync raised an error as well. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1187) Logs Metrics: (query) Provide end points for querying report logs, metrics for a specific report
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1187 Logs Metrics: (query) Provide end points for querying report logs, metrics for a specific report Change By: Kenneth Barber Designdoc:https://docs.google.com/a/puppetlabs.com/document/d/1oxr-YATkV8E67Gq1YJ8vfsxazAp0DKSagAPTUbxOn4g/edit#Thisinvolvescreatinganewspecificendpointfordrillingdownintoreportlogs.Something like/v4/reports/hash/[logs|metrics] Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1187) Logs: (query) Provide end point for querying report logs
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1187 Logs: (query) Provide end point for querying report logs Change By: Kenneth Barber Designdoc:https://docs.google.com/a/puppetlabs.com/document/d/1oxr-YATkV8E67Gq1YJ8vfsxazAp0DKSagAPTUbxOn4g/edit# Thisinvolvescreatinganewspecificendpointfordrillingdownintoreportlogs. Something Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1187) Logs Metrics: (query) Provide end points for querying report logs, metrics for a specific report
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1187 Logs Metrics: (query) Provide end points for querying report logs, metrics for a specific report Change By: Kenneth Barber Summary: Logs Metrics :(query)Provideend point points forqueryingreportlogs ,metricsforaspecificreport Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1244) Status: (query) Add capability for latest-report? handling for reports
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1244 Status: (query) Add capability for latest-report? handling for reports Issue Type: New Feature Assignee: Unassigned Created: 2015/02/19 11:51 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Kenneth Barber Design doc is here: https://docs.google.com/a/puppetlabs.com/document/d/1oxr-YATkV8E67Gq1YJ8vfsxazAp0DKSagAPTUbxOn4g/edit# We'll need the capability to analyze the latest report as part of the status filtering query count capability. This loosely involves surfacing the property 'latest_report?' like events, so it can be queried and filtered on Add Comment
Jira (PDB-1245) run services (at least) appears to consume stdin
Title: Message Title Rob Browning created an issue PuppetDB / PDB-1245 run services (at least) appears to consume stdin Issue Type: Bug Assignee: Unassigned Created: 2015/02/19 11:57 AM Priority: Minor Reporter: Rob Browning Noticed when running something like: lein run services ... | less puppetdb appeared to be eating some of the characters typed on stdin (to page the output, etc.). I fixed it like this: lein run services ... /dev/null | less It'd be nice to fix that, if feasible.
Jira (PUP-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Kylo Ginsberg commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data This work added a required dependency for puppet on the deep_merge gem. In the past, we have been cautious about adding new gems as hard requirements unless they were either a) puppet labs software (e.g. facter, hiera) or b) vendored (e.g. rgen). So deep_merge is the first to break that pattern (note that the only hard requirements are puppet/facter/hiera and rake (because rake is essentially assumed to always be there): https://github.com/puppetlabs/puppet/blob/a6486d548229128918dad72a90818e24266cea66/Gemfile#L29 So several possibilities here: 1) we decide that in the new AIO world we're okay adding additional gems as hard requirements (and we just bundle them in AIO, as we do for deep_merge) 2) we make this requirement optional, and make deep_merge a puppet feature as is done for all the other optional/extra gems 3) we vendor deep_merge as we did for rgen 4) leave this change as-is: deep_merge is special In some ways I like (1) best, but I'd like that to be a conscious decision. If we do open the door for adding hard requirements, we'd enable removing some of the feature checks e.g.: msgpack could be a hard requirement (not currently in puppet-agent but could be) ruby-augeas could be a hard requirement (currently only commented out in the Gemfile) and we could then enable spec testing of the augeas code (currently those tests never run in classic puppet CI b/c we don't test with the gem installed ruby-shadow similarly ... Also, rgen/pathspec/semantic could all be unvendored, included in puppet-agent and made a hard requirement, etc. Puppet code base trims down! The main downside to this line of thinking would be additional requirements on those who run puppet as a gem or roll their own packages. Thoughts? /cc Henrik Lindberg, Matthaus Owens, Eric Sorenson. Add Comment
Jira (PDB-1192) Metrics: Get metrics storage and retrieval working
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1192 Metrics: Get metrics storage and retrieval working Change By: Kenneth Barber Summary: Metrics: Schemamigrationfor Get metrics storageandretrievalworking Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Daniele Sluijters commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data I'd go with option 1. The official vendor packages are AIO and as such bundling in an extra dependency shouldn't really be an issue, especially not for something as useful as this. Maybe there needs to be some kind of threshold but always holding back risks the Puppet codebase growing with 'hacky ports' of something for which a decent gem already exists. If distributions want to provide their own non-AIO packaging it's up to them to figure this out. Debian already has the habit of ripping out any and every single dependency into its own package. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1184) Logs: Add logs storage and retrieval support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1184 Logs: Add logs storage and retrieval support Change By: Kenneth Barber Story Points: 2 3 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3821) Use of cfacter on Windows causes error
Title: Message Title Kurt Wall commented on PUP-3821 Re: Use of cfacter on Windows causes error Verified in said MSI at said SHA: C:\Program Files (x86)\Puppet Labs\Puppet\binpuppet agent --cfacter --test Info: Creating a new SSL key for jxvd651fpd1q1zr.delivery.puppetlabs.net Error: Could not request certificate: getaddrinfo: No such host is known. Exiting; failed to retrieve certificate and waitforcert is disabled C:\Program Files (x86)\Puppet Labs\Puppet\bin Add Comment
Jira (PUP-3821) Use of cfacter on Windows causes error
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-3821 Use of cfacter on Windows causes error Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1184) Logs: Add logs storage and retrieval support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1184 Logs: Add logs storage and retrieval support Change By: Kenneth Barber Summary: Logs: Createschemamigrationtostoreloginformation Addlogsstorageandretrievalsupport Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1184) Logs: Add logs storage and retrieval support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1184 Logs: Add logs storage and retrieval support Change By: Kenneth Barber Designdoc:https://docs.google.com/a/puppetlabs.com/document/d/1oxr-YATkV8E67Gq1YJ8vfsxazAp0DKSagAPTUbxOn4g/edit# Weneedtocreatethenewschemalayoutforstoringlogs. Changethecommandtostorelogs,storethemandhavetheterminusbemodifiedtosendthisalong.Logsshouldbeorderedintheterminusbytimestamp.Querycapabilitytoretrievelogsfromthereportsendpointshouldbeadded. Wealsoshouldconfirmthatthelogsareremovedduringreportremovalusingcascadingrelationships. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Michael Smith commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data This impacts how acceptance tests from git are run. The scripts that install puppet/facter/hiera don't seem to be aware of gem dependencies. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1228) investigate a paging solution for multi-row responses
Title: Message Title Kenneth Barber commented on PDB-1228 Re: investigate a paging solution for multi-row responses Here are some differential explain plans, with the mutli-row solution we have today, compared to a single row json_agg based solution: https://gist.github.com/kbarber/698238de6825e534b713 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2836) Incorrect lockfile placemen
Title: Message Title Nick Moriarty commented on PUP-2836 Re: Incorrect lockfile placemen We're hitting this issue occasionally; at present, we're planning to work around it by changing agent_catalog_run_lockfile to $rundir/agent_catalog_run.lock. At present, the default value of this is $statedir/agent_catalog_run.lock, which persists across reboots - I'd recommend this change to $rundir/agent_catalog_run.lock (which is where the main pidfiles live) so it doesn't persist. This issue crops up occasionally (we're seeing it in 3.7.3) - even with the sanity checking of lockfiles, it's possible to have a catalog run lockfile that persists across a reboot, containing a valid PID which references a completely different process after the reboot. In this case, Puppet may never run (consider the case where it ends up pointing at sshd, for example). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2836) Incorrect lockfile placement
Title: Message Title Nick Moriarty updated an issue Puppet / PUP-2836 Incorrect lockfile placement Change By: Nick Moriarty Affects Version/s: PUP3.7.3 Summary: Incorrectlockfile placemen placement Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt, we continue to suffer from one more issue. Two of our slaves begin to hang from time to time. Following issues can be found in puppetdb.log: 2015-02-19 10:33:00,701 WARN [o.e.j.s.ServerConnector] java.io.IOException: Too many open files at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method) ~[na:1.7.0_51] at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:241) ~[na:1.7.0_51] at org.eclipse.jetty.server.ServerConnector.accept(ServerConnector.java:336) ~[puppetdb.jar:na] at org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:466) ~[puppetdb.jar:na] at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607) [puppetdb.jar:na] at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536) [puppetdb.jar:na] at java.lang.Thread.run(Thread.java:744) [na:1.7.0_51]
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Henrik Lindberg commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back Now also acceptance tests are updated with explicit install of deep_merge gem on all hosts for the git and package cases. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title John Duarte commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back Michael Smith, Jenkins CI has failed at 354c19abc7fc23f8836a54e80dc829691c6d. Previously passed at 17afe9761a2c97feacb58d1d7e88201dbb3d. See the following job results: https://jenkins.puppetlabs.com/job/Hiera-Acceptance-master/203/ The tests fail to load deep_merge/core Error Message Host 'tun7xm0r4onxngv.delivery.puppetlabs.net' exited with 1 running: puppet apply --verbose /tmp/apply_manifest.pp.VCSHZw Last 10 lines of output were: [1;31mError: Could not run: cannot load such file -- deep_merge/core[0m Add Comment
Jira (PUP-3821) Use of cfacter on Windows causes error
Title: Message Title Ethan Brown commented on PUP-3821 Re: Use of cfacter on Windows causes error The latest MSIs from last nights pipeline (based on the aio2 branch) are now available. These should contain cfacter built from master branch (there will be a versions.txt that can be found after installing the MSI that details which cfacter SHA was used) http://builds.puppetlabs.lan/puppet-agent/c012e34025bda8a4df791b93481a79ae3d3b64fe/artifacts/windows/ Go to town! Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1225) Update fact storage and querying to use the new path column in the facts table
Title: Message Title Rob Browning assigned an issue to Unassigned PuppetDB / PDB-1225 Update fact storage and querying to use the new path column in the facts table Change By: Rob Browning Assignee: RobBrowning Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3927) (Regression) Redhat service provider is being used on systemd-based Fedora systems
Title: Message Title Scott Garman assigned an issue to Scott Garman Puppet / PUP-3927 (Regression) Redhat service provider is being used on systemd-based Fedora systems Change By: Scott Garman Assignee: ScottGarman Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3927) (Regression) Redhat service provider is being used on systemd-based Fedora systems
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-3927 (Regression) Redhat service provider is being used on systemd-based Fedora systems Change By: Eric Thompson Assignee: EricThompson QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3927) (Regression) Redhat service provider is being used on systemd-based Fedora systems
Title: Message Title Scott Garman commented on PUP-3927 Re: (Regression) Redhat service provider is being used on systemd-based Fedora systems Eric Thompson This is now ready for testing. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3927) (Regression) Redhat service provider is being used on systemd-based Fedora systems
Title: Message Title Scott Garman assigned an issue to Eric Thompson Puppet / PUP-3927 (Regression) Redhat service provider is being used on systemd-based Fedora systems Change By: Scott Garman Assignee: ScottGarman EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3927) (Regression) Redhat service provider is being used on systemd-based Fedora systems
Title: Message Title Eric Thompson commented on PUP-3927 Re: (Regression) Redhat service provider is being used on systemd-based Fedora systems thanks Scott. i might not get to this today and i'm on PTO tomorrow. assigning to QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1192) Metrics: Get metrics storage and retrieval working
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1192 Metrics: Get metrics storage and retrieval working Change By: Wyatt Alt Assignee: WyattAlt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Henrik Lindberg commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data I am for option 1, and to stop vendoring as AIO is our packaged solution going forward. The issues are the use cases where AIO is not applicable (our own testing, testing when developing by us and by the community). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1243) We should accept null fields for noop for incoming commands
Title: Message Title AJ Roetker assigned an issue to AJ Roetker PuppetDB / PDB-1243 We should accept null fields for noop for incoming commands Change By: AJ Roetker Assignee: AJRoetker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Kylo Ginsberg commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data I'm for option 1 also. Michael Smith raises a good point about acceptance test from git. I have a couple ideas (tweak install.rb? add beaker helpers?) but I'm not sure on the best course there. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1243) We should accept null fields for noop for incoming commands
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1243 We should accept null fields for noop for incoming commands Change By: AJ Roetker Sprint: PuppetDB2015- 03 02 - 11 25 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-298) Update FS layout for hiera
Title: Message Title Henrik Lindberg commented on HI-298 Re: Update FS layout for hiera ping Josh Cooper should the paths for windows be changed or not? They are currently unchanged. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3884) Craft migration/upgrade script for use in the AIO puppet agent
Title: Message Title Kylo Ginsberg commented on PUP-3884 Re: Craft migration/upgrade script for use in the AIO puppet agent WIth renewed attention to migration, I'm thinking this ticket really needs to be coordinated with Joshua Partlow's team. Josh, do we know enough about the integration plan for migration to scope what the requirements for the puppet-agent migration/upgrade script are? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Kylo Ginsberg commented on PUP-3632 Re: Update paths and defaults for the unified FS layout Merged to master in https://github.com/puppetlabs/puppet/commit/70feeef3810850c99199f9e702048848c0f02bf3 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Ethan Brown commented on PUP-4009 Re: Add Cfacter 0.4.0 to Windows MSI Yes, correct Melissa Stone - thanks for the clarification. The new AIO pipelines are pulling from https://github.com/puppetlabs/puppet-agent/blob/master/configs/components/cfacter.json which specifies origin/master at the moment for the CFacter version. The new pipelines don't use the existing ext/build_defaults.yaml. Such builds were produced successfully yesterday (2/18) for the first time as part of the new pipeline setup: http://builds.puppetlabs.lan/puppet-agent/c012e34025bda8a4df791b93481a79ae3d3b64fe/artifacts/windows/ The big question now is going to be how we pin to a well known CFacter version when we finally ship as I don't believe it's expressed as a pipeline configuration value. This is a question for Matthaus Owens and Justin Stoller Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3829 pip package provider is broken on EL (where osfamily is RedHat) Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Michael Smith commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back Fixing with patches to add deep_merge in acceptance runs, similar to what was done for Puppet. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1243) We should accept null fields for noop for incoming commands
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1243 We should accept null fields for noop for incoming commands Issue Type: Bug Assignee: Unassigned Created: 2015/02/19 8:28 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Kenneth Barber Currently null is not null in the database, but not optional when sending a command via 'store reports'. This is going to make it impossible for users with old data, whereby the value is null, to be able to export and then import the same data. Add Comment
Jira (PDB-1242) PR (1264): Remove some unused legacy query code - kbarber
Title: Message Title gepetto-bot commented on PDB-1242 Re: PR (1264): Remove some unused legacy query code - kbarber Pull request Remove some unused legacy query code has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title
Eric Thompson commented on PUP-3829
Re: pip package provider is broken on EL (where osfamily is RedHat)
verified on rhel7 through some pain in installing pip. instructions, if you aren't used to python/pip: http://linuxconfig.org/installation-of-pip-the-python-packaging-tool-on-rhel-7-linux
[root@xk3herqvq3jcrpq setuptools-7.0]# puppet apply -e 'package {s3cmd: ensure = installed, provider=pip}'
Notice: Compiled catalog for xk3herqvq3jcrpq.delivery.puppetlabs.net in environment production in 0.77 seconds
Notice: /Stage[main]/Main/Package[s3cmd]/ensure: created
Notice: Applied catalog in 1.85 seconds
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Justin Stoller commented on PUP-4009 Re: Add Cfacter 0.4.0 to Windows MSI IIRC, the idea was that CFacter would be promoted into the puppet-agent build the same was as the Ruby components. I believe last I checked there was some open questions around a compiled project's tests/slave usage would integrate into that workflow and everyone decided that focusing on Puppet was where to put our energy for the time being. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title John Duarte commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back FYI: The failure to load deep_merge/core is also causing stable acceptance to fail: https://jenkins.puppetlabs.com/job/Hiera-Acceptance-stable/364/ cc: Josh Cooper, Roger Ignazio Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Michael Smith commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back I think both of those are actually unrelated to this commit, but they need to be fixed. They're all coming from Puppet's dependency on deep_merge/core; it appears Hiera stable tests against Puppet master. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Kylo Ginsberg The comingupdatetotheFSlayout SSoT for ourprojectsrequiresseveralchangestodefaultpathingandconfigfilestoensurethatthecorrectdirectoriesareused.Offthetopofmyheadthisincludesdefaults.rbandpuppet.confbutitmayextendintootherfilesaswell.Defaultlogging paths is probablyalsoaffected.Thenewlayoutisdescribedhere now : https:// confluence github . puppetlabs. com/ display/DEL/Unified+Puppet+Agent+LayoutThelayoutintheunifiedPuppetAgentwillbeasfollows:Puppetpuppetdirwillbe/etc/ puppetlabs/puppet Puppetconfdirwillbe -specifications / etc blob / puppetlabs master / puppetPuppetcodedirwillbe/etc/puppetlabs/codePuppetvardirwillbe/opt/puppetlabs/agent/cachePuppetssldirwillbe/etc/puppetlabs/puppet/sslConfigfiles:/etc/puppetlabs/$project/$project file_paths . conf md Logs:/var/log/puppetlabs/$project.logPrefixis/opt/puppetlabs/puppetBinarieslivein/opt/puppetlabs/puppet/binLibrariesandheaderslivein/opt/puppetlabs/puppet/liband/opt/puppetlabs/puppet/include,respectivelyArchitectureindependentdata(manpagesforexample)in/opt/puppetlabs/puppet/shareUsermodulepath/etc/puppetlabs/code/modulesSystemmodulepath(forcorecommunitymodules)/opt/puppetlabs/puppet/modulesMCOplugindir:/opt/puppetlabs/mcollective/pluginsPidfiledir:/var/run/puppetlabsThislayoutwillhelpachievethefollowinggoals:EasiermigrationfromFOSStoPEforusers(nomigrationreallyintheunifiedagentworld)IsolationfrompotentialsystemlibraryconflictsSimplifyuserexperiencewithrespecttosoftwarelayoutbetweenFOSS/PESimplifydeploymentsystemsforFOSSandPEIsolateagentandservercomponentsUnifieddocumentationforthepuppetagent Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1229) change reports to use schema and retire validation.clj
Title: Message Title AJ Roetker assigned an issue to AJ Roetker PuppetDB / PDB-1229 change reports to use schema and retire validation.clj Change By: AJ Roetker Assignee: AJRoetker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title
Kylo Ginsberg updated an issue
Puppet / PUP-3809
Separate code (content?) and configuration directories for AIO packaging
Change By:
Kylo Ginsberg
Therehasbeenathreadgoingaroundbetweensomeengineeringfolksandsomereleasefolksabouttheneedforseparatingcode(orcontent)andconfigurationintotwodistinctdirectories.ThiswillmakeiteasiertosynctheappropriatefilesaroundtomultiplemastersviatheforthcomingFileSyncservice. The filesystemlayoutshouldlooklike:{code}#locations SSoT for 'puppet*'subcommandconfigfiles(agent,apply,master)/etc/puppetlabs/puppet/{puppet,auth,fileserver}.conf=canonicalconfigdirectory/etc/puppetlabs/puppet/ssl=puppet'ssslcerts#separatepuppetprojectsgettheirownconfigdirectoriesatthislevel/etc/puppetlabs/puppetserver=puppetserverconfigdir/etc/puppetlabs/puppetdb=puppetdbconfigdir#'code'constructs(i.e.inputsintoacatalog)gotonew'code'directory#this paths is usuallythecheckoutofar10kcontrolrepo now:https: / etc / puppetlabs/code=codedirincludeshiera github . yaml,hieradata,modules,manifests com / etc/ puppetlabs/ code/environments/=defaultlocationfor'$environmentpath'#binaries,libraries,modulesshippedwiththepackageliveunder/opt/puppetlabs/opt/puppetlabs/bin=symlinktargetfor' puppet ','puppetserver','puppetdb',etc./opt/puppetlabs/puppet=newruby - puppetroot(bin,lib,cache,plugins,include,shareunderneath) specifications / opt blob / puppetlabs master / puppet/modules=systemmodulepath/opt/puppetlabs/server=serversideappsliveunderneath/opt/puppetlabs/server/puppetserver/#stateandlogdirectories/var/run/puppetlabs=pidfilesgohere/var/log/puppetlabs=logfilesgohere{code} file_paths.md.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4026) Create specification for new AIO settings
Title: Message Title Kylo Ginsberg commented on PUP-4026 Re: Create specification for new AIO settings I also updated the description in the 3 linked tickets and in confluence to reference the specifications page for file paths. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1229) change reports to use schema and retire validation.clj
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1229 change reports to use schema and retire validation.clj Change By: AJ Roetker Sprint: PuppetDB2015-02-25 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-825) Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems
Title: Message Title Brook Shelley updated an issue Facter / FACT-825 Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems Change By: Brook Shelley Issue Type: NewFeature Bug Anissuewiththeprtdiagtimeoutthatwasaddressedinapreviousfixtofacterseemstohavebeenreverted,andtheoriginalfixof12secondscouldstillbetooshortforlargeSolarissystems.Considerincreasingthetimeout,orhavingitbearelativetimeout. https://support.puppetlabs.com/requests/1765https://projects.puppetlabs.com/issues/18141Thefixappliedhere:https://github.com/puppetlabs/facter/commit/d82f695a0f2b625a7719e4a07064a925dc11ed07Seemstohavebeendroppedhere:https://github.com/puppetlabs/facter/commit/1f835c682ab9a841c16cd73fe50033c82c6f89c0Tryingthelatestversionoffacter:root@its-gu-mph4:/export/home/e05593/facter-master#exportRUBYLIB=`pwd`/libroot@its-gu-mph4:/export/home/e05593/facter-master#bin/facter--version2.4.1root@its-gu-mph4:/export/home/e05593/facter-master#root@its-gu-mph4:/export/home/e05593/facter-master#bin/facter/dev/nullTimedoutafter6secondswhileresolvingfact='virtual',resolution='anonymous'BrokenPipeAlso,theoriginalfixof12secondsseemstobecuttingitabitclose,ifyouconsider:root@its-gu-mph4:/export/home/e05593/facter-master#timeprtdiag/dev/nullprtdiag/dev/null0.33suser1.44ssystem19%cpu9.312totalroot@its-gu-mph4:/export/home/e05593/facter-master#Perhaps20secondswouldbesaferfortheprtdiagtimeout. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Josh Cooper commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-825) Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-825 Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems Change By: Kylo Ginsberg Sprint: Client2015-03-18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-825) Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems
Title: Message Title Brook Shelley created an issue Facter / FACT-825 Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems Issue Type: New Feature Assignee: Eric Sorenson Created: 2015/02/19 3:59 PM Priority: Normal Reporter: Brook Shelley https://support.puppetlabs.com/requests/1765 https://projects.puppetlabs.com/issues/18141 The fix applied here: https://github.com/puppetlabs/facter/commit/d82f695a0f2b625a7719e4a07064a925dc11ed07 Seems to have been dropped here: https://github.com/puppetlabs/facter/commit/1f835c682ab9a841c16cd73fe50033c82c6f89c0 Trying the latest version of facter: root@its-gu-mph4:/export/home/e05593/facter-master # export RUBYLIB=`pwd`/lib root@its-gu-mph4:/export/home/e05593/facter-master # bin/facter --version 2.4.1 root@its-gu-mph4:/export/home/e05593/facter-master # root@its-gu-mph4:/export/home/e05593/facter-master # bin/facter /dev/null Timed out after 6 seconds while resolving fact='virtual', resolution='anonymous' Broken Pipe Also, the original fix of 12 seconds seems to be cutting it a bit close, if you consider: root@its-gu-mph4:/export/home/e05593/facter-master # time prtdiag /dev/null prtdiag /dev/null 0.33s user 1.44s system 19% cpu 9.312 total root@its-gu-mph4:/export/home/e05593/facter-master # Perhaps 20 seconds would be safer for the prtdiag timeout.
Jira (PUP-4018) Execute puppet AIO acceptance against puppetserver
Title: Message Title Josh Cooper commented on PUP-4018 Re: Execute puppet AIO acceptance against puppetserver This is ready for merge, as part of PUP-3632 and PR https://github.com/puppetlabs/puppet/pull/3634 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Josh Cooper Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-825) Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-825 Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems Change By: Kylo Ginsberg Scrum Team: ClientPlatform Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3546) Modify exec node terminus to support JSON
Title: Message Title Jean Bond commented on PUP-3546 Re: Modify exec node terminus to support JSON So this came my way because of the DOCS component on it... are there docs ramifications to this ticket at this point, or will there be? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-825) Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems
Title: Message Title Eric Sorenson commented on FACT-825 Re: Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems Kylo Ginsberg could someone on your team take a look at this? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4026) Create specification for new AIO settings
Title: Message Title Kylo Ginsberg assigned an issue to Eric Sorenson Puppet / PUP-4026 Create specification for new AIO settings Change By: Kylo Ginsberg Assignee: EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4026) Create specification for new AIO settings
Title: Message Title Kylo Ginsberg commented on PUP-4026 Re: Create specification for new AIO settings CI/Test is meaningless, but I'm going to put in Ready for Review so that Eric Sorenson has an opportunity to weigh in. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4027) Update embedded docs for package resource type in light of PUP-1073
Title: Message Title Kylo Ginsberg commented on PUP-4027 Re: Update embedded docs for package resource type in light of PUP-1073 Moved this to Ready for CI out of thoroughness. It doesn't need Test/Review beyond what Nick already gave it in the PR, so it can be Resolved once we have a green CI run. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-825) Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems
Title: Message Title Eric Sorenson assigned an issue to Kylo Ginsberg Facter / FACT-825 Default timeout for prtdiag in the 'virtual' fact is too low for large Solaris systems Change By: Eric Sorenson Assignee: EricSorenson KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3127) LDAP - introduce LDAP-Certificat Directory
Title: Message Title Scott Garman updated an issue Puppet / PUP-3127 LDAP - introduce LDAP-Certificat Directory Change By: Scott Garman Sprint: RE2015-02-25 Story Points: 2 3 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4031) Resource collectors can't be used as metaparameter values
Title: Message Title
Alex Jurkiewicz created an issue
Puppet / PUP-4031
Resource collectors can't be used as metaparameter values
Issue Type:
Bug
Affects Versions:
PUP 3.7.4, PUP 3.7.1
Assignee:
Unassigned
Components:
Language
Created:
2015/02/19 7:09 PM
Priority:
Normal
Reporter:
Alex Jurkiewicz
Using future parser, this is invalid:
exec { 'whatever': before = Network_route | |, }
You have to write this:
