Bug 972942 - org name changes do not propogate via sst into katello
org name changes do not propogate via sst into katello
Status: CLOSED ERRATA
Product: Subscription Asset Manager
Classification: Red Hat
Component: Splice (Show other bugs)
1.3
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: James Slagle
mkovacik
:
Depends On:
Blocks: sam13-tracker
  Show dependency treegraph
 
Reported: 2013-06-10 17:04 EDT by Chris Duryee
Modified: 2013-10-01 06:55 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-10-01 06:55:45 EDT
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)

  None (edit)
Description Chris Duryee 2013-06-10 17:04:28 EDT
Description of problem: If a satellite's org name is changed, this change does not make it into SAM via spacewalk-splice-tool --spacewalk-sync.


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


How reproducible: every time


Steps to Reproduce:
1. create an org in satellite, and perform a sync
2. change the org's name
3. sync again

Actual results: org name is not altered in SAM


Expected results: org name should be changed in SAM


Additional info: If an org label exists for the org in SAM, we don't do any further processing. We probably need to do an additional check to update the name if needed.
Comment 1 James Slagle 2013-06-19 08:09:21 EDT
commit 300cd8b5612996a23acdd9def04056d1f38c70ea to sst

Org name changes are now propagated from Satellite to SAM.  I also update the distributor name as well since the org name is part of the distributor name.
Comment 2 Vitaly Kuznetsov 2013-06-21 10:25:44 EDT
Verified in spacewalk-splice-tool-0.24-1.el6sam.x86_64
Comment 4 errata-xmlrpc 2013-10-01 06:55:45 EDT
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/RHEA-2013-1390.html

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