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:
When deploying via a compute resource, via a compute profile, settings from the profile are ignored for the network


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


How reproducible:
100%

Steps to Reproduce:
1.Create a compute resource (vmware or ovirt)
2.Create a compute profile and set the network to something other than ovirtmgmt)
3.create a New Host and select the profile created
4.Check the interface settings - name and network are ignored

Actual results:
Name and Network are ignored (not taken from the compute profile)

Expected results:
Name and network would come from the compute profile

Additional info:
See attachments

Created attachment 1236899 [details]
Compute profile

Created attachment 1236900 [details]
New host - using the profile

Created attachment 1236901 [details]
Interface screenshot

Thanks for the report. I'm sorry I couldn't get to this sooner. I think this is a duplicate of BZ 1322047 therefore I'm closing it. If you think I misunderstood this BZ or it's a separate issue, please let me know or reopen this. Otherwise I kindly ask you to watch BZ 1322047 for the progress, there's already a patch that should solve it.

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