Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 843462 - system unregister should remove itself from the associated system groups too
system unregister should remove itself from the associated system groups too
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: WebUI (Show other bugs)
6.0.1
Unspecified Unspecified
urgent Severity urgent (vote)
: Unspecified
: Unused
Assigned To: Brad Buckingham
Garik Khachikyan
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-26 07:47 EDT by Garik Khachikyan
Modified: 2015-01-04 16:59 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Unregistering a system via Red Hat Subscription Manager (RHSM) removes the system from the Organization's system list. However, it does not remove the system from associated system groups. System Engine failed when indexing the content in Pulp for the system group when the system was destroyed, which rendered the authorization credentials invalid. This fix modifies Pulp to only include required information and not index the content. Unregistering a system now removes it from all subscribed system groups.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-12-04 14:48:25 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-04 19:39:57 EST

  None (edit)
Description Garik Khachikyan 2012-07-26 07:47:59 EDT
Description of problem:
RHSM unregister does currently remove the system from the Org's system list but not cleans the info from all associated system groups. Doing cli `system_group systems` (as well as UI lising the systems of system group) still *shows* that system's info. 
Having limitation on system groups system count could bring to a problem.

Version-Release number of selected component (if applicable):
katello-configure-0.2.31-1.git.63.13a3892.el6.noarch
katello-glue-pulp-0.2.50-1.git.0.1110b64.el6.noarch
mod_wsgi-3.3-3.pulp.el6.x86_64
candlepin-0.5.32-1.el6.noarch
katello-common-0.2.50-1.git.0.1110b64.el6.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
qpid-cpp-client-0.14-16.el6.x86_64
python-oauth2-1.5.170-2.pulp.el6.noarch
katello-agent-1.0.4-1.git.11.1606589.el6.noarch
katello-repos-0.2.6-1.el6.noarch
qpid-cpp-server-0.14-16.el6.x86_64
qpid-cpp-client-ssl-0.14-16.el6.x86_64
candlepin-tomcat6-0.5.32-1.el6.noarch
katello-glue-foreman-0.2.50-1.git.0.1110b64.el6.noarch
katello-0.2.50-1.git.0.1110b64.el6.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-cli-common-0.2.45-1.git.0.5a7444e.el6.noarch
qpid-cpp-server-ssl-0.14-16.el6.x86_64
pulp-common-1.1.11-1.el6.noarch
python-qpid-0.14-8.el6.noarch
katello-selinux-0.2.6-1.git.9.1606589.el6.noarch
pulp-1.1.11-1.el6.noarch
katello-cli-0.2.45-1.git.0.5a7444e.el6.noarch
m2crypto-0.21.1.pulp-7.el6.x86_64
katello-certs-tools-1.1.6-1.git.572.1606589.el6.noarch
pulp-selinux-server-1.1.11-1.el6.noarch
katello-glue-candlepin-0.2.50-1.git.0.1110b64.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. register system to Katello 
2. assign to any system group
3. see it appears in system group's system list
4. unregister system
  
Actual results:
it removes the system from the org's system list but not from the list of the system group being associated.

Expected results:
all associated system groups should be adjusted with the fact of system being unregistered.

Additional info:
Comment 1 Brad Buckingham 2012-08-29 10:17:20 EDT
github pull request: 
https://github.com/Katello/katello/commit/1223e8f9c993dca5f3c7352619dc14c3f7daf137

github commit:
https://github.com/Katello/katello/commit/f5582c51e4a78d6bab34bafb9502640292f989b3

See commit for description of changes.
Comment 3 Garik Khachikyan 2012-09-17 10:33:38 EDT
# VERIFIED

issue is fixed. Adding the registered system to 2 different system groups (one with limit number of usage) does the right job on system unregister.

Same behaviour on system remove from UI and CLI calls.

Checked on version:
---
python-qpid-0.7.946106-1.el6.noarch
candlepin-cert-consumer-brno-cfse.usersys.redhat.com-1.0-1.noarch
qpid-cpp-client-0.14-16.el6.x86_64
candlepin-0.7.8-1.el6cf.noarch
katello-glue-pulp-1.1.12-7.el6cf.noarch
qpid-cpp-server-ssl-0.14-16.el6.x86_64
katello-candlepin-cert-key-pair-1.0-1.noarch
mod_wsgi-3.3-3.pulp.el6.x86_64
python-isodate-0.4.4-4.pulp.el6.noarch
katello-cli-common-1.1.8-1.git.2.a0908e7.el6.noarch
katello-cli-1.1.8-1.git.2.a0908e7.el6.noarch
qpid-cpp-client-ssl-0.14-16.el6.x86_64
python-oauth2-1.5.170-2.pulp.el6.noarch
pulp-common-1.1.12-1.el6cf.noarch
pulp-selinux-server-1.1.12-1.el6cf.noarch
m2crypto-0.21.1.pulp-7.el6.x86_64
candlepin-selinux-0.7.8-1.el6cf.noarch
katello-common-1.1.12-7.el6cf.noarch
katello-glue-candlepin-1.1.12-7.el6cf.noarch
katello-1.1.12-7.el6cf.noarch
katello-all-1.1.12-7.el6cf.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-certs-tools-1.1.8-1.el6cf.noarch
katello-repos-1.1.2-1.el6.noarch
katello-agent-1.1.2-1.el6.noarch
katello-configure-1.1.9-3.el6cf.noarch
qpid-cpp-server-0.14-16.el6.x86_64
pulp-1.1.12-1.el6cf.noarch
katello-selinux-1.1.1-1.el6cf.noarch
candlepin-tomcat6-0.7.8-1.el6cf.noarch
katello-qpid-client-key-pair-1.0-1.noarch
Comment 5 errata-xmlrpc 2012-12-04 14:48:25 EST
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, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHSA-2012-1543.html
Comment 6 Mike McCune 2013-08-16 14:18:24 EDT
getting rid of 6.0.0 version since that doesn't exist

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