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.

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

I just tested this on Sat 6.1, and when networks are selected (annoyingly, this is done in the Virtual Machine tab) instance creation works right. I believe this bug can be closed, we might want to consider moving the network UI from the VM tab to the networking tab in the next version.

Created attachment 1037133 [details]
screenshot of the selected networks and the success status of the instance creation

screenshot of the selected networks and the success status of the instance creation

*** This bug has been marked as a duplicate of bug 1229901 ***

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days