Feature #33449

Tracker #33447: Alternate Content Sources Support Tracker

As a user, I can expect my ACSs to be refreshed appropriately

Added by Ian Ballou 9 months ago. Updated 17 days ago.

Target version:
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:


When to refresh:
1) At ACS creation time
2) On a cron-based schedule
-> cron config:
-> The user can edit the cron config if they choose
3) When an ACS refresh API endpoint is hit

It would also be good to have a rake task to refresh the ACSs.

At refresh time, also update the remote and/or ACS if necessary.

Associated revisions

Revision 68b2cc92 (diff)
Added by Ian Ballou 18 days ago

Fixes #33449 - Alternate Content Source refreshing support (#10083)


#1 Updated by Ian Ballou 9 months ago

We should also ensure there is a hammer command to refresh ACSs.

#2 Updated by Jonathon Turel 9 months ago

  • Target version set to Katello 4.3.0

#3 Updated by Ian Ballou 9 months ago

  • Target version changed from Katello 4.3.0 to Katello Backlog

#4 Updated by Samir Jha 8 months ago

  • Triaged changed from No to Yes

#5 Updated by Ian Ballou about 1 month ago

As part of this, we need to ensure the ACS API returns a 'last refreshed' parameter for the UI.

#6 Updated by Ian Ballou 30 days ago

  • Target version changed from Katello Backlog to Katello 4.5.0

#7 Updated by The Foreman Bot 27 days ago

  • Assignee set to Ian Ballou
  • Status changed from New to Ready For Testing
  • Pull request added

#8 Updated by The Foreman Bot 18 days ago

  • Fixed in Releases Katello 4.5.0 added

#9 Updated by Anonymous 18 days ago

  • Status changed from Ready For Testing to Closed

#10 Updated by Ian Ballou 17 days ago

  • Target version deleted (Katello 4.5.0)
  • Assignee deleted (Ian Ballou)
  • Category deleted (Repositories)
  • Fixed in Releases deleted (Katello 4.5.0)

Just to be clear, this issue did not take care of the cron job. There is a separate packaging issue for that.

Also available in: Atom PDF