Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1428848[details]
foreman debug
Description of problem: I created a host group and associated a compute profile with it to attach Libvirt vms to "foreman" interface
Version-Release number of selected component (if applicable): 6.4
How reproducible: Always
Steps to Reproduce:
1. Create libvirt compute profile. Set attached network interface
2. Associate compute profile with hostgroup
3. Create a vm with hostgroup
Actual results: The compute profile is selected in the UI, but the network interface config is incorrect
Expected results: Network interface config from compute profile is used.
Additional info: attached foreman-debug take after creating host with compute profile, but incorrect network config which led to an error :
Failed to power up a compute locallibvirt (Libvirt) instance kathy-smeenk.lab.eng.rdu2.redhat.com: Call to virDomainCreateWithFlags failed: Cannot get interface MTU on '': No such device
Created attachment 1428848 [details] foreman debug Description of problem: I created a host group and associated a compute profile with it to attach Libvirt vms to "foreman" interface Version-Release number of selected component (if applicable): 6.4 How reproducible: Always Steps to Reproduce: 1. Create libvirt compute profile. Set attached network interface 2. Associate compute profile with hostgroup 3. Create a vm with hostgroup Actual results: The compute profile is selected in the UI, but the network interface config is incorrect Expected results: Network interface config from compute profile is used. Additional info: attached foreman-debug take after creating host with compute profile, but incorrect network config which led to an error : Failed to power up a compute locallibvirt (Libvirt) instance kathy-smeenk.lab.eng.rdu2.redhat.com: Call to virDomainCreateWithFlags failed: Cannot get interface MTU on '': No such device