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

puppetlabs-f5 virtualserver can't process a provider parameter

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: f5
    • Labels:
      None
    • Environment:

      puppetserver version: 2016.4.0.1006
      puppet version: 4.7.0
      RHEL 7.1
      F5 VE BigIP

    • CS Priority:
      Reviewed
    • QA Risk Assessment:
      Needs Assessment

      Description

      When following the documentation, particularly this part: https://forge.puppet.com/puppetlabs/f5/1.5.0/readme#step-one-classifying-your-servers

      running

      puppet device -v --user=root

      produces the following output:

      Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'provider' at /etc/puppetlabs/code/environments/<envname>/modules/profile/manifests/f5_device.pp:26 on F5_virtualserver[/Common/puppet_vs] at /etc/puppetlabs/code/environments/<envname>/modules/profile/manifests/f5_device.pp:26 on node bigip

      [...]

      Error: /Stage[main]/Profile::F5_device/F5_virtualserver[/Common/puppet_vs]: Could not evaluate: f5_virtualserver requires that a provider is declared. Available providers are: forwarding_ip, forwarding_layer_2, performance_http, performance_l4, reject, standard, stateless

      Nodes and pools are being created/enforced as expected. I'm using the example code from the documentation.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  hunter Hunter (Hunner) Haugen
                  Reporter:
                  dansparks Dan Sparks
                • Votes:
                  2 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support