Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1191953 - user shouldn't be allowed to create alias and bond interfaces without specifying identifer
user shouldn't be allowed to create alias and bond interfaces without specify...
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: WebUI (Show other bugs)
6.1.0
Unspecified Unspecified
medium Severity medium (vote)
: Unspecified
: Unused
Assigned To: Marek Hulan
Sachin Ghai
http://projects.theforeman.org/issues...
: Triaged
Depends On:
Blocks: 1193987
  Show dependency treegraph
 
Reported: 2015-02-12 04:54 EST by Sachin Ghai
Modified: 2017-02-23 15:32 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-12 01:24:46 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
see interface can be created without specifying identifier (19.90 KB, image/png)
2015-02-12 04:54 EST, Sachin Ghai
no flags Details
creating an alias interface without identifier throws error on UI (40.76 KB, image/png)
2015-03-17 03:07 EDT, Sachin Ghai
no flags Details
creating a bond interface without identifier throws error on UI (54.50 KB, image/png)
2015-03-17 03:08 EDT, Sachin Ghai
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 9429 None None None 2016-04-22 11:12 EDT
Red Hat Product Errata RHSA-2015:1592 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 05:04:35 EDT

  None (edit)
Description Sachin Ghai 2015-02-12 04:54:02 EST
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:
Comment 2 Marek Hulan 2015-02-18 09:14:35 EST
Created redmine issue http://projects.theforeman.org/issues/9429 from this bug
Comment 3 Bryan Kearney 2015-02-19 10:07:57 EST
Moving to POST since upstream bug http://projects.theforeman.org/issues/9429 has been closed
-------------
Marek Hulán
Applied in changeset commit:4feb1576f820b08712afd58a41b01cdfc2f9d600.
Comment 6 Bryan Kearney 2015-02-25 06:05:00 EST
Moving to POST since upstream bug http://projects.theforeman.org/issues/9429 has been closed
-------------
Marek Hulán
Applied in changeset commit:4feb1576f820b08712afd58a41b01cdfc2f9d600.
Comment 9 Sachin Ghai 2015-03-09 04:58:36 EDT
Verification of this bz is blocked due to bz 1198925.
Comment 10 Sachin Ghai 2015-03-17 03:06:34 EDT
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.
Comment 11 Sachin Ghai 2015-03-17 03:07:32 EDT
Created attachment 1002667 [details]
creating an alias interface without identifier throws error on UI
Comment 12 Sachin Ghai 2015-03-17 03:08:27 EDT
Created attachment 1002668 [details]
creating a bond interface without identifier throws error on UI
Comment 13 Bryan Kearney 2015-08-11 09:31:24 EDT
This bug is slated to be released with Satellite 6.1.
Comment 14 errata-xmlrpc 2015-08-12 01:24:46 EDT
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

Note You need to log in before you can comment on or make changes to this bug.