Jira (PUP-6954) handle upstart acceptance test sometimes fails due to rabbitmq crash
Title: Message Title Josh Cooper commented on PUP-6954 Re: handle upstart acceptance test sometimes fails due to rabbitmq crash According to https://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2010-September/009161.html, the crash indicates another rabbitmq instance is running. The test installs rabbitmq, stop it and then starts it, so I'm thinking the error occurs because puppet's upstart provider doesn't reliably block until the service is stopped. 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 (PUP-7014) Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 20000
Title: Message Title Glenn Sarti commented on PUP-7014 Re: Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 2 Raised maint PR https://github.com/puppetlabs/ci-job-configs/pull/2170 so that MCO and Hiera emit spec unit test results. 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 (PUP-7014) Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 20000
Title: Message Title Glenn Sarti commented on PUP-7014 Re: Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 2 The puppet acceptance test don't get a full run until Step 7 of the puppet-agent pipeline. 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 (PUP-7014) Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 20000
Title: Message Title Glenn Sarti commented on PUP-7014 Re: Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 2 The puppet acceptance jobs run the ci:test:quick rake task which runs a dynamic set of tests. So my method of auditing was incorrect. 15 tests plus any tests that have been modified in the last 2 weeks https://github.com/puppetlabs/puppet/blob/master/acceptance/Rakefile#L277-L310 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 (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title Kevin Henner commented on PUP-3483 Re: Systemd provider doesn't scan for changed units Just to pile on here: from a learning and usability perspective, the "package, file, service" pattern should be as simple as possible, while exec resources are a more advanced topic with a list of warnings and caveats. Exec is the kind of hammer that makes a lot of things look like nails, so the more we can avoid pointing newer in its direction, the better. 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 (PUP-7014) Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 20000
Title: Message Title Glenn Sarti commented on PUP-7014 Re: Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 2 Actions The latest run of the puppet acceptance tests mysteriously didn't run 9 tests. Will investigate The following jobs do not output job XML for Jenkins to consume so we're missing out on build statistics etc. on them platform_marionette-collective_unit-ruby_*** platform_marionette-collective_intn-van-sys_*** platform_hiera_unit-ruby_*** 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 (PUP-7014) Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 20000
Title: Message Title Glenn Sarti commented on PUP-7014 Re: Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 2 I wrote some powershell to extract all of the test results from Jenkins and then process them to look for anomalies. The scripts are attached. To detect anomalies I just took the average of the Total number of tests for a job, and then checked that each single build was +/- 5% of that average. Results are below: Average tests for job platform_facter_intn-van-sys_master is 59 *** Job platform_hiera_unit-ruby_master has no job stats! Average tests for job platform_hiera_intn-van-sys_master is 9 *** Job platform_marionette-collective_unit-ruby_master has no job stats! *** Job platform_marionette-collective_intn-van-sys_master has no job stats! Average tests for job platform_puppet_unit-ruby-win_master is 21889.5 Average tests for job platform_puppet_unit-ruby_master is 22357.2619047619 Average tests for job platform_puppet_intn-van-sys_master is 32.8461538461538
Jira (PUP-7014) Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 20000
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-7014 Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 2 Change By: Glenn Sarti Attachment: ProcessCSV.ps1 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 (PUP-7014) Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 20000
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-7014 Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 2 Change By: Glenn Sarti Attachment: AuditPuppetAgentTests.ps1 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 (PUP-7014) Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 20000
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-7014 Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 2 Change By: Glenn Sarti Assignee: Glenn Sarti 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 (PUP-7014) Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 20000
Title: Message Title Glenn Sarti commented on PUP-7014 Re: Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 2 Unfortunately Build 52 has been purged so an RCA is going to be very difficult. 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 (PUP-7052) Calls to the ENC terminus should use a configurable timeout
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-7052 Calls to the ENC terminus should use a configurable timeout Change By: Charlie Sharpsteen Some ENC terminii, such as the REST terminus, are limited by a timeout due to the default configuration of the Puppet HTTP client. Others, such as the exec terminus, do not use a timeout when requesting node data from an external service. The lack of a uniform timeout means that a Puppet Master can be stalled indefinitely by a misbehaving external script data source depending on which terminus is in use . 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 (PUP-7052) Calls to the ENC terminus should use a configurable timeout
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-7052 Calls to the ENC terminus should use a configurable timeout Issue Type: Improvement Affects Versions: PUP 4.8.1 Assignee: Unassigned Components: Performance Created: 2016/12/29 9:35 AM Priority: Normal Reporter: Charlie Sharpsteen Some ENC terminii, such as the REST terminus, are limited by a timeout due to the default configuration of the Puppet HTTP client. Others, such as the exec terminus, do not use a timeout when requesting node data from an external service. The lack of a timeout means that a Puppet Master can be stalled indefinitely by a misbehaving external script. Add Comment
Jira (PUP-7051) Static catalog compiler uses Puppet master hostname for %H in fileserver config
Title: Message Title Matthias Hörmann created an issue Puppet / PUP-7051 Static catalog compiler uses Puppet master hostname for %H in fileserver config Issue Type: Bug Affects Versions: PUP 4.8.1 Assignee: Unassigned Created: 2016/12/29 4:14 AM Environment: Puppet Server 2.7.2 on Debian wheezy Priority: Normal Reporter: Matthias Hörmann We have fileserver mount points for files that should not be checked into version control along with the environment and module manifests, either because they are too large or shared between environments (e.g. a host should still use the same SSL certificates if it is moved from production to development environment). One of these mount points is defined like this [nodespecific]
Jira (PUP-7050) Puppet apply is not report when fails to compile the catalog
Title: Message Title Peiman created an issue Puppet / PUP-7050 Puppet apply is not report when fails to compile the catalog Issue Type: Bug Affects Versions: PUP 3.8.7, PUP 3.8.6 Assignee: Unassigned Attachments: Screen Shot 2016-12-29 at 1.22.02 AM.png, Screen Shot 2016-12-29 at 1.23.13 AM.png Created: 2016/12/29 1:23 AM Environment: Ubuntu 14.04 and 16.04 Priority: Normal Reporter: Peiman We are doing masterless puppet runs (puppet apply) and store reports and send the reports to Foreman server. Reports are generated just fine when it runs the catalog however it will not report if it fails to compile the catalog.
