Bug 1474971

Summary: Anaconda: unknown error during VLAN addition
Product: Red Hat Enterprise Linux 7 Reporter: Yaroslav <ykargin>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-15 07:40:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda log none

Description Yaroslav 2017-07-25 17:55:31 UTC 
Created attachment 1304369 [details]
anaconda log

Description of problem:
13:45:45,769 CRIT anaconda: Traceback (most recent call last):

  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py", line 563, in on_new_connection
    self.add_connection_to_list(connection.get_uuid())

  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py", line 465, in add_connection_to_list
    uuid, existing_dev_cfg.con_uuid, existing_dev_cfg.device.get_iface())

AttributeError: 'NoneType' object has no attribute 'get_iface'



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


How reproducible:
100%

Steps to Reproduce:
1. Start new installation, goto anaconda networking screen
2. in my case there is just 1 NIC with DHCP enabled, turn it on
3. add VLAN with ID 444
4. Remove it
5. Add VLAN with same ID again.

Actual results:
An unknown error has occurred

Expected results:
VLAN added.

Additional info:
anaconda.log attached. Looks loke affected all EL7 including latest beta
Comment 3 RHEL Program Management 2021-01-15 07:40:17 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.