Project

General

Profile

Bug #10257

re-registering a capsule can break the connection between the capsule and content host object that represent the capsule

Added by Eric Helms almost 8 years ago. Updated over 4 years ago.

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

Associated revisions

Revision c72411db (diff)
Added by Eric Helms almost 8 years ago

Fixes #10257: Connect capsule and its content host at the DB level.

Currently there is no direct connection between a capsule and the
content host that represents it other than look ups by hostname during
certain operations. If the Capsule has been re-registered, then there
are situations where multiple content host records with the same hostname
can exist. This in turn can lead to a number of issues including the inability
to create repositories and sync content properly. This change adds a
system_id attribute to the smart proxy model. When a content host is created
a check is performed for any smart proxies with that hostname and the
two are associated (or re-associated if the smart proxy already had a
content host attached). This will also link an existing content host
to a smart proxy when the proxy is created.

Revision 6bb3684b
Added by Eric Helms almost 8 years ago

Merge pull request #5195 from ehelms/fixes-10257

Fixes #10257: Connect capsule and its content host at the DB level.

History

#1 Updated by The Foreman Bot almost 8 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/5195 added
  • Pull request deleted ()

#2 Updated by Eric Helms almost 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#3 Updated by Eric Helms almost 8 years ago

  • Bugzilla link set to 1219870

Also available in: Atom PDF