Project

Profile

Help

Issue #1784

closed

regression: "pulp-admin rpm repo search" with filters does not work as expected

Added by gmbnomis about 8 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.8.0
Platform Release:
2.8.3
OS:
CentOS 7
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

on a freshly installed Pulp 2.8.0 install (CentOS 7), pulp-admin behaves different to 2.7.1 when searching RPM repos.

There is a single RPM repo with id "sum42" on Pulp. Searching for it using the example syntax given in the command's help text yields nothing:

$ pulp-admin rpm repo search --fields id --str-eq="id=sum42"
+----------------------------------------------------------------------+
                              Repositories
+----------------------------------------------------------------------+

However, using "repo_id" as attribute name works:

$ pulp-admin rpm repo search --fields id --str-eq="repo_id=sum42"
+----------------------------------------------------------------------+
                              Repositories
+----------------------------------------------------------------------+

Id:           sum42

Interestingly, a raw JSON Mongo filter seems to accept both "id" and "repo_id":

$ pulp-admin rpm repo search --fields id --filters '{"id": "sum42"}'
+----------------------------------------------------------------------+
                              Repositories
+----------------------------------------------------------------------+

Id:           sum42

Also available in: Atom PDF