Bug 1620176 - hammer compute-resource network does not filter by cluster-id param
Summary: hammer compute-resource network does not filter by cluster-id param
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.3.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On: 1426592 1489516
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-22 15:25 UTC by John Berninger
Modified: 2019-10-02 16:07 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-02 16:07:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description John Berninger 2018-08-22 15:25:42 UTC
Description of problem:
When invoking the `hammer compute-resource networks` command it requires both an ID (of the compute resource) and a cluster ID (of the cluster inside that compute resource). The results are not limited to the specified cluster ID, and instead contain a list of networks throughout the compute resource. This is seen when running against a VMware type compute resource

Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli-0.11.0.1-1.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Configure a VMware type Compute Resource in Satellite that contains multiple clusters
2. Issue `hammer compute-resource networks --id 1 --cluster-id 0`
3. See all networks for all clusters within that compute resource
4. Issue `hammer compute-resource networks --id 1 --cluster-id 1`
5. See the same output

Actual results:
List of network for all clusters within the compute resource

Expected results:
List of networks for only the specified cluster.

Additional info:

Comment 2 Chris Roberts 2018-09-04 18:52:55 UTC
Related to:

https://bugzilla.redhat.com/show_bug.cgi?id=1426592

Comment 3 Bryan Kearney 2019-09-03 19:06:53 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 4 Bryan Kearney 2019-10-02 16:07:59 UTC
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, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.


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