Bug 67492 - Channel import causes tracebacks
Summary: Channel import causes tracebacks
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server
Version: unspecified
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Mihai Ibanescu
QA Contact: Fanny Augustin
Depends On:
TreeView+ depends on / blocked
Reported: 2002-06-26 12:50 UTC by Greg DeKoenigsberg
Modified: 2007-07-31 19:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2002-06-26 12:53:34 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Greg DeKoenigsberg 2002-06-26 12:50:24 UTC
So, when I run the initial channel import command...

satellite-import -channels -c redhat-linux-i386-7.3 --mountpoint /mnt/rhn-sat-import

I get the following error:

server.rhnSQL.sql_base.SQLError: (1400, 'ORA-01400: cannot insert NULL into
'insert into rhnChannelFamilyMembers (channel_id, channel_family_id) values
(:channel_id, :channel_family_id)', 'Params': [(':channel_family_id', [None]),
(':channel_id', [101])]})

...which is interesting.  I figured, well, maybe satellite-import isn't so good;
why not try the satellite-sync command?  So I ran the command from the docs:

satellite-sync -c redhat-linux-i386-7.2 --mountpoint /mnt/misc/rhndata

...which fails in a different way, which I failed to record.  But then, after
having run that, running the previous satellite-import command works (boggle).

I did replicate this for two different Oracle users in the classroom.

Therefore: I'm guessing that something isn't being set correctly by the CD-based
satellite-import that *is* being set correctly by satellite-sync.


1. Which tool is supported for filesystem-based install, satellite-import or
satellite-sync, or both?

2. Whichever one is supported, isn't working.

Relevant packages:

Comment 1 Mihai Ibanescu 2002-06-26 13:33:02 UTC
First step is 
satellite-import --channelfamilies --mountpoint /mnt/rhn-sat-import

Didn't get to update the freaking documentation. Doing it now.

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