integer out of range errors for fact_values

Bug #924105 reported by James Troup
This bug affects 5 people
Affects Status Importance Assigned to Milestone
puppet (Ubuntu)

Bug Description

Our puppet infrastructure recently ground to a halt as all nodes
errored out while trying to compile their catalogs with errors like

| err: INSERT INTO "fact_values" ("created_at", "updated_at", "value", "fact_name_id", "host_id") VALUES('2012-01-31 05:00:47.693719', '2012-01-31 05:00:47.693719', E'Tue Jan 31 05:00:47 +0000 2012', 29, 88) RETURNING "id"
| err: Could not retrieve catalog from remote server: Error 400 on SERVER: PGError: ERROR: integer out of range

We ended up working around this by shutting everything down and
running the following as postgres:

| ALTER SEQUENCE fact_values_id_seq RESTART; UPDATE fact_values SET id = DEFAULT;

Revision history for this message
James Troup (elmo) wrote :

This is filed upstream as -
I filed this bug in the hope of adding a bug watch but didn't realise
Launchpad didn't support 'watching' Redmine yet.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks for submitting this bug.

I'm marking it high priority and confirmed to mirror the upstream bug status.

Changed in puppet (Ubuntu):
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Nick Moffitt (nick-moffitt) wrote :

It happened again, just now.

Revision history for this message
Haw Loeung (hloeung) wrote :

This happened again today.

Revision history for this message
Alexander List (alexlist) wrote :

This happened again today.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.