Ok now I understand. Try the following:
cd /opt/openwisp2 source env/bin/activate ./manage.py shell_plus # the python/django shell will open Config.objects.filter(status='down').update(status='applied') This will fix the config status of your application. Seems that somebody did customize the config status to add "down", probably the customization was lost during the upgrade. However, to know if a device is reachable or not, I recommend using the monitoring module of OpenWISP <https://github.com/openwisp/openwisp-monitoring/>. Here you can see a demo: https://youtu.be/KN0xtej_L9I?t=3807 There's a thread in which I shared a sample playbook with the configuration needed to deploy it: https://groups.google.com/d/msg/openwisp/WuhK5rJJTX8/H0RIZoMKAgAJ I hope this helps. Federico On Wed, Oct 7, 2020 at 6:05 AM Ian Tait <[email protected]> wrote: > Hi, > > More output below, thanks. > > ansible-galaxy install --force openwisp.openwisp2 > - changing role openwisp.openwisp2 from 0.10.0 to unspecified > - downloading role 'openwisp2', owned by openwisp > - downloading role from > https://github.com/openwisp/ansible-openwisp2/archive/0.11.0.tar.gz > - extracting openwisp.openwisp2 to > /Users/administrator/.ansible/roles/openwisp.openwisp2 > - openwisp.openwisp2 (0.11.0) was installed successfully > - dependency Stouts.postfix is already installed, skipping. > administrator@gnc openwisp2-ansible-playbook % ansible-playbook -i hosts > playbook.yml -u administrator -k --become -K > > and the output from the 'migrate' section: > > TASK [openwisp.openwisp2 : migrate] > ********************************************************************************************************************************************************* > > fatal: [openwisp3.taitcorp.com]: FAILED! => {"changed": false, "cmd": > "./manage.py migrate --noinput", "msg": "stdout: Operations to perform:\n > Apply all migrations: account, admin, auth, config, connection, > contenttypes, geo, openwisp_users, pki, reversion, sessions, sites, > socialaccount, topology\nRunning migrations:\n Applying > openwisp_users.0008_update_admins_permissions... OK\n Applying > openwisp_users.0009_create_organization_owners... OK\n Applying > openwisp_users.0010_allow_admins_change_organization... OK\n Applying > openwisp_users.0011_user_first_name_150_max_length... OK\n Applying > topology.0011_fix_link_properties...\n:stderr: Traceback (most recent call > last):\n File \"./manage.py\", line 10, in <module>\n > execute_from_command_line(sys.argv)\n File > \"/opt/openwisp2/env/lib/python3.6/site-packages/django/core/management/__init__.py\", > line 401, in execute_from_command_line\n utility.execute()\n File > \"/opt/openwisp2/env/lib/python3.6/site-packages/django/core/management/__init__.py\", > line 395, in execute\n > self.fetch_command(subcommand).run_from_argv(self.argv)\n File > \"/opt/openwisp2/env/lib/python3.6/site-packages/django/core/management/base.py\", > line 328, in run_from_argv\n self.execute(*args, **cmd_options)\n File > \"/opt/openwisp2/env/lib/python3.6/site-packages/django/core/management/base.py\", > line 369, in execute\n output = self.handle(*args, **options)\n File > \"/opt/openwisp2/env/lib/python3.6/site-packages/django/core/management/base.py\", > line 83, in wrapped\n res = handle_func(*args, **kwargs)\n File > \"/opt/openwisp2/env/lib/python3.6/site-packages/django/core/management/commands/migrate.py\", > line 233, in handle\n fake_initial=fake_initial,\n File > \"/opt/openwisp2/env/lib/python3.6/site-packages/django/db/migrations/executor.py\", > line 117, in migrate\n state = self._migrate_all_forwards(state, plan, > full_plan, fake=fake, fake_initial=fake_initial)\n File > \"/opt/openwisp2/env/lib/python3.6/site-packages/django/db/migrations/executor.py\", > line 147, in _migrate_all_forwards\n state = self.apply_migration(state, > migration, fake=fake, fake_initial=fake_initial)\n File > \"/opt/openwisp2/env/lib/python3.6/site-packages/django/db/migrations/executor.py\", > line 245, in apply_migration\n state = migration.apply(state, > schema_editor)\n File > \"/opt/openwisp2/env/lib/python3.6/site-packages/django/db/migrations/migration.py\", > line 124, in apply\n operation.database_forwards(self.app_label, > schema_editor, old_state, project_state)\n File > \"/opt/openwisp2/env/lib/python3.6/site-packages/django/db/migrations/operations/special.py\", > line 190, in database_forwards\n self.code(from_state.apps, > schema_editor)\n File > \"/opt/openwisp2/env/lib/python3.6/site-packages/openwisp_network_topology/migrations/__init__.py\", > line 34, in fix_link_properties\n link.full_clean()\n File > \"/opt/openwisp2/env/lib/python3.6/site-packages/django/db/models/base.py\", > line 1222, in full_clean\n raise > ValidationError(errors)\ndjango.core.exceptions.ValidationError: {'status': > [\"Value 'down' is not a valid choice.\"]}\n", "path": > "/opt/openwisp2/env/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin", > "syspath": > ["/tmp/ansible_django_manage_payload_13scn343/ansible_django_manage_payload.zip", > "/usr/lib/python36.zip", "/usr/lib/python3.6", > "/usr/lib/python3.6/lib-dynload", "/usr/local/lib/python3.6/dist-packages", > "/usr/lib/python3/dist-packages"]} > > On 06/10/2020 17:24 Federico Capoano <[email protected]> wrote: > > > Dear Ian, > > 0.10 -> 0.11, which module is that? > > The error is mentioning status "down", which is not valid under any > module. A value like that makes sense in the monitoring module ( > https://github.com/openwisp/openwisp-monitoring/), but the definitions > used are "problem" and "critical", the labels can be changed however, so > that "critical" can be relabeled to "down", if preferred, but the > monitoring module is not even at version 0.1 yet. > > Best regards > Federico > > > On Tue, Oct 6, 2020 at 5:20 AM Ian Tait <[email protected]> wrote: > > Hi, > > Upgrading from 0.10 -> 0.11, getting an error in the migrate section: > > line 1222, in full_clean\n raise > ValidationError(errors)\ndjango.core.exceptions.ValidationError: {'status': > [\"Value 'down' is not a valid choice.\"]} > > Is that something that I can fix? > > Thanks. > > Ian > > -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/openwisp/193309916.233450.1601979648704%40privateemail.com > ( > https://groups.google.com/d/msgid/openwisp/193309916.233450.1601979648704%40privateemail.com?utm_medium=email&utm_source=footer). > > > > -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/openwisp/CAERYH6WUyXhbHQkNk2R2u5zhwEexPT%3DK-4HVn0mnC27mv12QGQ%40mail.gmail.com > ( > https://groups.google.com/d/msgid/openwisp/CAERYH6WUyXhbHQkNk2R2u5zhwEexPT%3DK-4HVn0mnC27mv12QGQ%40mail.gmail.com?utm_medium=email&utm_source=footer). > > > -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/openwisp/522883696.271286.1602068733092%40privateemail.com > <https://groups.google.com/d/msgid/openwisp/522883696.271286.1602068733092%40privateemail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/CAERYH6WGcF_%3DsuyKv-u1%3DadzacrG%2BqZTDwDen%2Buin3nnzWCc8A%40mail.gmail.com.
