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

No error context when a non-numeric index is used on a string

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • PUP 3.8.4, PUP 4.3.1
    • PUP 3.8.5, PUP 4.3.2
    • None
    • None
    • 1
    • Language 2015-12-16
    • Not Needed

    Description

      Having a non-capitalized resource type with a relationship Metaparameter resource will give non-descript errors during puppet runs and when using puppet apply.

      Manifest with correct metaparameter:

      class test {
      file {'test':
       ensure => present,
       require => Package['ehs']
       }
      }
      

      Manifest causing error:

      class test {
      file {'test':
       ensure => present,
       require => package['ehs']
       }
      }
      

      Puppet Run

      [root@pe-201522-master manifests]# puppet agent -t
      Info: Retrieving pluginfacts
      Info: Retrieving plugin
      Info: Loading facts
      Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: The value 'ehs' cannot be converted to Numeric. on node pe-201522-master.puppetdebug.vlan
      Warning: Not using cache on failed catalog
      Error: Could not retrieve catalog; skipping run
      

      Attachments

        Issue Links

          Activity

            People

              john.duarte John Duarte
              kaitlin Kaitlin Carter
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support