Bug 972923 - uploads erratum doesn't check the updated and issued parameters for the proper format
uploads erratum doesn't check the updated and issued parameters for the prope...
Status: CLOSED DUPLICATE of bug 1101597
Product: Pulp
Classification: Community
Component: rpm-support (Show other bugs)
2.2 Beta
Unspecified Unspecified
low Severity unspecified
: ---
: 2.6.0
Assigned To: pulp-bugs
Preethi Thomas
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2013-06-10 15:58 EDT by Jeremy Cline
Modified: 2014-12-01 12:24 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-12-01 12:24:52 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jeremy Cline 2013-06-10 15:58:36 EDT
Description of problem: According to the CLI, the --updated and --issued options of the 'pulp-admin rpm repo uploads erratum' command expect the format "YYYY-MM-DD HH:MM:SS". However, this is not checked, and no sort of error is reported.

Version-Release number of selected component (if applicable): pulp-rpm-admin-extensions-2.2.0-0.2.beta.fc18.noarch

How reproducible:

Steps to Reproduce:
1. pulp-admin rpm repo create --repo-id=uploads_errata
2. create a fake pkglist csv in the format "name,version,release,epoch,arch,filename,checksum,checksum_type,sourceurl"
3.pulp-admin rpm repo uploads erratum --repo-id=uploads_errata --erratum_id=test_id --title="Title of the Erratum" --description="A terse description of the erratum" --version=1.0.0 --release=stable --type=enhancement --status=final --updated="A long, long time ago" --issued="The day after tomorrow" --pkglist-csv=/home/jcline/fake_pkg_csv --from="someone@somewhere.com"

Actual results: The erratum is created and uploaded.

Expected results: Error message indicating the updated and issued fields are not of the expected format ("YYYY-MM-DD HH:MM:SS")

Additional info:
Comment 2 Jeremy Cline 2014-12-01 12:24:52 EST

*** This bug has been marked as a duplicate of bug 1101597 ***

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