Bug 153124
Summary: | using the same csv file twice should not require the --force option | ||
---|---|---|---|
Product: | [Retired] Red Hat Network | Reporter: | John Wregglesworth <wregglej> |
Component: | RHN/Backend | Assignee: | John Wregglesworth <wregglej> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Max Spevack <mspevack> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rhn400 | CC: | cmacleod, rhn-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHN 4.0.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-01 02:44:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 147875 |
Description
John Wregglesworth
2005-04-01 18:55:43 UTC
Removed the --force option and added the ability for rhn-download-manager to use the same csv file twice. this isn't entirly true. If you attempt to use the same csv file twice without deleteing anything that should require a force option (or be disallowed completely). doing 2 straight uploads would result in duplicate isos on the website. The problem I described was when isos were uploaded, then delete and then attempted to reupload again. Basically what happens is that they produce isos, then they get uploaded then they respinand we have to resync the isos and reupload them again after deleting them. rhn-download-manager shouldn't throw a FileModified error when doing a delete-upload cycle using the same csv file. It will throw a DuplicateFileError if the user attempts to upload a file that already exists in the db. Mass move to ON_QA <wregglej> mspevack_hm: chris has been using the changes I made to download-manager for a while now, you probably don't need to test that. There's not an easy test plan for that. <mspevack_hm> ok, PROD_READY it is :-) |