Bug 1022665

Summary:	Error: Could not retrieve catalog from remote server: integer 4294967294 too big to convert to `int'
Product:	[Fedora] Fedora	Reporter:	Orion Poplawski <orion>
Component:	puppet	Assignee:	Sam Kottler <skottler>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	20	CC:	fedora, jose.p.oliveira.oss, k.georgiou, mastahnke, mmagr, moses, ohadlevy, orion, skottler, tmz, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
URL:	https://projects.puppetlabs.com/issues/22955
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-23 20:36:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Orion Poplawski 2013-10-23 18:18:34 UTC

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 18:23:57 UTC

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 18:25:32 UTC

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 20:36:23 UTC

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.