[PDB Tech] peeringdb sync error

[Paul Vlaar]

This just keeps happening after a week or so of running "peeringdb sync"
successfully:

Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/org?since=1474062903 HTTP/1.1" 200 None
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/fac?since=1473922504 HTTP/1.1" 200 None
Operations to perform:
  Synchronize unmigrated apps: django_peeringdb
  Apply all migrations: admin, contenttypes, auth, sessions
Synchronizing apps without migrations:
  Creating tables...
    Running deferred SQL...
  Installing custom SQL...
Running migrations:
  No migrations to apply.
org last update 1474062903 0 changed
data to be processed 0
fac last update 1473922504 11 changed
data to be processed 11
Traceback (most recent call last):
  File "/usr/local/bin/peeringdb", line 9, in <module>
    load_entry_point('peeringdb==0.4.4.1', 'console_scripts', 'peeringdb')()
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 716,
in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 696,
in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line
1060, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 889,
in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 534,
in invoke
    return callback(*args, **kwargs)
  File
"/usr/local/lib/python2.7/dist-packages/peeringdb-0.4.4.1-py2.7.egg/peeringdb/cli.py",
line 167, in sync
    db.sync()
  File
"/usr/local/lib/python2.7/dist-packages/peeringdb-0.4.4.1-py2.7.egg/peeringdb/localdb.py",
line 140, in sync
    call_command('pdb_sync', interactive=False)
  File
"/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 120, in call_command
    return command.execute(*args, **defaults)
  File
"/usr/local/lib/python2.7/dist-packages/django/core/management/base.py",
line 445, in execute
    output = self.handle(*args, **options)
  File
"/usr/local/lib/python2.7/dist-packages/django_peeringdb/management/commands/pdb_sync.py",
line 85, in handle
    self.sync(tables)
  File
"/usr/local/lib/python2.7/dist-packages/django_peeringdb/management/commands/pdb_sync.py",
line 92, in sync
    self.update_db(cls, self.get_objs(cls))
  File
"/usr/local/lib/python2.7/dist-packages/django_peeringdb/management/commands/pdb_sync.py",
line 127, in update_db
    sync.sync_obj(cls, row)
  File
"/usr/local/lib/python2.7/dist-packages/django_peeringdb/sync.py", line
25, in sync_obj
    obj.full_clean()
  File
"/usr/local/lib/python2.7/dist-packages/django/db/models/base.py", line
1171, in full_clean
    raise ValidationError(errors)
django.core.exceptions.ValidationError: {'org': [u'organization instance
with id 15066 does not exist.']}

Should I just give up on the idea that we can keep doing incremental
updates, and run a full re-create every 12 hours or so?

Anyone else running into this problem?

	~paul