RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 761026 - vlan id should not accept a space in it
Summary: vlan id should not accept a space in it
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.2
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 761537
TreeView+ depends on / blocked
 
Reported: 2011-12-07 15:35 UTC by Joey Boggs
Modified: 2018-11-14 09:36 UTC (History)
14 users (show)

Fixed In Version: ovirt-node-2.2.1-1.el6
Doc Type: Bug Fix
Doc Text:
Previously, it was possible to enter invalid characters in the VLAN ID field, which led to network failures. Now, the VLAN ID field is automatically checked to ensure it does not contain any invalid characters.
Clone Of:
Environment:
Last Closed: 2012-07-19 14:16:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0741 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2012-07-19 18:10:46 UTC

Description Joey Boggs 2011-12-07 15:35:05 UTC 
vlanid with a space in it will be accepted and will fail to configure properly.
Comment 5 Mike Burns 2012-01-12 23:50:52 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The vlan id field allowed spaces which are not valid characters.  This led to failures in the network.  The field has been updated to check for spaces now and disallow them.
Comment 6 Tim Hildred 2012-01-25 01:19:07 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1,3 @@
-The vlan id field allowed spaces which are not valid characters.  This led to failures in the network.  The field has been updated to check for spaces now and disallow them.+Previously, it was possible to enter invalid characters in the VLAN ID field, which led to network failures. 
+
+Now, the VLAN ID field is automatically checked to ensure it does not contain any invalid characters.
Comment 7 shine 2012-02-22 04:33:42 UTC 
Verified on 6.3-20120215 build, it reports "invalid vlan ID" when Vlan ID with spaces.
Comment 9 errata-xmlrpc 2012-07-19 14:16:44 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2012-0741.html
Note You need to log in before you can comment on or make changes to this bug.