Bug 701238 - spacewalk-remove-channel in never ending cycle when a disk is full
Summary: spacewalk-remove-channel in never ending cycle when a disk is full
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization
Version: 541
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2011-05-02 08:56 UTC by Šimon Lukašík
Modified: 2014-07-04 13:26 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-04 13:26:43 UTC
Target Upstream Version:

Attachments (Terms of Use)
The log from Spacewalk-remove-channel (96.17 KB, text/plain)
2011-05-02 09:02 UTC, Šimon Lukašík 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Šimon Lukašík 2011-05-02 08:56:47 UTC 
Description of problem:
spacewalk-remove-channel ends with never ending cycle when there
is no space left on device.

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

How reproducible:
always

Steps to Reproduce:
1. Satellite sync rhel base channel
2. have a disk full
3. Increase the debug level of Spacewalk backend
3. spacewalk-remove-channel -c ...
  
Actual results:
Never ending loop of:

  Executing SQL: "delete from rhnPackageChangelog
  where package_id = :package_id" with bind params: ...

Expected results:
channel is deleted or at least error is thrown.
The never ending loop is not acceptable behaviour.

Additional info:
Comment 1 Šimon Lukašík 2011-05-02 09:02:46 UTC 
Created attachment 496191 [details]
The log from Spacewalk-remove-channel

Actually, the loop might not be never ending. It seems that after some
time Oracle manages to commit the transaction. (Note that the argument
of SQL changed 2011/05/02 04:52:28.
Note You need to log in before you can comment on or make changes to this bug.