Issue #348
closed
pulp-admin client should validate repository listings and return an error if an invalid repo name is given.
Description
Description of problem:
If an admin fat-fingers a repository name, no error is given.
Version-Release number of selected component (if applicable):
2.1.0
How reproducible:
always.
Steps to Reproduce:
1.create repository
2. sync repository
3. see status of repository with typo in name
Actual results:
In the below example, this repository doesn't exist.
[root@mis5labsrv ~]# pulp-admin rpm repo sync run --repo-id fake-repo
--------------------------------------------------------------------
Synchronizing Repository [fake-repo]
--------------------------------------------------------------------
The following resource(s) could not be found:
fake-repo (repo_id)
[root@mis5labsrv ~]# pulp-admin rpm repo sync status --repo-id fake-repo
--------------------------------------------------------------------
Repository Status [fake-repo]
--------------------------------------------------------------------
The repository is not performing any operations
Expected results:
status should also tell you that the repository doesn't exist.
Additional info:
+ This bug was cloned from Bugzilla Bug #951685 +
Updated by cduryee almost 9 years ago
This is still outstanding as of 2.4.3.
$ pulp-admin rpm repo sync status --repo-id fake-repo
--------------------------------------------------------------------
Repository Status [fake-repo]
--------------------------------------------------------------------
The repository is not performing any operations
+ This comment was cloned from Bugzilla #951685 comment 1 +
Updated by bmbouter over 4 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter over 4 years ago
- Severity set to 1. Low
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
.