Project

General

Profile

Actions
Copy link

Feature #33449

closed

Tracker #33447: Alternate Content Sources Support Tracker (MVP)

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

Added by Ian Ballou almost 3 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ian Ballou
Category:
Repositories
Target version:
Katello 4.5.0
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
https://github.com/Katello/katello/pull/10083, https://github.com/Katello/katello/pull/10152
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

When to refresh:
1) At ACS creation time
2) On a cron-based schedule
-> cron config: https://github.com/theforeman/foreman-packaging/blob/rpm/develop/packages/katello/katello/katello.cron
-> 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.

Actions
Copy link
 #1

Updated by Ian Ballou almost 3 years ago

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

Actions
Copy link
 #2

Updated by Jonathon Turel almost 3 years ago

  • Target version set to Katello 4.3.0
Actions
Copy link
 #3

Updated by Ian Ballou almost 3 years ago

  • Target version changed from Katello 4.3.0 to Katello Backlog
Actions
Copy link
 #4

Updated by Samir Jha almost 3 years ago

  • Triaged changed from No to Yes
Actions
Copy link
 #5

Updated by Ian Ballou about 2 years ago

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

Actions
Copy link
 #6

Updated by Ian Ballou about 2 years ago

  • Target version changed from Katello Backlog to Katello 4.5.0
Actions
Copy link
 #7

Updated by The Foreman Bot about 2 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Ian Ballou
  • Pull request https://github.com/Katello/katello/pull/10083 added
Actions
Copy link
 #8

Updated by The Foreman Bot about 2 years ago

  • Fixed in Releases Katello 4.5.0 added
Actions
Copy link
 #9

Updated by Anonymous about 2 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link
 #10

Updated by Ian Ballou about 2 years ago

  • Category deleted (Repositories)
  • Assignee deleted (Ian Ballou)
  • Target version deleted (Katello 4.5.0)
  • 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.

Actions
Copy link
 #11

Updated by Ian Ballou about 2 years ago

  • Category set to Repositories
  • Assignee set to Ian Ballou
  • Target version set to Katello 4.5.0
Actions
Copy link
 #12

Updated by The Foreman Bot about 2 years ago

  • Pull request https://github.com/Katello/katello/pull/10152 added
Actions
Copy link

Also available in: Atom PDF