Issue #6605
updated advisories with missing updated_date can cause sync failure
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
- create repository
- sync remote rpm-unsigned
- re-sync same repo with rpm-advisory-no-update-date remote
"error" {
"description": "'<' not supported between instances of 'datetime.datetime' and 'NoneType'"
...}
History
Please register to edit this issue