Bug #8511

Klever does not remove old jobs

Added by Pavel Andrianov over 3 years ago. Updated over 3 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Detected in build:
Published in build:


The report was uploaded with "Upload report" successfully. When we try to remove or reupload, Bridge fails with

Deleting ReportRoot files took 0.004882335662841797 seconds.
The 'archive' attribute has no file associated with it.
Traceback (most recent call last):
  File "/home/ldvuser/work/klever/bridge/jobs/", line 1111, in upload_reports
    UploadReportsWithoutDecision(job, request.user,
  File "/home/ldvuser/work/klever/bridge/jobs/", line 749, in __init__
  File "/home/ldvuser/work/klever/bridge/jobs/", line 782, in __prepare_job
    StartJobDecision(self._user,, configuration, fake=True)
  File "/home/ldvuser/work/klever/bridge/service/", line 785, in __init__
  File "/home/ldvuser/.local/lib/python3.5/site-packages/django/db/models/", line 972, in delete
    return collector.delete()
  File "/home/ldvuser/.local/lib/python3.5/site-packages/django/db/models/", line 279, in delete
    sender=model, instance=obj, using=self.using
  File "/home/ldvuser/.local/lib/python3.5/site-packages/django/dispatch/", line 193, in send
    for receiver in self._live_receivers(sender)
  File "/home/ldvuser/.local/lib/python3.5/site-packages/django/dispatch/", line 193, in <listcomp>
    for receiver in self._live_receivers(sender)
  File "/home/ldvuser/work/klever/bridge/reports/", line 165, in coverage_archive_delete_signal
  File "/home/ldvuser/.local/lib/python3.5/site-packages/django/db/models/fields/", line 65, in path
  File "/home/ldvuser/.local/lib/python3.5/site-packages/django/db/models/fields/", line 47, in _require_file
    raise ValueError("The '%s' attribute has no file associated with it." %
ValueError: The 'archive' attribute has no file associated with it.

The exception is thrown only for removing old jobs, which were created before updating Klever. All new reports are removed successfully. Now we have a set of jobs, which can not be modified, except renaming.



Updated by Evgeny Novikov over 3 years ago

  • Assignee set to Vladimir Gratinskiy
  • Priority changed from Normal to Immediate

It looks like a regression bug. So, we need either its fix (it shouldn't require dropping databases, say, because of some old incorrect migrations since that has no sense) or at least some workaround (it isn't necessary to run it through the web interface).


Updated by Evgeny Novikov over 3 years ago

  • Target version set to 1.0

If this will be possible, I would like to backport the bug fix to the stable branch for Klever 0.2.


Updated by Vladimir Gratinskiy over 3 years ago

  • Due date set to 10/20/2017
  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Fix in fix_8511 should solve the problem.


Updated by Evgeny Novikov over 3 years ago

  • Status changed from Resolved to Closed

It turned out that good testing of this bug fix is hard. So, after some shallow testing I merged the branch to master in ddb22435.

Due to lack of good testing I won't backport it to Klever 0.2. Thus, one won't be able to remove some old jobs until update to the specified version or to Klever version:0.3.

Also available in: Atom PDF