Project

General

Profile

Bug #31972

The repository update API should be asynchronous instead of synchronous since it spawns asynchronous Pulp 3 tasks

Added by Ian Ballou over 1 year ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Repositories
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

We're working around this for repository update since it's extra complicated to make it asynchronous, but changing the update API shouldn't be as bad.

Note: this will be a breaking API change, so it should be done as early as possible for 4.0.

History

#1 Updated by Ian Ballou over 1 year ago

  • Tracker changed from Refactor to Bug

#2 Updated by Ian Ballou over 1 year ago

  • Target version changed from Katello 4.0.1 to Katello 4.1.0

#3 Updated by Chris Roberts about 1 year ago

  • Triaged changed from No to Yes

#4 Updated by Ian Ballou about 1 year ago

  • Target version changed from Katello 4.1.0 to Katello 4.2.0

#5 Updated by Ian Ballou 10 months ago

  • Target version changed from Katello 4.2.0 to Katello 4.3.0

#6 Updated by Ian Ballou 7 months ago

  • Triaged changed from Yes to No
  • Target version changed from Katello 4.3.0 to Katello 4.4.0

I think we missed the bus on this one, so I'd like to bring it up in triage again.

#7 Updated by Justin Sherrill 7 months ago

  • Triaged changed from No to Yes

#8 Updated by Ian Ballou 7 months ago

To avoid API breakages, let's consider adding an API flag to run asynchronously.

#9 Updated by Ian Ballou 4 months ago

  • Triaged changed from Yes to No

#10 Updated by Ian Ballou 4 months ago

  • Target version deleted (Katello 4.4.0)

#11 Updated by Jonathon Turel 3 months ago

  • Triaged changed from No to Yes
  • Target version set to Katello Backlog

Also available in: Atom PDF