Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-1408

"integer <number> too big to convert to `int' at" with lookupvar

    Details

    • Template:
    • Acceptance Criteria:
      Hide

      N/a. See Erik Dasher's 8/15 comment.

      Show
      N/a. See Erik Dasher's 8/15 comment.
    • Team:
      Systems Engineering
    • Sub-team:
    • Story Points:
      3
    • Sprint:
      SE 2016-09-21, SE 2016-10-05
    • CS Priority:
      Reviewed
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      When a variable lookup is performed from Ruby code or an ERB template and the variable is not defined, catalog compilation should no longer periodically fail with an erroneous error message which looks similar to:

      "Puppet Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, integer 2181729414 too big to convert to `int` at <puppet file>"

      Instead, the lookup should return 'nil'.
      Show
      When a variable lookup is performed from Ruby code or an ERB template and the variable is not defined, catalog compilation should no longer periodically fail with an erroneous error message which looks similar to: "Puppet Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, integer 2181729414 too big to convert to `int` at <puppet file>" Instead, the lookup should return 'nil'.

      Description

      The lookupvar function started failing after some time without any reason with a error message "Puppet Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, integer 2181729414 too big to convert to `int' at <puppet file>"

      this occured on 2 puppetserver at the same time (were restarted at the same time) and also only occur if the name to look up does not exist.

      I found someone with the same problem in the irc logs of #puppet and there it couldn't be debugged, because a restart fixed it. I still have them running as I could workaround this problem and so they still can be used for debugging. (User: Spec, logs at https://botbot.me/freenode/puppet/2016-05-31/)

      Stacktrace from puppetserver log is attached. Interesting is that the number which couldn't be converted is increasing over time

      UPDATE


      This cause of this problem was found to be in JRuby - see link "JRuby issue 3980".

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  juergen_thomann Jürgen Thomann
                  QA Contact:
                  Erik Dasher
                • Votes:
                  5 Vote for this issue
                  Watchers:
                  21 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support