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 1229081[details]
Compute Profile
Description of problem:
I have created a Compute profile named "100-Cluster Node".
This profile has 2 network interfaces, both of them using NAT (the libvirt default network and an internal network for my nodes, see pic1).
When I try to create a new host from the WebUI, I select the aforementioned Compute Profile (pic2). However, in the interfaces tab, I noticed that the network of the 1st interface is not the default NAT, but a Bridged interface (pic3)
Except of this problem, MAC address is empty.
Version-Release number of selected component (if applicable):
6.2.4
How reproducible:
100%
Steps to Reproduce:
1. Follow the steps described above
Actual results:
New host interfaces are wrong.
Expected results:
New host interfaces should follow what is specified in the compute profile.
Additional info:
If you try to build the host, if fails with the following error:
Failed to power up a compute Local KVM (Libvirt) instance z1.testenv: Call to virDomainCreateWithFlags failed: Cannot get interface MTU on '': No such device
The error makes perfect sense if you consider the fact that libvirt has no bridges configured.
I suspect that this is only a WebUI bug. When I tried to create the host via the hammer, host was created:
hammer host create --hostgroup="Typical RHEL 7" --compute-resource="Local KVM" --compute-profile="100-Cluster Node" --location "Lab" --root-pass "pass" --organization-id 1 --lifecycle-environment="Production" --content-view "RHEL 7 Latest" --name z1
Host created
Checking the VM details the VM was created the way I want it.
I can confirm that I have the same issue when I provision hosts in vCenter.
I can post a screenshot, but bofore doing so, please turn the attachments as private. I don't want to have them in the wild.
Build: Satellite 6.3 snap 26
Verified.
PFA
1) Compute profile with two NAT interface
2) Host had two NAT interface Host Interfaces tab
3) Host Info from libvirt
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-2018:0336
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-2018:0336
Created attachment 1229081 [details] Compute Profile Description of problem: I have created a Compute profile named "100-Cluster Node". This profile has 2 network interfaces, both of them using NAT (the libvirt default network and an internal network for my nodes, see pic1). When I try to create a new host from the WebUI, I select the aforementioned Compute Profile (pic2). However, in the interfaces tab, I noticed that the network of the 1st interface is not the default NAT, but a Bridged interface (pic3) Except of this problem, MAC address is empty. Version-Release number of selected component (if applicable): 6.2.4 How reproducible: 100% Steps to Reproduce: 1. Follow the steps described above Actual results: New host interfaces are wrong. Expected results: New host interfaces should follow what is specified in the compute profile. Additional info: If you try to build the host, if fails with the following error: Failed to power up a compute Local KVM (Libvirt) instance z1.testenv: Call to virDomainCreateWithFlags failed: Cannot get interface MTU on '': No such device The error makes perfect sense if you consider the fact that libvirt has no bridges configured. I suspect that this is only a WebUI bug. When I tried to create the host via the hammer, host was created: hammer host create --hostgroup="Typical RHEL 7" --compute-resource="Local KVM" --compute-profile="100-Cluster Node" --location "Lab" --root-pass "pass" --organization-id 1 --lifecycle-environment="Production" --content-view "RHEL 7 Latest" --name z1 Host created Checking the VM details the VM was created the way I want it.