Project

General

Profile

Actions

Bug #37481

closed

Org still holds stale cached manifest expiration date after manifest import/refresh

Added by Jeremy Lenz 6 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Subscriptions
Target version:
Fixed in Releases:
Found in Releases:

Description

This means that after a manifest import / refresh, the manifest expiration date may be inaccurate until the cache expiration time (1 minute). Because of this you must refresh the browser page to see the new manifest expiration date.

Actions #1

Updated by The Foreman Bot 6 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/10999 added
Actions #2

Updated by Samir Jha 6 months ago

  • Triaged changed from No to Yes
Actions #3

Updated by The Foreman Bot 6 months ago

  • Fixed in Releases Katello 4.13.0 added
Actions #4

Updated by Jeremy Lenz 6 months ago

  • Status changed from Ready For Testing to Closed
Actions #5

Updated by The Foreman Bot 6 months ago

  • Pull request https://github.com/Katello/katello/pull/11019 added
Actions #6

Updated by The Foreman Bot 5 months ago

  • Pull request https://github.com/Katello/katello/pull/11051 added
Actions

Also available in: Atom PDF