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 1702925[details]
Error message when running FDI on IPv6 only network
Description of problem:
During host discovery using HTTP Boot on IPv6 only network the following issues were "discovered".
- Foreman Discovery Image (FDI) doesn't show IPv6 address by default. After boot there is a message "Primary IPv4: N/A", but no mention of IPv6 address. The IPv6 address can be found in the "Facts" section, though. This is more of a cosmetic issue, but having the IPv6 address displayed by default would be nice.
- FDI configures the IPv6 address automatically, but is doesn't get DNS server address from the DHCPv6 server. There is no /etc/resolv.conf present, actually. That makes discovery impossible, as the host is unable to resolve Discovery server address. Enabling the SSH console and running "dhclient -6" manually creates /etc/resolv.conf and configures the IPv6 DNS server.
- Even after manual config of an IPv6 DNS server, the registration itself fails with the following error:
ERF42-9331 [Foreman::Exception]: Unable to find primary NIC with <MAC-ADDRESS-OF-THE-HOST> specified via...
See the attached screenshot for the exact message.
Version-Release number of selected component (if applicable):
Foreman Discovery Image v3.6.1
tfm-rubygem-smart_proxy_discovery-1.0.5-5.el7sat.noarch
foreman-discovery-image-service-1.0.0-3.el7sat.x86_64
tfm-rubygem-smart_proxy_discovery_image-1.2.0-1.el7sat.noarch
tfm-rubygem-foreman_discovery-16.1.0-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_discovery-1.0.2-1.el7sat.noarch
foreman-discovery-image-3.6.1-1.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
1. You need an IPv6-only environment built by instruction provided here - https://github.com/theforeman/foreman-documentation/pull/116/files
2. Enable and configure HTTP Boot
3. Configure Discovery as described in the official Satellite documentation
4. Do a network boot using HTTP Boot and run FDI.
Actual results:
See above
Expected results:
The host is discovered successfully.
Additional info:
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.