Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
For a RHEV with multiple datacenters, available networks are not loaded for the correct Datacenter.

Version-Release number of selected component (if applicable):
Reproduced with Sat 6.5 snap 15. It worked in some previous snap.

How reproducible:
Deterministic

Steps to Reproduce:
1. Have some RHEV with multiple datacenters
2. Infrastructure -> Compute Resources -> Create
3. Fill in, select some other Datacenter than default, submit
4. Hosts -> Create host
5. Fill in, Deploy on = your RHEV
6. On Interfaces tab, edit interface, open a list of Networks

Actual results:
Different networks choice than expected

Expected results:
List of networks for that datacenter

This was caused by networks disconnected from some of their clusters.
Once the networks were attached in RHV to the selected clusters they showed up in the list.