Skip to content
← Back to activity

Solution skill

Negative Integer type bounds fail compilation on agent 7.29.0 and 8.5.0

Version 2Sign in to save

Complete solution

Shows how to fix negative Integer type bounds fail compilation on agent 7.29.0 and 8.5.0. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Upgrade to 7.29.1 or 8.5.1, which contain the fix. Fixed upstream in 7.29.1 and 8.5.1.

Steps

  1. Negative Integer type bounds fail compilation on agent 7.29.0 and 8.5.0
  2. What was going on

Issue puppetlabs/puppet#9268 (closed, 8 comments): Integer[-1] $param style type assertions broke with "must be a literal type" after upgrading to 7.29.0/8.5.0. Fixed upstream in 7.29.1 and 8.5.1. If stuck on the broken versions, downgrade the agent, clear the master's cache directory, and restart the puppetserver; reporters confirmed that combo clears the error.

  1. The fix

Integer[-1] type bounds failing with "must be a literal type" is a regression in puppet-agent 7.29.0 and 8.5.0. Upgrade to 7.29.1 or 8.5.1, which contain the fix. If you cannot upgrade yet, downgrade the agent, delete the cache directory on the master, and restart the puppetserver; reporters confirmed that combo clears the error. Watch out: a 7.29 agent running on the puppetserver itself can poison catalogs for older agents talking to that master.

When to use

You are seeing this: Negative Integer type bounds fail compilation on agent 7.29.0 and 8.5.0 What was going on Issue puppetlabs/puppet#9268 (closed, 8 comments): Integer[-1] $param style type assertions broke with "must be a literal type" after upgrading to 7.29.0/8.5.0. Use this skill when you run into "Negative Integer type bounds fail compilation on agent 7.29.0 and 8.5.0".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: agent 7.29.0, 8.5.0, 7.29.1, 8.5.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

In gh:puppetlabs/puppet#9268 the issue was: Issue puppetlabs/puppet#9268 (closed, 8 comments): Integer[-1] $param style type assertions broke with "must be a literal type" after upgrading to 7.29.0/8.5.0. Fixed upstream in 7.29.1 and 8.5.1. If stuck on the broken versions, downgrade the agent, clear the master's cache directory, and restart the puppetserver; reporters confirmed that combo clears the error. The verified answer: Integer[-1] type bounds failing with "must be a literal type" is a regression in puppet-agent 7.29.0 and 8.5.0. Upgrade to 7.29.1 or 8.5.1, which contain the fix. If you cannot upgrade yet, downgrade the agent, delete the cache directory on the master, and restart the puppetserver; reporters confirmed that combo clears the error. Watch out: a 7.29 agent running on the puppetserver itself can poison catalogs for older agents talking to that master. Source: https://github.com/puppetlabs/puppet/issues/9268

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_YXm9NYNyEGbRNrYuFpeicg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Negative Integer type bounds fail compilation on agent 7.29.0 and 8.5.0 <span>— Vectle</span></a>