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 1929008 - Configuring a network team and vlan via anaconda results in a traceback when anaconda attempts to write out the kickstart
Summary: Configuring a network team and vlan via anaconda results in a traceback when ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Radek Vykydal
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-16 00:40 UTC by Ryan Mullett
Modified: 2024-12-20 19:38 UTC (History)
8 users (show)

Fixed In Version: anaconda-33.16.5.2-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 18:42:11 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5807701 0 None None None 2021-02-16 18:16:22 UTC
Red Hat Knowledge Base (Solution) 5872751 0 None None None 2021-09-16 18:14:03 UTC
Red Hat Product Errata RHBA-2021:4254 0 None None None 2021-11-09 18:42:34 UTC

Description Ryan Mullett 2021-02-16 00:40:41 UTC 
Description of problem:
During anaconda installation, when installing with a team+vlan

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

How reproducible:
Always

Steps to Reproduce:
1. Boot a system with two network interfaces and begin RHEL 8.3 installation
2. Create team device, and add the two network interfaces. Ensure that ipv4 and ipv6 are set to not get IP addresses
3. Create VLAN device, using the team device as the underlying device
4. Assign port
5. Continue installation

Actual results:
Installation fails with traceback:

17:09:11,677 CRT exception: Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/pyanaconda/threading.py", line 280, in run
    threading.Thread.run(self)
  File "/usr/lib64/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/installation.py", line 394, in run_installation
    queue.start()
  File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 311, in start
    item.start()
  File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 311, in start
    item.start()
  File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 311, in start
    item.start()
  File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 490, in start
    self.run_task()
  File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 456, in run_task
    self._task(*self._task_args, **self._task_kwargs)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 456, in run_task
    self._task(*self._task_args, **self._task_kwargs)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/installation.py", line 71, in _writeKS
    f.write(str(ksdata))
  File "/usr/lib64/python3.6/site-packages/pyanaconda/kickstart.py", line 438, in __str__
    modules = proxy.GenerateKickstart().strip()
  File "/usr/lib/python3.6/site-packages/dasbus/client/handler.py", line 447, in _call_method
    **kwargs,
  File "/usr/lib/python3.6/site-packages/dasbus/client/handler.py", line 477, in _get_method_reply
    return self._handle_method_error(error)
  File "/usr/lib/python3.6/site-packages/dasbus/client/handler.py", line 497, in _handle_method_error
    raise exception from None
dasbus.error.DBusError: must be str, not NoneType


Expected results:
Installation proceeds normally

Additional info:
Tried the following tests in order to narrow down the issue, and confirm that it is solely related to attempting to write out the kickstart configuration

1. Booting with inst.nosave=output_ks works around the issue entirely, and the system is installed normally with no traceback

2. Initially I was adding the connection name in the name of the teamed interfaces. I attempted changing this to have a different name. No matter the names of the interfaces it fails

3. Installing without vlan configured, and just team with ipv4/ipv6 disabled on a team - installation fails

4. Installing with team configured, with ipv4 enabled and ipv6 disabled - installation fails

5. Installing with team configured, with ipv4 and ipv6 enabled - installation fails

The results of these tests seem to indicate that it is solely related to anaconda attempting to write out this kickstart configuration, and not anything else. When booting with inst.nosave=output_ks, I was able to confirm that network configuration is written out properly, and that the network is able to come up without issue.
Comment 2 Radek Vykydal 2021-02-16 11:51:41 UTC 
Fixed upstream by https://github.com/rhinstaller/anaconda/pull/2927.
The first part of the commit could be ported to RHEL 8.
Comment 4 Radek Vykydal 2021-05-18 15:22:16 UTC 
https://github.com/rhinstaller/anaconda/pull/3384
Comment 14 errata-xmlrpc 2021-11-09 18:42:11 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 (anaconda bug fix and enhancement update), 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/RHBA-2021:4254
Note You need to log in before you can comment on or make changes to this bug.