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.
DescriptionChristian Kellner
2020-07-28 16:55:12 UTC
Created attachment 1702692[details]
anaconda log
Anaconda version: 33.16.3.14-1.el8
Using "RHEL-8.3.0-20200728.n.0-BaseOS-x86_64-boot.iso" with a minimal kickstart file, supplied via kernel command line "inst.ks=http://<>/test.ks":
lang en_US.UTF-8
keyboard us
timezone UTC
zerombr
clearpart --all --initlabel
autopart
reboot
ostreesetup --nogpg --url=https://kojipkgs.fedoraproject.org/compose/ostree/repo --osname=fedora --remote=fedora --ref=fedora/x86_64/coreos/testing
leads to a crash in anaconda:
Traceback (most recent call last):
File "/sbin/anaconda", line 754, in <module>
anaconda.intf.run()
File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/__init__.py", line 840, in run
self._currentAction.refresh()
File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 379, in refresh
self._createBox()
File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 188, in _createBox
self._updateCompleteness(spoke, update_continue=False)
File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 234, in _updateCompleteness
spoke.selector.set_incomplete(not spoke.completed and spoke.mandatory)
File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/spokes/subscription.py", line 152, in mandatory
return check_cdn_is_installation_source(self.payload)
File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/lib/subscription.py", line 86, in check_cdn_is_installation_source
source_proxy = payload.get_source_proxy()
AttributeError: 'RPMOSTreePayload' object has no attribute 'get_source_proxy'
Had a quick look at the source and I think this is due to change introduce in https://github.com/rhinstaller/anaconda/commit/1f341cb27e77f6383a45ee19b8110ea43929ee87
So basically what happens here is that the OSTree payload object Anaconda uses during an OSTree installation does not have an attribute (a proxy for a DBus object) most of the other payloads have. This case was not addressed, so the code tried to access an attribute that does not exist and crashed.
Should be fixed by the following PR, which fixes the code to survive the missing attribute:
https://github.com/rhinstaller/anaconda/pull/2758
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-2020:4729