Project

General

Profile

Bug #24855

repository update will save info to Katello DB before backend services are updated

Added by Chris Duryee 9 months ago. Updated 6 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

If you enter bad data in Katello on the repository update page or via hammer or API, you may be able to get into a state where the Katello DB is updated, but Pulp does not accept the data. You're then left in a state where Katello and Pulp have a mismatch, which can cause issues.

To reproduce this issue, you may need to revert https://github.com/Katello/katello/pull/7673. There are probably other ways to do it too (perhaps by stopping pulp during a repo update), but I'm not sure how.

app/lib/actions/katello/repository/update.rb likely needs to be refactored to not update the attributes during plan phase.

History

#1 Updated by Jonathon Turel 8 months ago

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

#2 Updated by Christine Fouant 6 months ago

  • Target version changed from Katello 3.10.0 to Katello Backlog

Also available in: Atom PDF