[PDB Announce] PeeringDB 2.21.0 release at 2020-07-01T0400Z

Wed Jul 1 08:09:58 PDT 2020

Hi Matt

I have upgraded  to Django-peeringdb 2.1, but it doesn't play well:

pdb at pdb2:~$ peeringdb sync
Traceback (most recent call last):
  File "/usr/local/bin/peeringdb", line 11, in <module>
    sys.exit(main())
  File "/home/pdb/.local/lib/python3.6/site-packages/peeringdb/cli.py", line 62, in main
    return handler(config=cfg, **vars(options))
  File "/home/pdb/.local/lib/python3.6/site-packages/peeringdb/commands.py", line 20, in _wrapped
    r = func(*a, **k)
  File "/home/pdb/.local/lib/python3.6/site-packages/peeringdb/commands.py", line 212, in handle
    client = Client(config, **kwargs)
  File "/home/pdb/.local/lib/python3.6/site-packages/peeringdb/client.py", line 44, in __init__
    peeringdb.initialize_backend(orm_name, **orm_config)
  File "/home/pdb/.local/lib/python3.6/site-packages/peeringdb/__init__.py", line 84, in initialize_backend
    B = supportmod.load_backend(**kwargs)
  File "/home/pdb/.local/lib/python3.6/site-packages/django_peeringdb/client_adaptor/load.py", line 46, in load_backend
    backend.Backend().migrate_database()
  File "/home/pdb/.local/lib/python3.6/site-packages/django_peeringdb/client_adaptor/backend.py", line 211, in migrate_database
    call_command("migrate", interactive=False, verbosity=verbosity)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/core/management/__init__.py", line 148, in call_command
    return command.execute(*args, **defaults)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/core/management/base.py", line 364, in execute
    output = self.handle(*args, **options)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/core/management/base.py", line 83, in wrapped
    res = handle_func(*args, **kwargs)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 234, in handle
    fake_initial=fake_initial,
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 117, in migrate
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
    state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 245, in apply_migration
    state = migration.apply(state, schema_editor)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/migrations/migration.py", line 124, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/migrations/operations/fields.py", line 249, in database_forwards
    schema_editor.alter_field(from_model, from_field, to_field)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 535, in alter_field
    old_db_params, new_db_params, strict)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 648, in _alter_field
    old_default = self.effective_default(old_field)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 233, in effective_default
    return field.get_db_prep_save(self._effective_default(field), self.connection)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/models/fields/related.py", line 937, in get_db_prep_save
    return self.target_field.get_db_prep_save(value, connection=connection)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/models/fields/__init__.py", line 789, in get_db_prep_save
    return self.get_db_prep_value(value, connection=connection, prepared=False)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/models/fields/__init__.py", line 958, in get_db_prep_value
    value = connection.ops.validate_autopk_value(value)
  File "/home/pdb/.local/lib/python3.6/site-packages/django/db/backends/mysql/operations.py", line 181, in validate_autopk_value
    raise ValueError('The database backend does not accept 0 as a '
ValueError: The database backend does not accept 0 as a value for AutoField.

pdb at pdb2:~$ pip3 freeze | grep peeringdb
django-peeringdb==2.1.0
peeringdb==1.0.0
pdb at pdb2:~$

Anything I am missing?

Best regards
Jan

________________________________
Von: Pdb-announce <pdb-announce-bounces at lists.peeringdb.com> im Auftrag von Matt Griswold <grizz at 20c.com>
Gesendet: Mittwoch, 1. Juli 2020 16:44
An: Stephen McManus <smcmanus at peeringdb.com>
Cc: pdb-announce at lists.peeringdb.com <pdb-announce at lists.peeringdb.com>
Betreff: Re: [PDB Announce] PeeringDB 2.21.0 release at 2020-07-01T0400Z

This has been released, let us know with any issues.

Please note, for doing a local sync with the python client, this
requires updating to django-peeringdb 2.1.

* Stephen McManus <smcmanus at peeringdb.com> [200624 16:24 -0400]:
> On Wednesday, July 1st at 0400Z, the current beta site will be
>   deployed unless any critical issues are found. Your help in
>   verifying that the upgrade went well by thoroughly testing
>   https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbeta.peeringdb.com%2F&data=02%7C01%7CJan.Boogman%40swisscom.com%7C4fa19103014a48754cb008d81dcd3dc3%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637292114623781761&sdata=5DW7w18DHEK0MKkH25xO5Bc0Jq4NC18ZfBkvJMQZFas%3D&reserved=0 would be greatly appreciated.
>
> Please review the changes and test against the beta site as necessary
>   to prepare for a production roll out. In addition, we will also
>   release the language packs that have reached maturity since our
>   last release.
>
> Preview of the release is at:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbeta.peeringdb.com%2F&data=02%7C01%7CJan.Boogman%40swisscom.com%7C4fa19103014a48754cb008d81dcd3dc3%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637292114623781761&sdata=5DW7w18DHEK0MKkH25xO5Bc0Jq4NC18ZfBkvJMQZFas%3D&reserved=0
>
> Release notes for v2.21.0 are here:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.peeringdb.com%2Frelease_notes%2F%23release-2210&data=02%7C01%7CJan.Boogman%40swisscom.com%7C4fa19103014a48754cb008d81dcd3dc3%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637292114623781761&sdata=uyr9afhTNwdiHTmgzc8b5COde2H2CffrPAG6wvIH98c%3D&reserved=0
>
> Highlights for this release include:
> * Two Factor Auth (2FA) support being added to better secure user
>   accounts
> * Several improvements for updates and delete actions, including
>   better error handling and hints to users
> * Some usability and UI improvements
>
> As always, let us know at support at peeringdb.com with any
>   comments/questions/concerns.
>
> Steve McManus on behalf of PeeringDB ProductCom
> _______________________________________________
> Pdb-announce mailing list
> Pdb-announce at lists.peeringdb.com
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.peeringdb.com%2Fcgi-bin%2Fmailman%2Flistinfo%2Fpdb-announce&data=02%7C01%7CJan.Boogman%40swisscom.com%7C4fa19103014a48754cb008d81dcd3dc3%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637292114623781761&sdata=iurTCB9sypoZZENT9cOdgowqIFMkjO4mT%2FqJVz7eV08%3D&reserved=0

_______________________________________________
Pdb-announce mailing list
Pdb-announce at lists.peeringdb.com
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.peeringdb.com%2Fcgi-bin%2Fmailman%2Flistinfo%2Fpdb-announce&data=02%7C01%7CJan.Boogman%40swisscom.com%7C4fa19103014a48754cb008d81dcd3dc3%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637292114623781761&sdata=iurTCB9sypoZZENT9cOdgowqIFMkjO4mT%2FqJVz7eV08%3D&reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.peeringdb.com/pipermail/pdb-announce/attachments/20200701/cfc56d4c/attachment-0001.htm>