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.
DescriptionJoniel Pasqualetto
2019-06-26 13:27:00 UTC
Created attachment 1584822[details]
Screenshot showing what nic should be selected to reproduce the issue
Description of problem:
When all following conditions are met, provisioned host won't get a subnet assigned.
Here are the conditions:
- a discovered host has multiple nics (2 are already enough)
- nic used to discover is the first in the list of available nics when booting the FDI (see attached image)
- when provisioning, no customization is done in the interfaces to assign a subnet manually
- hostgroup doesn't force a subnet, only a domain
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. Create a hostgroup with NO SUBNET.
2. Create a VM with multiple NICs
3. Boot the VM using the discovery image and ensure you use the first NIC in the list of available nics to boot (see attached image)
4. Use quick submit provisioning with the hostgroup configured in the step 1
5. Check the subnet association of the created host ( Edit -> interfaces -> choose the nic ) and see there is none.
Actual results:
- host has no subnet assigned, actually blocking the provisioning (template rendering failing because there is no subnet).
Expected results:
- host would have the discovered subnet assigned
Additional info:
1. If you do the same steps, but use another nic to discover (the second in the list, for example), the discovered subnet will be assigned
2. In Satellite 6.5 behavior seems to be the same.
3. In Satellite 6.3.5, no such behavior is observed and host always get a subnet.
This is a known bug: when Subnet is changed via UI, discovery form does NOT request new IP address from the subnet range. There is some work in progres to implement this at least for autoprovisioning. There are some technical limitations.
Workaround for the UI: click on Unused IP button to get correct IP address after Subnet is set.
*** This bug has been marked as a duplicate of bug 1367549 ***
Created attachment 1584822 [details] Screenshot showing what nic should be selected to reproduce the issue Description of problem: When all following conditions are met, provisioned host won't get a subnet assigned. Here are the conditions: - a discovered host has multiple nics (2 are already enough) - nic used to discover is the first in the list of available nics when booting the FDI (see attached image) - when provisioning, no customization is done in the interfaces to assign a subnet manually - hostgroup doesn't force a subnet, only a domain Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Create a hostgroup with NO SUBNET. 2. Create a VM with multiple NICs 3. Boot the VM using the discovery image and ensure you use the first NIC in the list of available nics to boot (see attached image) 4. Use quick submit provisioning with the hostgroup configured in the step 1 5. Check the subnet association of the created host ( Edit -> interfaces -> choose the nic ) and see there is none. Actual results: - host has no subnet assigned, actually blocking the provisioning (template rendering failing because there is no subnet). Expected results: - host would have the discovered subnet assigned Additional info: 1. If you do the same steps, but use another nic to discover (the second in the list, for example), the discovered subnet will be assigned 2. In Satellite 6.5 behavior seems to be the same. 3. In Satellite 6.3.5, no such behavior is observed and host always get a subnet.