Project

Profile

Help

Issue #8999

closed

A no-op re-sync of a file repository will (if mirroring is enabled) result in a failed task

Added by dalley over 1 year ago. Updated over 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

The problem is that mirror-mode tries to publish without checking whether a new repository version has actually been created. "rv == None" and it blows up.


  File "/usr/local/lib/pulp/lib64/python3.9/site-packages/pulp_smash/pulp3/bindings.py", line 78, in monitor_task
    raise PulpTaskError(task=task)
pulp_smash.pulp3.bindings.PulpTaskError: (PulpTaskError(...), 'Pulp task failed (null value in column "repository_version_id" of relation "core_publication" violates not-null constraint\nDETAIL:  Failing row contains (6c867c2b-5cf0-41d4-baec-8c01600022fb, 2021-07-01 00:33:43.763667+00, 2021-07-01 00:33:43.763675+00, file.file, f, t, null).\n)')


Related issues

Related to File Support - Backport #9060: Backport 8999CLOSED - CURRENTRELEASEdaviddavis

Actions
Actions #1

Updated by dalley over 1 year ago

  • Project changed from Pulp to File Support

Added by dalley over 1 year ago

Revision f73bc657

Fix error on no-op mirror sync

closes: #8999 https://pulp.plan.io/issues/8999

Actions #3

Updated by dalley over 1 year ago

  • Status changed from POST to MODIFIED
Actions #4

Updated by dalley over 1 year ago

Actions #6

Updated by pulpbot over 1 year ago

  • Sprint/Milestone set to 1.9.0
Actions #7

Updated by pulpbot over 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF