Project

Profile

Help

Issue #6354

closed

_last_updated is not set when a module or module-defaults are updated

Added by ipanova@redhat.com almost 5 years ago. Updated over 4 years ago.

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

Description

Currently we update the record and then call safe_import.

https://github.com/pulp/pulp_rpm/blob/2-master/plugins/pulp_rpm/plugins/importers/yum/modularity.py#L108 https://github.com/pulp/pulp_rpm/blob/2-master/plugins/pulp_rpm/plugins/importers/yum/modularity.py#L285

This approach does not update the _last_updated field on the unit.

To fix this we need to call save() instead that in the _pre_save_signal updates _last_updated, or we need to manually update that field on the unit.

Actions #1

Updated by ttereshc almost 5 years ago

  • Triaged changed from No to Yes
Actions #2

Updated by pulpbot over 4 years ago

  • Status changed from NEW to POST

Added by ttereshc over 4 years ago

Revision c227c1d1 | View on GitHub

Use save instead of update so _last_updated is set properly

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

Actions #3

Updated by ttereshc over 4 years ago

  • Status changed from POST to MODIFIED
Actions #4

Updated by dalley over 4 years ago

  • Platform Release set to 2.21.2

Added by ttereshc over 4 years ago

Revision 456756b4 | View on GitHub

Use save instead of update so _last_updated is set properly

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

(cherry picked from commit c227c1d12494dc113a44436609a0ccf1409e3ee5)

Actions #6

Updated by ttereshc over 4 years ago

Actions #7

Updated by dalley over 4 years ago

  • Status changed from MODIFIED to 5
Actions #8

Updated by dalley over 4 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE

Also available in: Atom PDF