Bug 975874 - error messages for a null --repo-id are not consistent in rpm repo
error messages for a null --repo-id are not consistent in rpm repo
Product: Pulp
Classification: Community
Component: rpm-support (Show other bugs)
2.2 Beta
Unspecified Unspecified
low Severity unspecified
: ---
: ---
Assigned To: pulp-bugs
Preethi Thomas
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2013-06-19 09:59 EDT by Jeremy Cline
Modified: 2015-02-28 16:57 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-28 16:57:15 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)

External Trackers
Tracker ID Priority Status Summary Last Updated
Pulp Redmine 359 None None None Never

  None (edit)
Description Jeremy Cline 2013-06-19 09:59:12 EDT
Description of problem: when a null repo id is given (--repo-id=) some commands present a validation error to the users, but other commands print the command options again with the message that --repo-id is required and was not specified.

Version-Release number of selected component (if applicable):
[jeremy@jcline ~]$ rpm -q pulp-rpm-admin-extensions 

How reproducible: always

Steps to Reproduce:
1. use '--repo-id=' on any command in the rpm repo content, copy, and remove sections (in the case of copy it's --from-repo-id and --to-repo-id).
2. compare to using '--repo-id=' in the rpm repo update, delete, export, sync, and uploads sections.

Actual results:
[jeremy@jcline ~]$ pulp-admin rpm repo remove rpm --repo-id=
Command: rpm
Description: remove RPMs from a repository

Available Arguments:


The following options are required but were not specified:

[jeremy@jcline ~]$ pulp-admin rpm repo uploads rpm --repo-id=
Validation failed for argument [--repo-id]: value must contain only letters,
numbers, underscores, periods and hyphens

Expected results: A consistent error throughout the commands.

Additional info:
Comment 2 Brian Bouterse 2015-02-28 16:57:15 EST
Moved to https://pulp.plan.io/issues/359

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