Project

General

Profile

Actions

Bug #18941

closed

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

Added by Leah Fisher about 7 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Repositories
Target version:
Difficulty:
Triaged:
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.

Actions #1

Updated by Eric Helms about 7 years ago

  • Status changed from New to Needs design
Actions #2

Updated by John Mitsch almost 7 years ago

  • Category set to Repositories
  • Assignee set to John Mitsch
  • translation missing: en.field_release set to 228
Actions #3

Updated by John Mitsch almost 7 years ago

  • Target version set to 160
Actions #4

Updated by Justin Sherrill almost 7 years 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.

Actions #5

Updated by Justin Sherrill almost 7 years ago

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

Actions #6

Updated by Justin Sherrill almost 7 years ago

  • Status changed from Needs design to Need more information
  • translation missing: en.field_release changed from 228 to 166
Actions #7

Updated by Justin Sherrill almost 7 years 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!

Actions

Also available in: Atom PDF