Bug 1035288 - Update spacewalk-remote-utils with RHEL 6.5 channel definitions
Summary: Update spacewalk-remote-utils with RHEL 6.5 channel definitions
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Client
Version: 560
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks: sat560-triage
TreeView+ depends on / blocked
 
Reported: 2013-11-27 13:15 UTC by Tomas Lestach
Modified: 2013-12-02 08:14 UTC (History)
2 users (show)

Fixed In Version: spacewalk-remote-utils-2.0.1-3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-02 08:14:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1777 0 normal SHIPPED_LIVE Red Hat Network Tools spacewalk-remote-utils enhancement update 2013-12-02 13:14:23 UTC

Description Tomas Lestach 2013-11-27 13:15:57 UTC 
Description of problem:
spacewalk-remote-utils does not contain RHEL 6.5 channel definitions

Version-Release number of selected component (if applicable):
spacewalk-remote-utils-2.0.1-2
Comment 1 Tomas Lestach 2013-11-27 13:25:30 UTC 
spacewalk.git: afa8824b1745ab4284bab0b12153ea95d51261cb
Comment 3 Lukas Pramuk 2013-11-27 14:59:54 UTC 
VERIFIED. spacewalk-remote-utils-2.0.1-3.el6sat

REPRO:
# spacewalk-create-channel -l admin -s `hostname` -v 6 -u u5 -r Server -a x86_64 -d rhel6u5
Password:
Error: data file '6-u5-server-x86_64' does not exist

vs.

FIX:
# spacewalk-create-channel -l admin -s `hostname` -v 6 -u u5 -r Server -a x86_64 -d rhel6u5
Password: 
You have not specified a source channel, we will try to determine it from inputs
Trying with source channel: rhel-x86_64-server-6
Creating channel, rhel6u5, with arch x86_64 3690 packages in source file to push.
...
Comment 5 errata-xmlrpc 2013-12-02 08:14:44 UTC 
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-1777.html
Note You need to log in before you can comment on or make changes to this bug.