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.
Description of problem:
Error is shown when interface field are filled in different order.
Version-Release number of selected component (if applicable):
Sat 6.8 snap 10
How reproducible:
Always
Steps to Reproduce:
1. Create domain, and ipv4 subnet with associated domain.
2. Create host -> go directly into interfaces and edit it
3. Firstly fill domain and subnet then type in mac address and click for example into device identifier field. The error below IPv6 address row is shown.
4. It's possible to interface and after filling all other necessary fields also the host is created without error. So it's probably just visual problem.
Actual results:
Below the IPv6 Address row the error is shown: Error generating IP: Bad Request
Expected results:
The error message is not shown.
Additional info:
From my point of view, this is just visual bug.
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 (Important: Satellite 6.8 release), 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-2020:4366