Bug 1533814

Summary:	GET /api/compute_resources/:id/available_clusters/:cluster_id/available_networks shows all networks in a datacenter
Product:	Red Hat Satellite	Reporter:	Beat Rubischon <brubisch>
Component:	Compute Resources - VMWare	Assignee:	Chris Roberts <chrobert>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.13	CC:	bkearney, chrobert, lhellebr, mhernon, mhulan, oezr, yferszt
Target Milestone:	6.6.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	foreman-1.22.0-0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 19:50:41 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 Beat Rubischon 2018-01-12 09:57:37 UTC

Description of problem:

The API documentation describes an API call to get the networks attached to a VMware cluster:
GET /api/compute_resources/:id/available_clusters/:cluster_id/available_networks
List available networks for a compute resource cluster

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

Satellite 6.2.x

How reproducible:

always

Steps to Reproduce:
1. Create a network in VCenter on Cluster level
2. Query Satellite API

Actual results:

All networks on Datacenter level are listet

Expected results:

Networks on Cluster level are listet

Additional info:

Comment 3 Ondřej Ezr 2019-08-02 08:06:40 UTC

This has been fix in a scope of other BZ - https://bugzilla.redhat.com/show_bug.cgi?id=1489516 and is fixed in Satellite 6.6

Comment 7 Lukáš Hellebrandt 2019-10-02 12:01:42 UTC

Verified with Sat 6.6 snap 23.

Used reproducer from OP, there are only networks in cluster X when listing networks through the "GET /api/compute_resources/:id/available_clusters/X/available_networks" endpoint.

Comment 8 Bryan Kearney 2019-10-22 19:50:41 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3172