Jira (PDB-3222) stop testing multiple hosts/cell in PDB acceptance tests
Title: Message Title Wayne Warren commented on PDB-3222 Re: stop testing multiple hosts/cell in PDB acceptance tests Wyatt Alt this would be very helpful, yes... However I think converting the puppetdb pipeline to CI.Next directly from AWS, which we want to do anyway but keep getting slammed by infrastructure fires or the need to do important strategic work like working up estimates for our CI.Next mesos master needs, will allow y'all to begin using vmpooler templates even with PR testing. In CI.Next we pre-provision vmpooler nodes before the jenkins job that uses them actually leaves the queue and we use a more or less "capacity aware" resource allocator layer on top of vmpooler to do this so even relatively high-cadence pipelines like puppetdb's will not be able to "tip" vmpooler over...instead, jobs will sit in the queue waiting for vmpooler capacity to free up before being allowed to run. We already have work ticketed to do this migration; see QENG-4282 and QENG-4303 Because this is a busy PTO time of year and we have challenging WIP, it's hard to predicted exactly when we'll get to this work. For an idea of the magnitude of remaining CI.Next migration work done/notdone and how we've mapped it out, please see http://grafana.ops.puppetlabs.net/dashboard/db/cinext-jira-graph-and-progress Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2254) docs changes (on stable at least) provoke an acceptance test run
Title: Message Title Wayne Warren commented on PDB-2254 Re: docs changes (on stable at least) provoke an acceptance test run Susan McNerney I'm fairly certain that as long as we are using github pull request triggers it won't be possible to filter out doc changes. This isn't a bug, this is a limitation of the Jenkins plugin that we would have to work around in some other way--probably 2-3 story points worth of effort for a QE sprint. James Wagner, do you think this is something we have the resources for? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2254) docs changes (on stable at least) provoke an acceptance test run
Title: Message Title Wayne Warren commented on PDB-2254 Re: docs changes (on stable at least) provoke an acceptance test run Wyatt Alt ah, I was assuming this ticket was about a triger of the on-merge pipeline. I don't think it's possilbe to filter github pull request triggers on files changed the same way as can be done for the on-merge polling trigger. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2254) docs changes (on stable at least) provoke an acceptance test run
Title: Message Title Wayne Warren commented on PDB-2254 Re: docs changes (on stable at least) provoke an acceptance test run There is no link to a build triggered by merge of the linked PR, nor is there a git polling log from the job in the ticket description. These things would be very helpful when investigating further. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-7) investigate moving puppetdb acceptance testing to use vsphere
Title: Message Title Wayne Warren commented on PDB-7 Re: investigate moving puppetdb acceptance testing to use vsphere Andrew Roetker Yeah we can close this, the investigatory work has already been done. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1814) PuppetDB automated testing should use vmpooler
Title: Message Title Wayne Warren created an issue PuppetDB / PDB-1814 PuppetDB automated testing should use vmpooler Issue Type: Bug Assignee: Unassigned Components: PE, Platform Created: 2015/07/17 5:24 PM Fix Versions: PDB 3.0.x Priority: Normal Reporter: Wayne Warren This ticket is intended to provide the PuppetDB team a way to track getting their acceptance tests to use vmpooler. Add Comment
Jira (PUP-3511) Refactor Application.run() for external reuse
Title: Message Title Wayne Warren commented on PUP-3511 Re: Refactor Application.run() for external reuse Kevin Corcoran Christopher Price This won't hit puppet-server CI until the submodule is updated, should we leave this ticket in Ready for CI until then? Or should I simply verify that this commit has made it into the MRI puppet FOSS pipeline? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3512) Add deprecation warning for old profiler API in Puppet
Title: Message Title Wayne Warren commented on PUP-3512 Re: Add deprecation warning for old profiler API in Puppet Christopher Price Preben Ingvaldsen This won't hit puppet-server CI until the submodule is updated, do you want to leave it in Ready for CI until then? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3593) Address SSL cleanup and puppetserver restart issues in acceptance tests.
Title: Message Title Wayne Warren created an issue Puppet / PUP-3593 Address SSL cleanup and puppetserver restart issues in acceptance tests. Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Unassigned Created: 30/Oct/14 10:48 AM Fix Versions: PUP 3.7.3 Priority: Normal Reporter: Wayne Warren Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3593) Address SSL cleanup and puppetserver restart issues in acceptance tests.
Title: Message Title Wayne Warren updated an issue Puppet / PUP-3593 Address SSL cleanup and puppetserver restart issues in acceptance tests. Change By: Wayne Warren Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Wayne Warren commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. Christopher Price No, I haven't heard about this. Add Comment Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-3459) reports directory created by first puppet agent/apply run, should be created by OS package
Title: Message Title Wayne Warren commented on an issue Re: reports directory created by first puppet agent/apply run, should be created by OS package Josh Cooper that was just a workaround for puppet-server. I am going to change the title of this ticket to reflect discussion in that PR where Matthaus Owens suggested that reportsdir have group write permissions and setgid. group write permissions means that the puppet group would have write permissions on reportsdir, setgid on the reportsdir directory will ensure that the group permissions are inherited by subdirectories So even if root creates a subdirectory, the puppet user (having its primary group as the puppet group) will also be able to write to it. Let me know if any further clarification is necessary. Add Comment Puppet / PUP-3459 reports directory created by first puppet agent/apply run, should be created by OS package When running puppet apply as root during acceptance/integration test pre_suite in order to stub a host in /etc/hosts, a reports directory directory is created as the root user which leads to permissions errors during subsequent runs of puppet as the puppet user. This is a directory that we should definitely not be creating on a programmatic basis. ...
Jira (PUP-3459) reports directory should have group write permissions and be setgid
Title: Message Title Wayne Warren updated an issue Puppet / PUP-3459 reports directory should have group write permissions and be setgid Change By: Wayne Warren Summary: reportsdirectory createdbyfirstpuppetagent/applyrun, should havegroupwritepermissionsand be createdbyOSpackage setgid Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-3459) reports directory should have group write permissions and be setgid
Title: Message Title Wayne Warren updated an issue Puppet / PUP-3459 reports directory should have group write permissions and be setgid Change By: Wayne Warren Whenrunningpuppetapplyasrootduring puppet-server acceptance/integrationtestpre_suite ( inordertostubahostin/etc/hosts ) ,areports subdirectory directory directory forthemasterhost iscreatedastherootuserwhichleadstopermissionserrorsduringsubsequentrunsofpuppetasthepuppetuser. This Suggestedfix is adirectorythatweshoulddefinitelynotbecreating to*setgroupwritepermission on aprogrammaticbasis.Ifwemustdo reportsdir*setgidonreportsdir so thenmoredetailedthoughtshouldgointodirectoryownershipand subdirectoriesinheritgroup permissions .Inthepastwehaveaddressedsimilarproblemswithotherdirectoriesbycreatingthemduringpackageinstallationwhichseemslikeagoodapproachtome. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-3459) reports directory created by first puppet agent/apply run, should be created by OS package
Title: Message Title Wayne Warren created an issue Puppet / PUP-3459 reports directory created by first puppet agent/apply run, should be created by OS package Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Kylo Ginsberg Components: Client Created: 14/Oct/14 9:41 AM Priority: Normal Reporter: Wayne Warren When running puppet apply as root during acceptance/integration test pre_suite in order to stub a host in /etc/hosts, a reports directory directory is created as the root user which leads to permissions errors during subsequent runs of puppet as the puppet user. This is a directory that we should definitely not be creating on a programmatic basis. If we must do so then more detailed thought should go into directory ownership and permissions. In the past we have addressed similar problems with other directories by creating them during package installation which seems like a good approach to me.
Jira (PUP-3175) Intermittent failure for node/check_woy_cache_works testcase
Title: Message Title Wayne Warren updated an issue Puppet / PUP-3175 Intermittent failure for node/check_woy_cache_works testcase Change By: Wayne Warren Fix Version/s: 3.7.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1680) incorrect header check using Ruby 2
Title: Message Title Wayne Warren updated an issue Puppet / PUP-1680 incorrect header check using Ruby 2 Change By: Wayne Warren Affects Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1680) incorrect header check using Ruby 2
Title: Message Title Wayne Warren updated an issue Puppet / PUP-1680 incorrect header check using Ruby 2 Change By: Wayne Warren Fix Version/s: 3.7.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1680) incorrect header check using Ruby 2
Title: Message Title Wayne Warren updated an issue Puppet / PUP-1680 incorrect header check using Ruby 2 Change By: Wayne Warren Affects Version/s: 3.7.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-3173) Remove 'jvm-puppet' references in Puppet acceptance code
Title: Message Title Wayne Warren updated an issue Puppet / PUP-3173 Remove 'jvm-puppet' references in Puppet acceptance code Change By: Wayne Warren Labels: puppet-server Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-3173) Remove 'jvm-puppet' references in Puppet acceptance code
Title: Message Title Wayne Warren updated an issue Puppet / PUP-3173 Remove 'jvm-puppet' references in Puppet acceptance code Change By: Wayne Warren Affects Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-3173) Remove 'jvm-puppet' references in Puppet acceptance code
Title: Message Title Wayne Warren created an issue Puppet / PUP-3173 Remove 'jvm-puppet' references in Puppet acceptance code Issue Type: Task Assignee: Unassigned Created: 02/Sep/14 2:26 PM Priority: Normal Reporter: Wayne Warren The is_jvm_puppet flag was set in puppet-server acceptance tests to indicate that acceptance tests were being run against jvm puppet. Now that we have made a name change in preparation for the OSS release we need to change this flag to is_puppetserver for consistency's sake. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3175) Intermittent failure for node/check_woy_cache_works testcase
Title: Message Title Wayne Warren created an issue Puppet / PUP-3175 Intermittent failure for node/check_woy_cache_works testcase Issue Type: Bug Affects Versions: 3.7.0 Assignee: Unassigned Created: 02/Sep/14 5:00 PM Priority: Normal Reporter: Wayne Warren While running tests against `puppet-server` we have encountered intermittent failures on this test case that we have not been able to reproduce outside of CI. This bug is primarily about isolating this testcase from other tests by pointing it to a temporary yamldir to avoid node yaml files being tainted by previously run tests and to prevent subsequent tests from overwriting the node yaml file created by this test. Add Comment
Jira (PUP-3165) Puppet 'apply' creates /var/lib/puppet/reports/node-name unreadable by master
Title: Message Title
Wayne Warren created an issue
Puppet / PUP-3165
Puppet 'apply' creates /var/lib/puppet/reports/node-name unreadable by master
Issue Type:
Bug
Affects Versions:
3.7.0
Assignee:
Kylo Ginsberg
Components:
Client
Created:
29/Aug/14 5:19 PM
Environment:
any
Priority:
Major
Reporter:
Wayne Warren
To reproduce, install puppet on master SUT.
manifest = %Q[
Exec { path = /usr/bin:/bin }
node default {
notify { false: }
}
node a_different_node_name {
notify { notify #{success_message}: }
}
]
on master, puppet_apply(--verbose --node_name_value a_different_node_name), :stdin = manifest
on master, ls -l /var/lib/puppet/reports
This assumes that Beaker 1.17.6 is being used. Beaker 1.17.6 by default runs all SUT commands as root, so the puppet apply here is being run as root. This leads to the creation of a
Jira (PUP-3165) Puppet 'apply' creates /var/lib/puppet/reports/node-name/ unwritable by master
Title: Message Title Wayne Warren updated an issue Puppet / PUP-3165 Puppet 'apply' creates /var/lib/puppet/reports/node-name/ unwritable by master Change By: Wayne Warren Summary: Puppet'apply'creates/var/lib/puppet/reports/node-name unreadable /unwritable bymaster Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-3165) Puppet 'apply' creates /var/lib/puppet/reports/node-name/ unwritable by master
Title: Message Title
Wayne Warren commented on an issue
Re: Puppet 'apply' creates /var/lib/puppet/reports/node-name/ unwritable by master
Kylo Ginsberg definitely related, but whereas PUP-3163 deals with a directory that can be known about at install time (/var/lib/puppet/reports/), this ticket deals with directories that cannot be known about until puppet is run either as master with an agent running against it or as the repro case in the description mentions, as puppet apply run on the master before the master has the opportunity to create the directory.
I think the fixes for PUP-3163 and this bug are fundamentally different--I understand the former as a packaging bug and this as a behavior bug in the 'puppet apply' code path.
Add Comment
Puppet / PUP-3165
Puppet 'apply' creates /var/lib/puppet/reports/node-name/ unwritable by master
To reproduce, install puppet on master SUT. {code} manifest = %Q[ Exec { path = /usr/bin:/bin } node default { notify { false: } } node a_different_node_name { notify { notify #{success_message}: } } ] on master, puppet_apply(--verbose --node_name_value a_different_node_name), :stdin = manifest on master, l...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3035) Debian package does not create /var/run/puppet dir during install
Title: Message Title Wayne Warren created an issue Puppet / PUP-3035 Debian package does not create /var/run/puppet dir during install Issue Type: Bug Assignee: Unassigned Created: 07/Aug/14 2:37 PM Priority: Critical Reporter: Wayne Warren It looks like `/var/run/puppet` has typically been created during by the debian init script if it didn't exist already: https://github.com/puppetlabs/puppet/blob/master/ext/debian/puppetmaster.init#L22 This should instead be handled by the `puppet-common.dirs` file in the `puppet-common` package. I say that it should be included in the `puppet-common` package because it is used by components other than the `puppetmaster` daemon (for example `jvm-puppet` which does not currently depend on `puppetmaster` being installed, just `puppet-common`) Add Comment
Jira (PUP-2999) Merge clay-davis branch of FOSS puppet into upstream repository.
Title: Message Title Wayne Warren moved an issue Puppet / PUP-2999 Merge clay-davis branch of FOSS puppet into upstream repository. Change By: Wayne Warren Component/s: JVMPuppetMaster Component/s: TestInfrastructure Affects Version/s: 3.4.0 Affects Version/s: 3.4.0 Workflow: PuppetEnterprise Platform Workflow Key: PE PUP - 4847 2999 Project: Puppet Enterprise[Internal] Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
