Bug 245969

Summary:	rhn-manage-channel --create should be a single XMLRPC call
Product:	[Retired] Red Hat Network	Reporter:	James Bowes <jbowes>
Component:	RHN/Backend	Assignee:	rhn-dev-list
Status:	CLOSED EOL	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	rhn500	CC:	bkearney, rhn-bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	189361, 428922

Description James Bowes 2007-06-27 18:10:02 UTC

rhn-5.0.2, rhn-content-mgmt-0.2.9

When running rhn-manage-channel with a csv file, and not specifying --commit,
you will see spurious errors if:
 The channel families do not exist, even though you specified --create-family
 A channel in your csv is a child channel of another channel in your csv

These happen because each channel creation, and each channel family creation, is
a distinct XMLRPC call that gets rolled back at the end.

Instead, the entire operation should be a single call, so it can be rolled back
or committed together.

Comment 1 James Bowes 2008-01-03 18:26:32 UTC

*** Bug 204521 has been marked as a duplicate of this bug. ***

Comment 2 James Bowes 2008-02-11 16:02:58 UTC

The code change for this will be large, for little gain; I'm not certain its
worth it.

Comment 5 Thomas "Shea" DeAntonio 2017-07-05 15:12:29 UTC

As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).

Comment 6 Thomas "Shea" DeAntonio 2017-07-05 15:13:19 UTC

As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).