Bug 158566 - Web site manages config file quota differently than rhncfg-manager
Summary: Web site manages config file quota differently than rhncfg-manager
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Web Site
Version: rhn400
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Shannon Hughes
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-05-23 16:31 UTC by John Wregglesworth
Modified: 2008-10-16 15:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-16 15:12:00 UTC
Embargoed:


Attachments (Terms of Use)

Description John Wregglesworth 2005-05-23 16:31:09 UTC
Description of problem: I've been working on bug 138749, which is about
rhncfg-manager being able to upload files without them counting against the
quota. I've noticed that the web side and the command-line side don't behave the
same way.

If you upload the same file into the same channel repeatedly through the web
interface without any changes to the file, the revision of the file gets bumped
up and the size of the file gets counted against the quota every time it gets
uploaded.

Using rhncfg-manager in 'add' mode, if you upload the same file (even with a
different filename) repeatedly, it only gets counted against the quota the first
time you upload it, and the revision doesn't get bumped up unless some changes
have been made. If you make some changes to the file and then upload it again,
the size of the file is counted against the quota and the revision number is
bumped up, which is correct. This happens because the md5 sum of the file is
stored in the db, and the file is counted against the quota only if the md5 sum
isn't already present in the db.

The web site should handle uploaded config files the same way rhncfg-manager
handles them.

Comment 1 Amanda Carter 2008-10-16 15:12:00 UTC
This bug has been closed due to inactivity.  Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed.


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