Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-8158

puppetlabs-mysql: 100% CPU and memory leak on 4.7 during tests

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: mysql
    • Labels:
      None
    • Environment:

      MacOS, Docker Alpine, Ruby 2.3

    • Template:
      MODULES Bug Template
    • Epic Link:
    • Team:
      Modules
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Module Version: 6.0.0 and higher
      Puppet Version: 4.7
      OS Name/Version: MacOS (tests), Docker Alpine (tests)

      I'm not 100% sure if this is a bug in our module or in MySQL module version 6 and up.

      We're maintaining a [PowerDNS module for Puppet|https://github.com/sensson/puppet-powerdns] Our dependency management was falling a bit behind so I was updating our .fixtures.yml dependency list one by one running tests at each stage.

      As soon as I update puppetlabs/mysql to version 6 it doesn't compile anymore. CPU usage skyrockets to 100% and something is leaking memory.

      This only happens on Puppet 4.7. Puppet 4.10 is fine. I've tested this on both MacOS and a clean Ruby Docker image. Both show the same issue.

      Steps to reproduce:

      git clone https://github.com/sensson/puppet-powerdns.git
      cd puppet-powerdns
      Change .fixtures.yml and update MySQL to 6.0.0
      bundle install --path vendor/bundle
      bundle exec rake test

      Desired Behavior:

      A module that compiles on Puppet 4.7 with puppetlabs/mysql 6+.

      Actual Behavior:

      Ruby caught in a loop, eventually crashing the instance it's running on.

       

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            ju5t ju5t
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Zendesk Support