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 990824[details]
see interface can be created without specifying identifier
Description of problem:
I can create alias and bond interfaces without specifying identifier. I think its required to link the virtual interface with the physical one.
If we don't pass identifier then I think it won't be configured on provisioned host via config template.
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150210.0
Sat6.1.0 beta snap2
How reproducible:
always
Steps to Reproduce:
1. Add_interface of type Bond and alias
2.
3.
Actual results:
Alias and bond Interfaces can be created without interface identifier
Expected results:
User should get validation error as identifier are required for linking purpose.
Additional info:
Moving to POST since upstream bug http://projects.theforeman.org/issues/9429 has been closed
-------------
Marek Hulán
Applied in changeset commit:4feb1576f820b08712afd58a41b01cdfc2f9d600.
Moving to POST since upstream bug http://projects.theforeman.org/issues/9429 has been closed
-------------
Marek Hulán
Applied in changeset commit:4feb1576f820b08712afd58a41b01cdfc2f9d600.
verified with:
sat6.1 beta snap6 compose2 (Satellite-6.1.0-RHEL-6-20150311.1).
Now if user creates managed alias and bond interfaces without specifying identifier, UI throws error that identifier can't be blank. Thanks for fixing this. Please see the screenshot for verification.
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-2015:1592
Created attachment 990824 [details] see interface can be created without specifying identifier Description of problem: I can create alias and bond interfaces without specifying identifier. I think its required to link the virtual interface with the physical one. If we don't pass identifier then I think it won't be configured on provisioned host via config template. Version-Release number of selected component (if applicable): Satellite-6.1.0-RHEL-6-20150210.0 Sat6.1.0 beta snap2 How reproducible: always Steps to Reproduce: 1. Add_interface of type Bond and alias 2. 3. Actual results: Alias and bond Interfaces can be created without interface identifier Expected results: User should get validation error as identifier are required for linking purpose. Additional info: