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.
DescriptionFred van Zwieten
2015-03-02 08:31:57 UTC
Description of problem:
When editing an existing (bare metal) Host with an already filled in mac address, it is not possible to save the changes because the mac address is already in use. This is with DHCP integration on the capsule
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create/Deploy bare metal host using capsule with DHCP integration. Specify the correct mac address.
2. After deployment, edit the Host and change some filed (however, not the mac address) field
3.
Actual results:
Cannot save because mac address is already in use
Expected results:
Saved
Additional info:
Comment 1RHEL Program Management
2015-03-02 14:24:42 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
I just tested it with latest develop, and it seems like this may have been fixed in the networking feature.
Can you retest this with latest Sat build, to see if it works as expected?
Verified with sat6.2 beta snap6.2.
I provisioned a host (discovered host to mimic bare-metal provisioning) and edited the same host and defined virtual interfaces. Interfaces were created successfully and didn't see the "mac address is already in use" error.
Later, I rebuild the host to see configured interfaces on host
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/RHBA-2016:1500