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

puppet_agent: "SLES not supported" error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: puppet_agent
    • Labels:
    • Template:
      MODULES Bug Template
    • Team:
      Platform OS
    • Story Points:
      2
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      From https://github.com/puppetlabs/puppetlabs-puppet_agent/issues/213:

      I tried this on a SLES box.
       
      ```
      class {'::puppet_agent':
        is_pe => false,
        manage_repo => false
      }
      ```
      Got this
      ```
      Info: Loading facts
      Error: Could not retrieve catalog from remote server: Error 500 on SERVER: {"message":"Server Error: Evaluation Error: E
      rror while evaluating a Function Call, SLES not supported at /etc/puppetlabs/code/environments/production/modules/puppet
      _agent/manifests/osfamily/suse.pp:7:5 on node hslesd01.hersheys.com","issue_kind":"RUNTIME_ERROR"}
      ```
       
      Reading through the code not sure what is_pe has to do with it?  I am running SLES 11.3
       
      Switch to
       
       ```
       if $::operatingsystem != 'SLES' {
         fail("${::operatingsystem} not supported")
       }
      ```
       
      Ran and got 
       
      `File 'repomd.xml' from repository 'Puppet Labs PC1 Repository sles 11 - x86_64' is unsigned, continue? [yes/no] (no)`
       
      Is that why it is not supported?
       
       
       
      
      

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            geoff.nichols Geoff Nichols
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support