Issue #6354
closed
_last_updated is not set when a module or module-defaults are updated
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.
Updated by pulpbot about 4 years ago
- Status changed from NEW to POST
Added by ttereshc almost 4 years ago
Updated by ttereshc almost 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset c227c1d12494dc113a44436609a0ccf1409e3ee5.
Added by ttereshc almost 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)
Updated by pulpbot almost 4 years ago
Updated by ttereshc almost 4 years ago
Applied in changeset 456756b44745b13f3a57b74e827b27c3ed6f7b59.
Updated by dalley almost 4 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
.
Use
saveinstead ofupdateso _last_updated is set properlycloses #6354 https://pulp.plan.io/issues/6354