Bug 83127 - rmchannel doesn't work
rmchannel doesn't work
Status: CLOSED CURRENTRELEASE
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Mihai Ibanescu
Red Hat Satellite QA List
:
Depends On:
Blocks: 78555
  Show dependency treegraph
 
Reported: 2003-01-30 11:00 EST by Jason Kohles
Modified: 2007-07-31 15:20 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-30 11:18:30 EST
Type: ---
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 Jason Kohles 2003-01-30 11:00:23 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
[root@linuxsat-m01 root]# rmchannel -c redhat-powertools-i386-7.1
Traceback (innermost last):
  File "/usr/bin/rmchannel", line 16, in ?
    sys.exit(main() or 0)
  File "/var/www/rhns/satellite_tools/satrm.py", line 81, in main
    justdb=options.justdb)
  File "/var/www/rhns/satellite_tools/satrm.py", line 165, in delete_channels
    h = rhnSQL.prepare(query % (table, field))
  File "/var/www/rhns/server/rhnSQL/__init__.py", line 97, in prepare
    return db.prepare(sql)
  File "/var/www/rhns/server/rhnSQL/intOracle.py", line 128, in prepare
    self.cache[sql] = Cursor(self.dbh, sql)
  File "/var/www/rhns/server/rhnSQL/_intOracle.py", line 42, in __init__
    raise rhnException("Can not prepare statement", e.args)
common.rhnException.rhnException: ('Can not prepare statement', (942,
'ORA-00942: table or view does not exist\012', {'SQL': 'delete from
rhnPathChannelMap where channel_id = :channel_id', 'Params': None}))


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


How reproducible:
Always

Steps to Reproduce:
1.rmchannel -c <channel>
2.
3.
    

Additional info:
Comment 1 Mihai Ibanescu 2003-01-30 11:13:27 EST
Should be fixed in 1.2.6.1-14
Comment 2 Jason Kohles 2003-01-30 11:18:30 EST
Indeed it is fixed...

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