Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not skip sync if units were removed from the repository. #859

Merged
merged 1 commit into from
May 10, 2016

Conversation

goosemania
Copy link
Member

sync_due_to_unit_removal = False
if last_sync is not None:
last_sync = dateutils.parse_iso8601_datetime(last_sync)
sync_due_to_unit_removal = last_sync < self.repo.last_unit_removed
Copy link
Member

@ipanova ipanova May 3, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think if there was no any unit removal then last_unit_removed will be None. I guess you should take this situation also into account when comparing to last_sync

@ipanova
Copy link
Member

ipanova commented May 10, 2016

@goosemania lgtm, please make sure that there is an issue opened for the pulp-smash test.

@ipanova ipanova added the LGTM label May 10, 2016
@ipanova ipanova assigned goosemania and unassigned ipanova May 10, 2016
@goosemania goosemania merged commit df5a26d into pulp:2.8-dev May 10, 2016
@goosemania goosemania deleted the issue1775 branch May 12, 2016 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants