Bug 2231126

Summary:	[RFE] Request to have the view 'Restrict to architecture", 'Restrict to OS version', and 'Always update to latest version' with hammer
Product:	Red Hat Satellite	Reporter:	tharring
Component:	Repositories	Assignee:	Partha Aji <paji>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.13.0	CC:	aruzicka, dsinglet, iballou, ofedoren, rlavi
Target Milestone:	Unspecified	Keywords:	EasyFix, FutureFeature, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:26:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description tharring 2023-08-10 16:41:36 UTC

Description of problem:
[RFE]: 

Request to have the option to see the below with 'hammer repository info'
 
 ~~~
 Restrict to architecture
 Restrict to OS version
 ~~~

Request to have the option to see the below with 'hammer content-view info' for the content view which is a part of the composite content view
 
 ~~~
 Always update to latest version
 ~~~

Version-Release number of selected component (if applicable):


How reproducible: Always

Actual results:
The options do not seem to exist in the hammer documentation and are only available via the Web UI

Expected results:
Would like to have the options available with the hammer CLI

Comment 2 Partha Aji 2024-03-07 11:14:50 UTC

Connecting redmine issue https://projects.theforeman.org/issues/37232 from this bug

Comment 3 Bryan Kearney 2024-03-08 00:13:04 UTC

Upstream bug assigned to paji

Comment 4 Bryan Kearney 2024-03-08 00:13:06 UTC

Upstream bug assigned to paji

Comment 5 Bryan Kearney 2024-03-08 20:03:32 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/37232 has been resolved.

Comment 6 Eric Helms 2024-06-06 16:26:24 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.