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.
Cause: Availability of the "core" package group in selected repositories, required for successfully installation, was not checked before proceeding to the package installation phase.
Consequence: When no selected repository had the "core" package group, installation ended with an exception when proceeding to package installation.
Fix: Check if selected repositories have the "core" package group and if they don't, show a warning dialog instead of proceeding to the next step.
Result: If the selected repositories don't contain the "core" group, a warning dialog is shown and the installation is blocked until a repository containing the "core" group is added.
Description of problem:
Following traceback is displayed when user tries to use only additional repository for the installation:
anaconda 13.21.194 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/iw/task_gui.py", line 529, in <lambda>
"default", False), grps)
File "/usr/lib/anaconda/iw/task_gui.py", line 529, in getNext
"default", False), grps)
File "/usr/lib/anaconda/gui.py", line 1384, in nextClicked
rc = self.currentWindow.getNext ()
AttributeError: 'NoneType' object has no attribute 'default'
Version-Release number of selected component (if applicable):
anaconda-13.21.194
How reproducible:
always
Steps to Reproduce:
1. start installation in graphical mode
2. proceed to the software selection screen
3. unselect "Red Hat Enterprise Linux" repository, which is selected by default
4. select any additional repository, for example "High Availability"
5. click "Next"
Actual results:
anaconda traceback
Expected results:
There should be some warning message, user should be able to go back and select correct repositories.
Comment 3RHEL Program Management
2013-05-06 21:14:50 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
Fixed both in GUI and TUI.
In GUI it now shows a dialog that notifies that none of the selected repositories have the core package group and won't allow to continue the installation until some repos containing the core package group are added.
And in TUI, if none of the repositories specified in kickstart (as there is no standalone repository dialog in TUI) contains the core group, it shows a warning dialog and exits.
Retested with anaconda-13.21.206-1.el6 from compose RHEL6.5-20130924.2. Anaconda doesn't allow the user to continue until base repository is selected.
Thanks, moving to VERIFIED.
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-2013-1588.html
Description of problem: Following traceback is displayed when user tries to use only additional repository for the installation: anaconda 13.21.194 exception report Traceback (most recent call first): File "/usr/lib/anaconda/iw/task_gui.py", line 529, in <lambda> "default", False), grps) File "/usr/lib/anaconda/iw/task_gui.py", line 529, in getNext "default", False), grps) File "/usr/lib/anaconda/gui.py", line 1384, in nextClicked rc = self.currentWindow.getNext () AttributeError: 'NoneType' object has no attribute 'default' Version-Release number of selected component (if applicable): anaconda-13.21.194 How reproducible: always Steps to Reproduce: 1. start installation in graphical mode 2. proceed to the software selection screen 3. unselect "Red Hat Enterprise Linux" repository, which is selected by default 4. select any additional repository, for example "High Availability" 5. click "Next" Actual results: anaconda traceback Expected results: There should be some warning message, user should be able to go back and select correct repositories.