Bug 1921055 - [RFE] Global Registration: Registration should remove older katello-ca-consumer if present
Summary: [RFE] Global Registration: Registration should remove older katello-ca-consum...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Registration
Version: 6.9.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: 6.10.0
Assignee: Leos Stejskal
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-27 13:12 UTC by Kenny Tordeurs
Modified: 2021-11-16 14:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:09:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31820 0 Normal Closed GR template - add --force option for Sub-man to re-register a host 2021-05-26 20:05:03 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:10:05 UTC

Description Kenny Tordeurs 2021-01-27 13:12:10 UTC
Description of problem:
Registration should remove katello-ca-consumer if present to avoid conflicts when moving a system from  Satellite -> Capsule or vice versa.

Version-Release number of selected component (if applicable):
Satellite 6.9

How reproducible:
100%

Steps to Reproduce:
1. Register system with Satellite
2. Attempt to register to Capsule
3.

Actual results:
~~~
Error: Transaction test error:
  file /usr/bin/katello-rhsm-consumer from install of katello-ca-consumer-ktordeur-testathon-capsule.kenny.lan-1.0-1.noarch conflicts with file from package katello-ca-consumer-ktordeur-testathon.kenny.lan-1.0-1.noarch
~~~


Expected results:
No errors

Additional info:

Comment 3 Kenny Tordeurs 2021-01-29 08:33:15 UTC
Trying to register a system to Capsule with the new global registration from

Comment 4 Leos Stejskal 2021-02-11 13:53:14 UTC
> Registration should remove katello-ca-consumer if present to avoid conflicts when moving a system from  Satellite -> Capsule or vice versa.

Registration feature does not support moving host from satellite to capsule.
Selecting capsule in registration form is for cases where host cannot access Satellite instance directly, only through Capsule.

Plus we don't want to delete anything on host machines without user's confirmation,
so I would say it's more of request for change than a bug.

Comment 9 Leos Stejskal 2021-03-02 09:46:11 UTC
Created redmine issue https://projects.theforeman.org/issues/31989 from this bug

Comment 10 Bryan Kearney 2021-04-27 08:03:52 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31989 has been resolved.

Comment 14 errata-xmlrpc 2021-11-16 14:09:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:4702


Note You need to log in before you can comment on or make changes to this bug.