RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 651789 - rhn-channel should report error when adding/removing wrong channel
Summary: rhn-channel should report error when adding/removing wrong channel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rhn-client-tools
Version: 6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Miroslav Suchý
QA Contact: Martin Minar
URL:
Whiteboard:
Depends On: 670214 670216
Blocks: 582655 651790 715145
TreeView+ depends on / blocked
 
Reported: 2010-11-10 09:58 UTC by Petr Sklenar
Modified: 2016-07-04 00:55 UTC (History)
4 users (show)

Fixed In Version: rhn-client-tools-1.0.0-44
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 651790 670214 670216 (view as bug list)
Environment:
Last Closed: 2011-05-19 13:05:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0565 0 normal SHIPPED_LIVE rhn-client-tools and yum-rhn-plugin bug fix and ehnancement update 2011-05-18 17:57:10 UTC

Comment 2 Miroslav Suchý 2011-01-17 15:15:58 UTC
This is more difficult then it look.

First. spacewalk-channel does not read returned code. Let solve it here.
Let define return code:
0  - everything is OK, channel is added/removed
1  - some error, channel is *not* added/removed
I will track client changes in this BZ.

Second. rhnParent always send return code 0. No matter what happen there.
So we have to do some change in both RHN Satellite and RHN hosted.

I will clone this BZ to both RHN Satellite and RHN hosted to track the change in server parts.

Comment 3 Miroslav Suchý 2011-01-17 15:55:11 UTC
Fixed in spacewalk.git as commit ca2b95ea966d7a1f8efb56fd2569effed9e778d0

Comment 4 Miroslav Suchý 2011-01-17 16:08:12 UTC
cherry picked to satellite.git as commit 5189ecd9aa5a1cdc8540d146416543e6959b2bac

Comment 7 Miroslav Suchý 2011-02-24 10:48:57 UTC
I could not reproduce, flipping back to ON_QA

Comment 9 Miroslav Suchý 2011-02-24 16:26:07 UTC
This is problem in backend handler. If there is no exception in code (i.e. one should be raised if you use name, which does not exist) there is simple
 return 0
So I have no chance to raise error on client.

If you use non existend name. E.g foo, you will get:
Error Message:
    Channel foo does not exist?

I will clone this BZ to RHN Satellite. Please test it without the problem in #8

Comment 10 Miroslav Suchý 2011-02-24 16:27:47 UTC
Argh, I already created them in past. 
See #670214 #670216.

Comment 11 Martin Minar 2011-02-25 09:05:44 UTC
Verified with rhn-client-tools-1.0.0-50.el6.noarch

Comment 12 errata-xmlrpc 2011-05-19 13:05:17 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0565.html


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