tag 847277 + unreproducible
severity 847277 normal
thanks

On Tue, 06 Dec 2016 22:15:30 +0100
Andreas Beckmann <a...@debian.org> wrote:

> Package: lava-server
> Version: 2016.11-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade
> from 'jessie' to 'jessie-backports' to 'stretch'.
> It installed fine in 'jessie' and upgraded to 'jessie-backports'
> successfully, then the upgrade to 'stretch' fails.

In a jessie VM which was upgraded to jessie-backports and then to stretch, 
lava-server upgraded perfectly. We also run daily upgrade and install tests 
inside LAVA itself on our staging instance.

Downgrading until the problem can be reproduced outside piuparts.

> >From the attached log (scroll to the bottom...):  

.. unable to download log from the bug report and no attachment was received.
 
>   Setting up lava-server (2016.11-1) ...
>   Installing new version of config
> file /etc/apache2/sites-available/lava-server.conf ... Installing new
> version of config file /etc/init.d/lava-server ... Installing new
> version of config file /etc/lava-server/settings.conf ... Installing
> new version of config file /etc/lava-server/uwsgi.ini ... lavaserver
>    lavaserver
>    devel
>    devel
>   System check identified some issues:
>   
>   WARNINGS:
>   va_scheduler_app.Notification.job_status_trigger: (fields.W901)
> CommaSeparatedIntegerField has been deprecated. Support for it
> (except in historical migrations) will be removed in Django 2.0.
> HINT: Use
> CharField(validators=[validate_comma_separated_integer_list]) instead.
> 
> cceback (most recent call last):
>     File "/usr/bin/lava-server", line 77, in <module>
>       main()
>     File "/usr/bin/lava-server", line 74, in main
>       execute_from_command_line(django_options)
>     File
> "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
> line 367, in execute_from_command_line utility.execute() File
> "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
> line 359, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv) File
> "/usr/lib/python2.7/dist-packages/django/core/management/base.py",
> line 294, in run_from_argv self.execute(*args, **cmd_options) File
> "/usr/lib/python2.7/dist-packages/django/core/management/base.py",
> line 345, in execute output = self.handle(*args, **options) File
> "/usr/lib/python2.7/dist-packages/django/core/management/commands/migrate.py",
> line 86, in handle
> executor.loader.check_consistent_history(connection) File
> "/usr/lib/python2.7/dist-packages/django/db/migrations/loader.py",
> line 292, in check_consistent_history connection.alias,
> django.db.migrations.exceptions.InconsistentMigrationHistory:
> Migration lava_scheduler_app.0001_initial is applied before its
> dependency linaro_django_xmlrpc.0001_initial on database 'default'.
> heerr, r processing package lava-server (--configure): subprocess
> installed post-installation script returned error exit status 1

This looks like a partial (and broken) purge was forced before the upgrade.

-- 


Neil Williams
=============
http://www.linux.codehelp.co.uk/

Attachment: pgppfvIM2AdYi.pgp
Description: OpenPGP digital signature

Reply via email to