Project

Profile

Help

Send by e-mail

Issue #6605

updated advisories with missing updated_date can cause sync failure

Added by ppicka 5 months ago. Updated 5 months ago.

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

Description

If advisory has same ID, version but update_date missing sync will fail.

If updated_date missing in advisory issued_date is not take into consideration in advisory conflict resolution time.

How to reproduce:

git clone https://github.com/pulp/pulp-fixtures
cd pulp-fixtures
# create fixtures
make fixtures/rpm-unsigned
make fixtures/rpm-advisory-no-update-date
  1. create repository
  2. sync remote rpm-unsigned
  3. re-sync same repo with rpm-advisory-no-update-date remote
"error" {
"description": "'<' not supported between instances of 'datetime.datetime' and 'NoneType'"
...}

History

#1 Updated by ppicka 5 months ago

  • Description updated (diff)

#2 Updated by ppicka 5 months ago

  • Subject changed from As user I can sync advisories with missing updated_date to updated advisories with missing updated_date can cause sync failure

#3 Updated by ppicka 5 months ago

  • Description updated (diff)

#4 Updated by ttereshc 5 months ago

  • Triaged changed from No to Yes

Please register to edit this issue

Send by e-mail

Also available in: Atom PDF