Red Hat Bugzilla – Bug 623641
Duplicate repo error after cancelling network enablement invoked by adding/editing a repo.
Last modified: 2011-05-19 08:34:05 EDT
+++ This bug was initially created as a clone of Bug #623639 +++
Description of problem:
When adding/editing repo in UI, if the network enablement is required, and device selection dialog is cancelled, next try ([Ok]) within the same Add Repository dialog causes "The repository ... has already been added" error.
Version-Release number of selected component (if applicable):
F14 Alpha RC2
Steps to Reproduce:
1. Start DVD install without using network.
2. In repo UI add network requiring repo, "Select Network Interface" dialog appears, press "Cancel"
3. In Add Repository dialog press "Ok"
error message "The repository ... has already been added..."
"Select Network Interface" dialog appears (or appropriate action is taken if the repository was modified in step 3 before pressing "Ok"
If bug #623149 is not fixed yet, this traceback https://bugzilla.redhat.com/show_bug.cgi?id=623017#c3 occurs instead of the error message.
--- Additional comment from firstname.lastname@example.org on 2010-08-12 07:46:25 EDT ---
Sending a patch to anaconda devel list.
Not for 6.0, quite a corner case.
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
This should be fixed in version 13.21.84-1 of anaconda.
In snap #2 if you press Cancel and do not enable the network the next time you click OK to add the repository the network config screen pops up again.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.