Bug 1022665 - Error: Could not retrieve catalog from remote server: integer 4294967294 too big to convert to `int'
Error: Could not retrieve catalog from remote server: integer 4294967294 too ...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: puppet (Show other bugs)
20
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Sam Kottler
Fedora Extras Quality Assurance
https://projects.puppetlabs.com/issue...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-23 14:18 EDT by Orion Poplawski
Modified: 2014-06-18 04:14 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-10-23 16:36:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Orion Poplawski 2013-10-23 14:18:34 EDT
Description of problem:

Running puppet 3.3.0 (or 3.3.1 from rawhide) on Fedora 20 with 3.3.1 server. Iā€™m getting:

Error: Could not retrieve catalog from remote server: integer 4294967294 too big to convert to int' Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Error: Could not save last run local report: integer 4294967294 too big to convert toint' Error: Could not send report: integer 4294967294 too big to convert to `int'
Comment 1 Orion Poplawski 2013-10-23 14:23:57 EDT
Okay, I think I found the trigger:

# ls -ld /var/lib/puppet/client_data/catalog/
drwxr-xr-x. 2 4294967294 4294967294 4096 Oct 23 12:21 /var/lib/puppet/client_data/catalog/
Comment 2 Sam Kottler 2013-10-23 14:25:32 EDT
Thanks for the bug report - I've watched the upstream bug and will either update or patch the package when it's fixed upstream.

Just out of curiosity, how many resources are in your catalog.
Comment 3 Orion Poplawski 2013-10-23 16:36:23 EDT
That's user ids, not directory size.  This is an artifact of problems occuring during my restore from backup procedure.  So I'm going to close this as NOTABUG, although a nicer error message might be nice.

Note You need to log in before you can comment on or make changes to this bug.