Bug 1304093 - Migrating a system can leave it in old-org's SSM rhnSet
Summary: Migrating a system can leave it in old-org's SSM rhnSet
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 2.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space27
TreeView+ depends on / blocked
 
Reported: 2016-02-02 21:02 UTC by Grant Gainey
Modified: 2017-09-28 18:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-16 07:45:24 UTC
Embargoed:

Attachments (Terms of Use)

Description Grant Gainey 2016-02-02 21:02:28 UTC 
Description of problem:


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

spacewalk-nightly

How reproducible:

* Have a spacewalk instance with two Orgs, Org1 and Org2
* Have Org2 'trust' Org1
* Register three systems to Org1.
* Select all three (puts them into Org1's SSM)
* Observe that Org1's SSM-count is now '3'
* Pick a system, and 'migrate' it to Org2
* Note that Org1's SSM-count stays at '3'
* Go to 'Manage'
* Go to 'List systems'
* Note that only the two not-migrated are shown

Actual results:

Migrated system's ID stays in Org1's SSM rhnSet

Expected results:

Migrating a system clears it from originating-org's SSM list, if it's in there.
Comment 1 Jiri Precechtel 2016-05-27 07:58:53 UTC 
Fixed

Space-walk-git: 42b2da21ad18a16088eb48e52a5526f5bc86b719

If the solution does not work for you, re-assign this bug please.
Comment 3 Tomáš Kašpárek 2016-06-16 07:45:24 UTC 
Spacewalk 2.5 was released.
Comment 4 Eric Herget 2017-09-28 18:11:21 UTC 
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.
Note You need to log in before you can comment on or make changes to this bug.