Jira (PUP-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Henrik Lindberg, the way I see it, using the hiera_xxx functions is similar to explicitly specify the options with a parameter when using the lookup function. I.e. the user expresses a desire to override the default and should be able to do so. Therefore I'm in favor of keeping the hiera_xxx functions as they are. Another reason for this is that I view them as legacy functions that should be deprecated eventually. As such, it's better to just leave them as they are. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5414) Tag the release and create packages
Title: Message Title Kylo Ginsberg commented on PUP-5414 Re: Tag the release and create packages This release will be based on b628b07eb521caacc920f8b87749974d269a58bc. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5410) Update version number in source
Title: Message Title Kylo Ginsberg commented on PUP-5410 Re: Update version number in source This was already done. We've been updating version numbers asynchronously after release. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5409) Reconcile git commits and JIRA tickets
Title: Message Title Kylo Ginsberg commented on PUP-5409 Re: Reconcile git commits and JIRA tickets I ran the ticketmatch.rb script and Jira and git are reconciled. Also, all tickets have Release Notes fields updated. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5408) Is the code ready for release?
Title: Message Title Kylo Ginsberg commented on PUP-5408 Re: Is the code ready for release? Yes, it's already green and all tickets are in. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5411) Merge master into stable
Title: Message Title Kylo Ginsberg commented on PUP-5411 Re: Merge master into stable Z release off 3.x. Does not apply. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5407) puppet 3.8.4 2015-11-02 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5407 puppet 3.8.4 2015-11-02 Release Change By: Kylo Ginsberg Note that this date is a bit of a placeholder, but I wanted to get this ticket ready now.The code itself is ready so, the scheduling is mostly a question for [~melissa] and [~jorie]. Ideally we'd do this sometime before 11/11. puppet 3.8.4 2015-11-02 ReleaseWhen working through this ticket, add it to the board and then keep it in the Ready for Engineering column.Move the subtasks to In Progress when you are working on them and Resolved when you have completed them.In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. * The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. * Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. * When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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
Jira (PUP-5420) Send out announcements
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5420 Send out announcements Issue Type: Sub-task Assignee: Eric Sorenson Created: 2015/10/22 10:52 PM Priority: Normal Reporter: Kylo Ginsberg Melissa Stone: update the release google spreadsheet. Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014) Send the drafted release notes email. If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev). If this release has security implications, also send the release announcement to puppet-security-announce Make a PSA on IRC letting those kiddos know about the new release. Something along the lines of "PSA: facter 1.7.3 now available" Dependencies:
Jira (PUP-5421) Close all resolved tickets in Jira
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5421 Close all resolved tickets in Jira Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/10/22 10:52 PM Priority: Normal Reporter: Kylo Ginsberg Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%223.8.4%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select "Transition Issues" Step 3 - Select "Closed" Step 4 - Select "Fixed" in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies:
Jira (PUP-5407) puppet 3.8.4 2015-11-02 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5407 puppet 3.8.4 2015-11-02 Release Change By: Kylo Ginsberg Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5414) Tag the release and create packages
Title: Message Title
Kylo Ginsberg created an issue
Puppet / PUP-5414
Tag the release and create packages
Issue Type:
Sub-task
Assignee:
Melissa Stone
Created:
2015/10/22 10:51 PM
Priority:
Normal
Reporter:
Kylo Ginsberg
Tag and create packages
Developer provides the SHA - Henrik Lindberg - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m "1.7.3" 1.7.3
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git describe` will show you the tag. Make sure you're building what you think you're building.
Jira (PUP-5411) Merge master into stable
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5411 Merge master into stable Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/10/22 10:51 PM Priority: Normal Reporter: Kylo Ginsberg For some releases, the code base will need to be merged down to stable. NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: git fetch upstream git rebase upstream/master git checkout stable
Jira (PUP-5408) Is the code ready for release?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5408 Is the code ready for release? Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/10/22 10:51 PM Priority: Normal Reporter: Kylo Ginsberg If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable & master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%223.8.4%22
Jira (PUP-5409) Reconcile git commits and JIRA tickets
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5409 Reconcile git commits and JIRA tickets Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/10/22 10:51 PM Priority: Normal Reporter: Kylo Ginsberg Use the ticketmatch script to ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. cd ~/work git clone https://github.com/puppetlabs/ticketmatch cd ~/work/puppet # or whatever the repo is you're releasing from ruby ../ticketmatch/ticketmatch.rb Enter Git From Rev: 4.1.0 Enter Git To Rev: |master| stable Enter JIRA project: |PUP| Enter JIRA fix version: PUP 4.2.0 The output may contain the following headers: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF ...) Lists git commits that don't have a corresponding ticket, at least not for the specified fix version. If the commit has a ticket, but the ticket is not targeted correctly, then the ticket's fixVersion should be updated. This can frequently happen if a ticket is initially targeted for a future release (master), but is pulled into an earlier release (stable), but the ticket's fixVersion is not updated.
Jira (PUP-5416) Go/no-go meeting (before 4pm)
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5416 Go/no-go meeting (before 4pm) Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/10/22 10:51 PM Priority: Normal Reporter: Kylo Ginsberg This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time. Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Participants: Henrik Lindberg Jorie Tappa Eric Sorenson John Duarte Melissa Stone
Jira (PUP-5407) puppet 3.8.4 2015-11-02 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5407 puppet 3.8.4 2015-11-02 Release Change By: Kylo Ginsberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5407) puppet 3.8.4 2015-11-02 Release
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5407 puppet 3.8.4 2015-11-02 Release Issue Type: Task Assignee: Henrik Lindberg Created: 2015/10/22 10:51 PM Priority: Normal Reporter: Kylo Ginsberg puppet 3.8.4 2015-11-02 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
Jira (PUP-5418) Packages pushed
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5418 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/10/22 10:51 PM Priority: Normal Reporter: Kylo Ginsberg Push packages run `rake pl:jenkins:uber_ship` You will need the keys to the castle (aka the passphrase) for this to work. Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms. Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay. If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file. If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed. Dependencies:
Jira (PUP-5407) puppet 3.8.4 2015-11-02 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5407 puppet 3.8.4 2015-11-02 Release Change By: Kylo Ginsberg Sprint: Language 2015-11-11 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5412) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5412 Is the Jira tidy-up done for this release and prepared for the next one? Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/10/22 10:51 PM Priority: Normal Reporter: Kylo Ginsberg This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as "Released" in the Project Admin -> Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket): 'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone 'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for Everyone
Jira (PUP-5410) Update version number in source
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5410 Update version number in source Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/10/22 10:51 PM Priority: Normal Reporter: Kylo Ginsberg Bump VERSION in lib/PUP/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3". If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Reconcile git commits and JIRA tickets
Jira (PUP-5413) Prepare long form release notes and short form release story
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5413 Prepare long form release notes and short form release story Issue Type: Sub-task Assignee: Jorie Tappa Created: 2015/10/22 10:51 PM Priority: Normal Reporter: Kylo Ginsberg Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5417) Push tag
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5417 Push tag Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/10/22 10:51 PM Priority: Normal Reporter: Kylo Ginsberg The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. Dependencies: Go / No Go meeting (except where it's required to push the tag to build packages - MSIs) Add Comment This message was sent by Atlassian JIR
Jira (PUP-5419) Docs pushed
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5419 Docs pushed Issue Type: Sub-task Assignee: Jorie Tappa Created: 2015/10/22 10:52 PM Priority: Normal Reporter: Kylo Ginsberg Push the documentation updates to docs.puppetlabs.com. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5415) Smoke test packages
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5415 Smoke test packages Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/10/22 10:51 PM Priority: Normal Reporter: Kylo Ginsberg Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm. For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems. Lighter testing of Z releases is acceptable. Add a link to the Packages repository that you receive from the "Tag and create packages" subtask Ping folks on your team for help with different platforms. When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output. When a
Jira (PUP-5380) Slow catalog run after updating to puppet 3.7.5
Title: Message Title Eric Thompson commented on PUP-5380 Re: Slow catalog run after updating to puppet 3.7.5 validating on rhel7 against 3.x at SHA: 0b75d59 [root@e1oyf1ywgsa1fjh puppet]# puppet module install puppetlabs/apache Notice: Preparing to install into /etc/puppet/environments/production/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Notice: Installing -- do not interrupt ... /etc/puppet/environments/production/modules └─┬ puppetlabs-apache (v1.6.0) ├── puppetlabs-concat (v1.2.4) └── puppetlabs-stdlib (v4.9.0) [root@e1oyf1ywgsa1fjh puppet]# vi /etc/puppet/environments/production/m manifests/ modules/
Jira (PUP-5387) AIX service provider returns before service operations are complete
Title: Message Title William Hopper commented on PUP-5387 Re: AIX service provider returns before service operations are complete update: what's actually happening here is that when restarting a service, we stop it and send it into the stopping state, and then immediately try to start it. AIX will complain quietly at this, but still exit with 0 and ignore the start request. It seems that we need to wait a reasonable amount of time in the provider while restarting to start the service. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5342) Empty arrays does not match type of typed arrays
Title: Message Title Hailee Kenney assigned an issue to Unassigned Puppet / PUP-5342 Empty arrays does not match type of typed arrays Change By: Hailee Kenney Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5342) Empty arrays does not match type of typed arrays
Title: Message Title Hailee Kenney commented on PUP-5342 Re: Empty arrays does not match type of typed arrays When I test on 3d79fe2d1006a4b493169df233d84cbeea12ff05 (after the change), the empty array appears as an Array of Unit ❤ > be puppet apply -e 'notice(assert_type(String, []))' Error: Evaluation Error: Error while evaluating a Function Call, assert_type(): Expected type String does not match actual: Array[Unit] at line 1:8 on node hailees-mbp-2.corp.puppetlabs.net And when I test on d7fda9f1166110aab6e9f92f5db94cebcc41298a (before the change), the empty array appears as an Array of Undef: ❤ > be puppet apply -e 'notice(assert_type(String, []))' Error: Evaluation Error: Error while evaluating a Function Call, assert_type(): Expected type String does not match actual: Array[Undef] at line 1:8 on node hailees-mbp-2.corp.puppetlabs.net Add Comment
Jira (PUP-5398) Fix regression that reintroduced file watching for directory environments
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5398 Fix regression that reintroduced file watching for directory environments Change By: Eric Thompson QA Risk Assessment Reason: unlimited environment_timeout ineffective QA Highest Test Level: Acceptance QA Risk Probability Reason: perhaps low in 3.x but higher in 4.x QA Risk Assessment: Medium QA Risk Probability: Medium QA Risk Severity: Medium QA Highest Test Level Reason: regressions and multiple code-paths QA Status: Reviewed Add Comment
Jira (PUP-5398) Fix regression that reintroduced file watching for directory environments
Title: Message Title
Eric Thompson commented on PUP-5398
Re: Fix regression that reintroduced file watching for directory environments
validated in 3.x at SHA: b628b07 on rhel7 with:
[root@e1oyf1ywgsa1fjh manifests]# puppet agent -t
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Caching catalog for e1oyf1ywgsa1fjh.delivery.puppetlabs.net
Info: Applying configuration version '1445556697'
Notice: production
Notice: /Stage[main]/Main/Notify[production]/message: defined 'message' as 'production'
Notice: Finished catalog run in 0.02 seconds
[root@e1oyf1ywgsa1fjh manifests]# cat /etc/puppet/environments/production/manifests/site.pp
notify{'production':}
Jira (PUP-5387) AIX service provider returns before service operations are complete
Title: Message Title
William Hopper commented on PUP-5387
Re: AIX service provider returns before service operations are complete
This one's a bit odd, and it doesn't seem to happen all the time, It seems that the best way to reproduce is:
[0] [AIX] root@pe-aix-61-agent:~ # puppet apply -e "service { 'puppet': ensure => running }"
[0] [AIX] root@pe-aix-61-agent:~ # puppet apply refresh_manifest.pp --debug --verbose
...
Info: /Stage[main]/Main/Notify[refreshing]: Scheduling refresh of Service[puppet]
Debug: /Stage[main]/Main/Notify[refreshing]: The container Class[Main] will propagate my refresh event
Debug: Executing: '/usr/bin/lssrc -s puppet'
Debug: Service puppet is active
Debug: Executing: '/usr/bin/lssrc -s puppet'
Debug: Service puppet is active
Jira (PUP-5359) scheduled_task won't work with schedule monthly
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5359 scheduled_task won't work with schedule monthly Change By: Ethan Brown Sprint: Windows 2015-12-02 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5359) scheduled_task won't work with schedule monthly
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5359 scheduled_task won't work with schedule monthly Change By: Ethan Brown Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-3231) Specifying --tags doesn't cause suitability check to be skipped for skipped resources
Title: Message Title Kylo Ginsberg commented on PUP-3231 Re: Specifying --tags doesn't cause suitability check to be skipped for skipped resources Note that this issue is not related to hpux at all. That was simply a convenient example to use because it is a not suitable provider on any system we typically test against. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5359) scheduled_task won't work with schedule monthly
Title: Message Title
Ethan Brown commented on PUP-5359
Re: scheduled_task won't work with schedule monthly
Hi Anthony Scudese - thanks for the report.
It appears that there is a problem with using the value 'last'. I suggest that you use the value 28 instead of 'last' as a temporary workaround for now. The task scheduler GUI allows me to specify last, so we'll have to do a little diagnostic work to figure out where the failure is happening.
The following task definition should work ok.
scheduled_task { 'Adobe Remote Update Manager':
ensure=> present,
command => $adoberum::command_source,
enabled => true,
trigger => {schedule => monthly, on => [1,3,17,28], start_time => '08:00', months => [1, 3, 5]},
}
Add Comment
Jira (PUP-5398) Fix regression that reintroduced file watching for directory environments
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-5398 Fix regression that reintroduced file watching for directory environments Change By: Eric Thompson Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Felix Frank commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Sounds like a good plan. I think this will even satisfy John Bollinger's request for consistent lookup behavior. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2096) hitting /pdb/foo gives a confusing error
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2096 hitting /pdb/foo gives a confusing error Change By: Russell Mull Fix Version/s: PDB 3.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Also agree to that we do not really need a puppet setting. If the lookupoptions key is there - the feature is on. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Henrik Lindberg Fix Version/s: PUP 4.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Thomas Hallgren also brought up (in a conversation we had) that it is confusing if the lookup options are not also the default lookup options when performing a lookup using the lookup function, and I agreed to that. For the hiera_xxx functions it may become problematic, since they are themselves already specifying one aspect of the lookup (the type), and there is a global parameter in hiera.yaml controlling how hash lookup is expected to work. As an example, should a hiera (priority) lookup perform a merge if the lookup options in hiera data specifies this, or is the call to hiera (priority) the way the user specifies that it should not do a merge (no matter what the default is)? It was for these reasons I originally said that the lookup options should only have effect for automatic data binding. Opinions? Is it ok if we leave the hiera_xxx functions as they are since they have the style that implies that the user knows the data configuration? Instead users should use the lookup function where the lookup options from data files becomes the default if not given as an argument to lookup. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2070) Extended terminus command submission
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-2070 Extended terminus command submission Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2070) Extended terminus command submission
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2070 Extended terminus command submission Change By: Russell Mull Fix Version/s: PDB 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1964) applied-migrations swallows exceptions and returns an empty set
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1964 applied-migrations swallows exceptions and returns an empty set Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5262) Solaris (10) service provider returns before service refresh is complete
Title: Message Title
William Hopper commented on PUP-5262
Re: Solaris (10) service provider returns before service refresh is complete
After taking a first pass at digging into this, it's hard to say if the SMF provider is doing the right thing or not.
First, some background on SMF service states. Every service on the system has a state and an nstate. State represents the current state of the service, while nstate represents the next state and is only used when a service is transitioning between states. For example, while puppet is happily running, we see:
-bash-3.2# svcs -H -o state,nstate puppet
online - # <== the '-' indicates that there is no state transition happening.
The SMF provider uses both the state and nstate to determine the "status" of the service. The following is the block of logic in question:
84 # get the current state and the next state, and if the next
85 # state is set (i.e. not "-") use it for state comparison
86 states = svcs("-H", "-o", "state,nstate", @resource[:name]).chomp.split
87 state = states[1] == "-" ? states[0] : states[1]
...
Jira (PDB-2097) Disable dujour checkins for Puppet Server during CI runs
Title: Message Title Andrew Roetker commented on PDB-2097 Re: Disable dujour checkins for Puppet Server during CI runs Fyi this will require us to break up the step 20_install_puppet from our pre_suite so that we can sandwich the step 60_munge_etc_hosts_for_dujour in between when we install puppetserver and start puppetserver. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4488) Support global data lookup using data providers
Title: Message Title
Henrik Lindberg commented on PUP-4488
Re: Support global data lookup using data providers
The current data binding for hiera is implemented as a terminus. We could do one of the following:
Add a new terminus (say 'hiera4') that uses the 'data in modules' implementation
Modify the existing 'hiera' terminus to either use the existing hiera implementation or the new based on the version key in hiera.yaml
In both cases, the hiera_config setting should be used to get the hiera.conf file specifying the global configuration.
Users should note that when they switch to using `hiera4`, the calls to the `hiera_xxx` functions will not work (and users should switch to instead call `lookup`, and the current hiera will not be loaded. If we continue to support both hiera 3 and 4 in parallel it will probably be very confusing as hiera_xxx calls would work against a separate hierarchy from automatic data binding. We can however relay the hiera_xxx calls to lookup if users are using the hiera4 data binding terminus (or we need yet another flag to support that). Using relay also gives us the opportunity to add deprecation warnings ("hiera_xxx calls are deprecated in favor of the lookup function").
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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.googl
Jira (PUP-5382) Compiler raises a cryptic error when no node mappings are defined on an application declaration
Title: Message Title Henrik Lindberg commented on PUP-5382 Re: Compiler raises a cryptic error when no node mappings are defined on an application declaration Merged to master: 3d79fe2 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5382) Compiler raises a cryptic error when no node mappings are defined on an application declaration
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-5382 Compiler raises a cryptic error when no node mappings are defined on an application declaration Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5382) Compiler raises a cryptic error when no node mappings are defined on an application declaration
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5382 Compiler raises a cryptic error when no node mappings are defined on an application declaration Change By: Henrik Lindberg Sprint: Language Triage 2015-10-28 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5382) Compiler raises a cryptic error when no node mappings are defined on an application declaration
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5382 Compiler raises a cryptic error when no node mappings are defined on an application declaration Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5060) Add support for --facts in 'puppet lookup' command
Title: Message Title Henrik Lindberg commented on PUP-5060 Re: Add support for --facts in 'puppet lookup' command Merged to master at: 029b8c4 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5081) CapabilityFinder needs to look up capabilities by code_id
Title: Message Title John Duarte assigned an issue to Eric Thompson Puppet / PUP-5081 CapabilityFinder needs to look up capabilities by code_id Change By: John Duarte Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5391) nim provider fails on AIX
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5391 nim provider fails on AIX Change By: John Duarte Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5271) Windows user resource should not manage password unless specified
Title: Message Title Rob Reynolds assigned an issue to Ryan Gard Puppet / PUP-5271 Windows user resource should not manage password unless specified Change By: Rob Reynolds Assignee: qa Ryan Gard Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5134) Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5134 Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet Change By: Josh Cooper Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5134) Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet
Title: Message Title Josh Cooper commented on PUP-5134 Re: Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet The work for Solaris 11 i386 is complete, and we decided not complete the work for Solaris 11 SPARC for 1.2.7, instead manually preparing the box prior to running acceptance. This change will go into PUP 4.3.0 for puppet-agent 1.3.0, so I'll update the relationship and remove the impediment flag. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5271) Windows user resource should not manage password unless specified
Title: Message Title
Josh Cooper commented on PUP-5271
Re: Windows user resource should not manage password unless specified
This passed puppet#3.x, puppet-agent# {stable,master}
CI
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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-5271) Windows user resource should not manage password unless specified
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-5271 Windows user resource should not manage password unless specified Change By: Josh Cooper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5342) Empty arrays does not match type of typed arrays
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-5342 Empty arrays does not match type of typed arrays Change By: Hailee Kenney Assignee: qa Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2098) first-cut TK status integration
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2098 first-cut TK status integration Change By: Wyatt Alt This tracks the work required for Burnside status features. Exact requirements pending on discussion in this document:https://docs.google.com/document/d/1I7kmb-RopMysvgMPzQGPZ3e1u17rWC72V_YzJdphJ2k/edit Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2098) first-cut TK status integration
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2098 first-cut TK status integration Issue Type: Improvement Assignee: Unassigned Created: 2015/10/22 11:32 AM Fix Versions: PDB 4.0.0 Priority: Normal Reporter: Wyatt Alt Exact requirements pending on discussion in this document: https://docs.google.com/document/d/1I7kmb-RopMysvgMPzQGPZ3e1u17rWC72V_YzJdphJ2k/edit Add Comment This message
Jira (PUP-5262) Solaris (10) service provider returns before service refresh is complete
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-5262 Solaris (10) service provider returns before service refresh is complete Change By: William Hopper Assignee: William Hopper Scope Change Category: Adopted Scope Change Reason: Continuing work on potentially high-risk Solaris issues Sprint: Client 2015- 11 10 - 11 28 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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.
Jira (PUP-4547) Ruby and irb on Windows can't find 'puppet', 'facter', etc.
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4547 Ruby and irb on Windows can't find 'puppet', 'facter', etc. Change By: Ethan Brown Sprint: Windows 2015- 12 11 - 02 18 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4547) Ruby and irb on Windows can't find 'puppet', 'facter', etc.
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4547 Ruby and irb on Windows can't find 'puppet', 'facter', etc. Change By: Ethan Brown Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4547) Ruby and irb on Windows can't find 'puppet', 'facter', etc.
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4547 Ruby and irb on Windows can't find 'puppet', 'facter', etc. Change By: Ethan Brown Sprint: Windows 2015-12-02 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1231) Remove blkid cache write for partitions fact
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1231 Remove blkid cache write for partitions fact Change By: Kylo Ginsberg Summary: Remove blkid cache write for paritions partitions fact Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2097) Disable dujour checkins for Puppet Server during CI runs
Title: Message Title Christopher Price commented on PDB-2097 Re: Disable dujour checkins for Puppet Server during CI runs It would definitely need to happen before Puppet Server was started. We haven't 100% confirmed that the seemingly inflated Puppet Server numbers on dujour are coming from this, but it's the best guess we have at the moment, and if Puppet Server is being started before that pre-suite step then it would seem likely that this was what was going on. Thanks for looking into it! Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4917) puppet resource package does not display installs that use QuietDisplayName
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-4917 puppet resource package does not display installs that use QuietDisplayName Change By: Rob Reynolds Assignee: Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5346) Investigate puppet_mcollective_service_management acceptance test failure on AIX and Solaris 11
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5346 Investigate puppet_mcollective_service_management acceptance test failure on AIX and Solaris 11 Change By: Kylo Ginsberg Fix Version/s: PUP 4.2.3 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5346) Investigate puppet_mcollective_service_management acceptance test failure on AIX and Solaris 11
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5346 Investigate puppet_mcollective_service_management acceptance test failure on AIX and Solaris 11 Change By: Kylo Ginsberg Issue Type: Bug Task Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1238) Facter should respect long-form hostnames to populate hostname, domain, and FQDN
Title: Message Title John Duarte commented on FACT-1238 Re: Facter should respect long-form hostnames to populate hostname, domain, and FQDN Kenn Hussey, I have pinged Branan Riley, William Hopper, Josh Cooper, Kylo Ginsberg, and Michael Smith on this. Maybe Peter Huene should take a look at it as well. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1238) Facter should respect long-form hostnames to populate hostname, domain, and FQDN
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1238 Facter should respect long-form hostnames to populate hostname, domain, and FQDN Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5134) Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-5134 Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2097) Disable dujour checkins for Puppet Server during CI runs
Title: Message Title Kenneth Barber commented on PDB-2097 Re: Disable dujour checkins for Puppet Server during CI runs We already have this: https://github.com/puppetlabs/puppetdb/blob/master/acceptance/setup/pre_suite/60_munge_etc_hosts_for_dujour.rb Perhaps we need to move it earlier? Looks like its after we install Puppet. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2097) Disable dujour checkins for Puppet Server during CI runs
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2097 Disable dujour checkins for Puppet Server during CI runs Change By: Kenneth Barber Sprint: PuppetDB 2015-11-18 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2097) Disable dujour checkins for Puppet Server during CI runs
Title: Message Title Christopher Price created an issue PuppetDB / PDB-2097 Disable dujour checkins for Puppet Server during CI runs Issue Type: Bug Assignee: Unassigned Created: 2015/10/22 10:42 AM Priority: Major Reporter: Christopher Price Analyzing the dujour data for Puppet Server, we are starting to suspect that it is being artificially inflated by checkins from PuppetDB CI tests in AWS. In various CI jobs we've solved this in the beaker pre-suites by either setting a bunk entry for the dujour hostname in /etc/hosts, or by configuring the TK dujour client with a bunk server hostname. I believe that other teams that are using Puppet Server in their CI already have something like this in their pre-suites, but it's less of an issue for the other projects anyway because their tests run on our internal hardware, meaning that the dujour checkins would all share a small number of remote IP addresses and those are easy to filter out if some accidentally slip through. It's a much bigger problem with PuppetDB since the CI jobs are running in AWS; we have no way of differentiating between "real" AWS checkins and PuppetDB CI checkins. Add Comment
Jira (PDB-2058) build from source instructions no longer valid for PDB 3+ on arch linux (if not in general)
Title: Message Title Kenneth Barber commented on PDB-2058 Re: build from source instructions no longer valid for PDB 3+ on arch linux (if not in general) Although for older jars, we could always push explicitly/manually, something to be mindful of. At least for the versions we've done releases for ... this would make the process backwards compatible with stuff we have in the wild in theory. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5406) Address race conditions when stopping puppet
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5406 Address race conditions when stopping puppet Issue Type: Bug Assignee: Unassigned Created: 2015/10/22 10:38 AM Priority: Normal Reporter: Kylo Ginsberg We've seen intermittent failures stopping puppet in acceptance. Per Matthaus Owens: pe-puppet has a stop function that looks like this: https://github.com/puppetlabs/pe-puppet/blob/3.8.x/ext/redhat/pe-puppet-client.init#L58-L90 foss has https://github.com/puppetlabs/puppet/blob/stable/ext/redhat/client.init#L52-L66 which just kills it and returns A similar approach should be in place for redhat/debian/solaris/aix.
Jira (PDB-2058) build from source instructions no longer valid for PDB 3+ on arch linux (if not in general)
Title: Message Title Kenneth Barber commented on PDB-2058 Re: build from source instructions no longer valid for PDB 3+ on arch linux (if not in general) I think this would be better done with ezbake released to clojars, after speaking to Christopher Price, Melissa Stone and Matthaus Owens - we think all we need is to change the publish location in ezbake's project.clj to be clojars instead of internal. We'd also need a release to make it live . Either way, I think this effort is worth doing before this work (probably as part of this ticket?) to make it easier to document the process. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1258) Exceptions thrown while resolving facts should be caught when running inside Ruby
Title: Message Title Michael Smith commented on FACT-1258 Re: Exceptions thrown while resolving facts should be caught when running inside Ruby I couldn't think of a way to wrap arbitrary function pointers in a try/catch, as the wrapper would have to be a member function and I don't think you can pass a non-static function as a function pointer. So every Ruby callback we register should wrap everything in a try/catch block. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5346) Investigate puppet_mcollective_service_management acceptance test failure on AIX and Solaris 11
Title: Message Title William Hopper updated an issue Puppet / PUP-5346 Investigate puppet_mcollective_service_management acceptance test failure on AIX and Solaris 11 Change By: William Hopper Comment: If we find that any changes to puppet are needed, we'll create a new ticket. This will be the initial investigation ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5380) Slow catalog run after updating to puppet 3.7.5
Title: Message Title John Duarte assigned an issue to Eric Thompson Puppet / PUP-5380 Slow catalog run after updating to puppet 3.7.5 Change By: John Duarte Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5346) Investigate puppet_mcollective_service_management acceptance test failure on AIX and Solaris 11
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-5346 Investigate puppet_mcollective_service_management acceptance test failure on AIX and Solaris 11 Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1963) Generated resources never receive dependency edges
Title: Message Title John Duarte assigned an issue to Tony Vu Puppet / PUP-1963 Generated resources never receive dependency edges Change By: John Duarte Assignee: qa Tony Vu Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1231) Remove blkid cache write for paritions fact
Title: Message Title John Duarte assigned an issue to Tony Vu Facter / FACT-1231 Remove blkid cache write for paritions fact Change By: John Duarte Assignee: John Duarte Tony Vu Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Thomas Hallgren Sprint: Language 2015- 11 10 - 11 28 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Thomas Hallgren Scope Change Category: Found Scope Change Reason: Deemed important for 4.3. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4917) puppet resource package does not display installs that use QuietDisplayName
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4917 puppet resource package does not display installs that use QuietDisplayName Change By: Ryan Gard QA Risk Assessment: Medium QA Status: Reviewed QA Contact: Eric Thompson Ryan Gard Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4426) group resource doesn't work on Windows when members is an array and noop is used
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4426 group resource doesn't work on Windows when members is an array and noop is used Change By: Ryan Gard QA Risk Assessment: Medium QA Status: Reviewed QA Contact: Eric Thompson Ryan Gard Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Rob Nelson commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings I like the idea of a lookupoptions key, that does seem more appealing than a global setting even if it's slightly more verbose. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Felix Frank commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings True. So yes, I guess we can go with this design instead. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings There can only be one lookupoptions object per file which means that all overrides would be declared in one place (per file). I think there's both pros and cons to that approach. Not sure one outweighs the other. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Felix Frank commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings My knowledge on YAML is failing me. Does the merge allow the same key to appear multiple times in one hash declaration? I.e. code lookupoptions: mysql_server: ... ... lookupoptions: apache: ... code If this is an issue, then that would be a usability minus compared to the lookupoptions::* keys. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5405) Puppet should enforce cross-platform standards for environment names
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-5405 Puppet should enforce cross-platform standards for environment names Issue Type: Bug Assignee: Unassigned Created: 2015/10/22 7:53 AM Priority: Normal Reporter: Nicholas Fagerlund We never specified real rules for how to identify an environment by its name, and just punted to the underlying filesystem's behavior. Unfortunately, we support platforms with different behavior; Windows and OS X are case insensitive when finding environments, and Linux is case sensitive. I posit that this is bad, and environments should behave the same way across all our platforms. My suggestion is that we go case-insensitive everywhere (and two environments with ambiguous names are an error), or else enforce all-lowercase names everywhere. Add Comment
Jira (PUP-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings That is nice. Needs to do a lookup of "lookupoptions" with a deep merge to avoid having to have central definition of all lookup options. But that is fine, far less expensive that looking up each lookupoption for each and every parameter. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-431) Get pre-suites working for Solaris 11 (SPARC, i386) for Hiera
Title: Message Title Josh Cooper commented on HI-431 Re: Get pre-suites working for Solaris 11 (SPARC, i386) for Hiera puppet-agent#master passed hiera acceptance, no verification needed, resolving. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1186) Get pre-suites working for Solaris 11 (SPARC, i386) for Facter
Title: Message Title Josh Cooper commented on FACT-1186 Re: Get pre-suites working for Solaris 11 (SPARC, i386) for Facter puppet-agent#master passed facter acceptance, no verification needed, resolving. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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.
