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:
updating a NIC's "Device identifier" if it doesn't already have one fails if the "Device identifier" includes a . or :


Version-Release number of selected component (if applicable):
sat6.2

How reproducible:
100%

Steps to Reproduce:
1. Create a new ( dont set Device identifier on the NIC)
2. edit host and try to set Device identifier to eth1:210 for example
3.

Actual results:
Error: Can't add or remove : from identifier

Expected results:
to be able to set it.


Additional info:

Upstream bug component is Orchestration

Upstream bug component is Orchestration

Upstream bug component is Networking

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16935 has been resolved.

Created attachment 1313995 [details]
Updated interface

Verified.

6.3.0 snap 11

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