Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-9015

Can't puppet describe vendored modules if provider requires helper code

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 6.0.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      Hide

      Should be possible to run puppet describe -l add see information about the mount type.

      Show
      Should be possible to run puppet describe -l add see information about the mount type.
    • Team:
      Coremunity
    • Sprint:
      Platform Core KANBAN
    • Release Notes:
      Not Needed
    • Release Notes Summary:
      Issue was introduced in the master branch and never released.
    • QA Risk Assessment:
      Needs Assessment

      Description

      If a vendored modules' provider includes helper code within the same module, then running puppet describe will fail, because the module's lib directory is not on the ruby $LOAD_PATH. For example, the mount provider calls

      require 'puppet/provider/mount'
      

      which is helper code in the same module, and results in:

      # puppet describe -l
      Error: Could not autoload puppet/provider/mount/parsed: cannot load such file -- puppet/provider/mount
      Error: Could not autoload puppet/type/mount: Could not autoload puppet/provider/mount/parsed: cannot load such file -- puppet/provider/mount
      Error: Could not run: Could not autoload puppet/type/mount: Could not autoload puppet/provider/mount/parsed: cannot load such file -- puppet/provider/mount
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              josh Josh Cooper
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support