Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
This seems to be regression compared to 8.2.
When configuring a bond on the kernel command line, the following backtrace is seen after anaconda starts:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
anaconda 33.16.3.26-1.el8 for Red Hat Enterprise Linux 8.3 started.
* installation log files are stored in /tmp during the installation
* shell is available on TTY2
* if the graphical installation interface fails to start, try again with the
inst.text bootoption to start text installation
* when reporting a bug add logs from /tmp as separate text/plain attachments
Traceback (most recent call last):
File "/sbin/anaconda", line 555, in <module>
initialize_network()
File "/usr/lib64/python3.6/site-packages/pyanaconda/network.py", line 290, in
initialize_network
run_network_initialization_task(network_proxy.DumpMissingIfcfgFilesWithTask())
File "/usr/lib64/python3.6/site-packages/pyanaconda/network.py", line 268, in
run_network_initialization_task
sync_run_task(task_proxy)
File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/common/task/__init__.py", line 46, in sync_run_task
task_proxy.Finish()
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: 'NoneType' object has no attribute 'set_property'
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
This prevents installing.
Version-Release number of selected component (if applicable):
anaconda-33.16.3.26-1.el8
How reproducible:
Always
Steps to Reproduce:
1. Set up a VM with 2 network interfaces on same network
- disconnect link 2 for convenience if you don't have real bonding available (my case)
2. Boot on the network using the following bond configuration
ip=bond0:dhcp bond=bond0:enp1s0,enp2s0:mode=active-backup
Actual results:
Traceback
Expected results:
No traceback
Additional info:
Doesn't happen on RHEL8.1, 8.2 and 7.9
(In reply to Masahiro Matsuya from comment #7)
> The one line fix is in upstream:
>
> https://github.com/rhinstaller/anaconda/commit/
> a3e46c49216f76f73097587b15ded52b253ce3d2
>
> NM.SettingWired is not used for bond device. So, get_setting_wired() doesn't
> return anything.
>
> RHEL 8.4 Beta has already had the fix. So, it doesn't happen in RHEL8.4 Beta.
>
Thank you for the debugging.
The rhel-8 commit is in
https://github.com/rhinstaller/anaconda/pull/2938
and I agree that it should fix this BZ.
Just a note that this can be reproduced on RHEL-8.3 when the bond device configuration is before the ip= argument on the kernel command line:
bond=bond0:enp1s0,enp2s0:mode=active-backup ip=bond0:dhcp
I wasn't able to reproduce with the order "ip=bond0:dhcp bond=... "
Description of problem: This seems to be regression compared to 8.2. When configuring a bond on the kernel command line, the following backtrace is seen after anaconda starts: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- anaconda 33.16.3.26-1.el8 for Red Hat Enterprise Linux 8.3 started. * installation log files are stored in /tmp during the installation * shell is available on TTY2 * if the graphical installation interface fails to start, try again with the inst.text bootoption to start text installation * when reporting a bug add logs from /tmp as separate text/plain attachments Traceback (most recent call last): File "/sbin/anaconda", line 555, in <module> initialize_network() File "/usr/lib64/python3.6/site-packages/pyanaconda/network.py", line 290, in initialize_network run_network_initialization_task(network_proxy.DumpMissingIfcfgFilesWithTask()) File "/usr/lib64/python3.6/site-packages/pyanaconda/network.py", line 268, in run_network_initialization_task sync_run_task(task_proxy) File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/common/task/__init__.py", line 46, in sync_run_task task_proxy.Finish() 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: 'NoneType' object has no attribute 'set_property' -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- This prevents installing. Version-Release number of selected component (if applicable): anaconda-33.16.3.26-1.el8 How reproducible: Always Steps to Reproduce: 1. Set up a VM with 2 network interfaces on same network - disconnect link 2 for convenience if you don't have real bonding available (my case) 2. Boot on the network using the following bond configuration ip=bond0:dhcp bond=bond0:enp1s0,enp2s0:mode=active-backup Actual results: Traceback Expected results: No traceback Additional info: Doesn't happen on RHEL8.1, 8.2 and 7.9