[PDB Tech] peeringdb sync error

[Greg Dendy]

Upgraded to 0.4.4 and now crashing out with: 

django.core.exceptions.ValidationError: {'net': [u'network instance with id 7 does not exist.’]}

This was a clean database, no existing tables.  Suggestions?



> On Aug 4, 2016, at 10:31 PM, LOOS Eric (BCS/CBU) <eric.loos at bics.com> wrote:
> 
> I have no issue, but since we are running into this so often, I believe we should raise it as a feature request to have a fix capability in the pdb_sync command.
> 
> --
> Eric Loos
> 
> 
> 
> 
> -----Original Message-----
> From: Pdb-tech [mailto:pdb-tech-bounces at lists.peeringdb.com] On Behalf Of Greg Dendy
> Sent: Thursday 4 August 2016 22:02
> To: pdb-tech at lists.peeringdb.com
> Subject: Re: [PDB Tech] peeringdb sync error
> 
> Interestingly I’m seeing this error also, trying to sync to a new, clean database.  I am running version 0.4.3, so you’re probably going to tell me to upgrade ...
> 
> 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.
> Starting new HTTPS connection (1): www.peeringdb.com "GET /api/org?since=1470340115 HTTP/1.1" 200 None org last update 1470340115 0 changed data to be processed 0 Starting new HTTPS connection (1): www.peeringdb.com "GET /api/fac?since=1470340126 HTTP/1.1" 200 None fac last update 1470340126 0 changed data to be processed 0 Starting new HTTPS connection (1): www.peeringdb.com "GET /api/net?since=0 HTTP/1.1" 200 None net last update 0 6921 changed data to be processed 6921 Traceback (most recent call last):
>  File "/bin/peeringdb", line 11, in <module>
>    sys.exit(cli())
>  File "/usr/lib/python2.7/site-packages/click/core.py", line 716, in __call__
>    return self.main(*args, **kwargs)
>  File "/usr/lib/python2.7/site-packages/click/core.py", line 696, in main
>    rv = self.invoke(ctx)
>  File "/usr/lib/python2.7/site-packages/click/core.py", line 1060, in invoke
>    return _process_result(sub_ctx.command.invoke(sub_ctx))
>  File "/usr/lib/python2.7/site-packages/click/core.py", line 889, in invoke
>    return ctx.invoke(self.callback, **ctx.params)
>  File "/usr/lib/python2.7/site-packages/click/core.py", line 534, in invoke
>    return callback(*args, **kwargs)
>  File "/usr/lib/python2.7/site-packages/peeringdb/cli.py", line 125, in sync
>    db.sync()
>  File "/usr/lib/python2.7/site-packages/peeringdb/localdb.py", line 97, in sync
>    call_command('pdb_sync', interactive=False)
>  File "/usr/lib64/python2.7/site-packages/django/core/management/__init__.py", line 120, in call_command
>    return command.execute(*args, **defaults)
>  File "/usr/lib64/python2.7/site-packages/django/core/management/base.py", line 445, in execute
>    output = self.handle(*args, **options)
>  File "/usr/lib/python2.7/site-packages/django_peeringdb/management/commands/pdb_sync.py", line 85, in handle
>    self.sync(tables)
>  File "/usr/lib/python2.7/site-packages/django_peeringdb/management/commands/pdb_sync.py", line 92, in sync
>    self.update_db(cls, self.get_objs(cls))
>  File "/usr/lib/python2.7/site-packages/django_peeringdb/management/commands/pdb_sync.py", line 127, in update_db
>    sync.sync_obj(cls, row)
>  File "/usr/lib/python2.7/site-packages/django_peeringdb/sync.py", line 25, in sync_obj
>    obj.full_clean()
>  File "/usr/lib64/python2.7/site-packages/django/db/models/base.py", line 1171, in full_clean
>    raise ValidationError(errors)
> django.core.exceptions.ValidationError: {'org': [u'organization instance with id 8897 does not exist.’]}
> 
> 
> 
>> On Aug 3, 2016, at 12:10 AM, Matt Griswold <grizz at 20c.com> wrote:
>> 
>> * Paul Vlaar <pvlaar at afilias.info> [160802 18:48 +0200]:
>>>> 3. Does the problem persist if you do it on a fresh db (eg. after
>>>> running the drop_tables command, WARNING: this will delete all
>>>> existing data)
>>> 
>>> I am not ready to do this, as there's a live system feeding from this
>>> data. I suppose I may have to resort to that.
>> Is this MySQL?
>> _______________________________________________
>> Pdb-tech mailing list
>> Pdb-tech at lists.peeringdb.com
>> http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech
> 
> _______________________________________________
> Pdb-tech mailing list
> Pdb-tech at lists.peeringdb.com
> http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech
> 
> ________________________________
> 
> **** DISCLAIMER****
> http://www.bics.com/maildisclaimer/