Project

General

Profile

Bug #18941

Repo sync is completing successfully, but is not finding new packages that are in the repo

Added by Leah Fisher over 1 year ago. Updated about 1 month ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Repositories
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Brad
Fixed in Releases:
Found in Releases:

Description

Upon upgrade from 3.2 to 3.3, the sync was no longer updating properly. Since I was syncing to a local url, I was able to look at my apache logs and see that there was no request for repodata in my apache logs. I'm unsure why it was completing successfully.

Updating the link to somethat that would error and changing it back seemed to solve the problem. I also had to run
mongo pulp_database --eval 'db.repo_importers.update({"scratchpad": {$ne: null}}, {$set: {"scratchpad.repomd_revision": null}}, {"multi":true})' since the repo metadata date locally got update.

History

#1 Updated by Eric Helms over 1 year ago

  • Status changed from New to Needs design

#2 Updated by John Mitsch over 1 year ago

  • Category set to Repositories
  • Assignee set to John Mitsch
  • Legacy Backlogs Release (now unused) set to 228

#3 Updated by John Mitsch over 1 year ago

  • Target version set to 160

#4 Updated by Justin Sherrill over 1 year ago

I believe this may have been resolved by http://projects.theforeman.org/issues/18816 where by the feed url was being updated to localhost.

#5 Updated by Justin Sherrill over 1 year ago

Are you able to reproduce this on 3.3.1 or 3.4 rc?

#6 Updated by Justin Sherrill about 1 year ago

  • Status changed from Needs design to Need more information
  • Legacy Backlogs Release (now unused) changed from 228 to 166

#7 Updated by Justin Sherrill about 1 year ago

  • Status changed from Need more information to Rejected

Closing this as we believe it is now resolved, please reopen if you can still reproduce!

Also available in: Atom PDF