Description of problem: hammer srpm list using product which have more than one repo fails with error 'Found more than one repository' Version-Release number of selected component (if applicable): @Satellite 6.7.0 snap 3.0 How reproducible: Always Steps to Reproduce: 1. Create a Product and add two yum repos in it. 2. Now try to list SRPM as below: # hammer srpm list --organization=<org_name> --product-id=<Product_id> Actual results: Error: Found more than one repository. Expected results: Should be able to see SRPM packages list
same is happing with 'package list' as well: [root@hp-dl180-04 ~]# hammer package list --organization-id 1 --product=Prod1 Error: Found more than one repository. [root@hp-dl180-04 ~]#
Hey Vijay, Hammer (nor our api) has never supported listing packages/srpms or any type of content by product. Those --product options are there to help resolve the repository by name, so you could do something like: # hammer srpm list --organization=<org_name> --product-id=<Product_id> --repository="Repo Name" The api has never supported fetching these things by product, and so hammer never has either. I tested 6.5 and see the same behavior as you see in 6.7. I will agree that the error message is not good, it should say something like: "More than one repository within the product, please specify repository", or possibly even just "PLease specify repository" if not repository name or id is given at all. Given this, is this bug really high priority, or can we de-prioritize it? Thanks! Justin
Hey Justin, Thanks for the update , you are right this is not working under 6.5 too (hence it was not marked as regression too) ... as error is bit misleading so looks more a bug around that only and after updating the error/message it would be fine too. As this is expected behaviour then I'll update automation accordingly ..for now priority is low for it.
Thanks Vijay, I'll remove automation blocker too for now. Thanks!
All, Based upon the discussion, I am placing this bugzilla on sat-backlog for now. I also added the UserExperience keyword to indicate that the lack of good error message does impact the user.
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.