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 1656702 - Unexpected warning message 'Repository x does not match selected protocol' when adding a new repository in Installation Source
Summary: Unexpected warning message 'Repository x does not match selected protocol' wh...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: anaconda
Version: 9.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: beta
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
: 1656703 1753945 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-06 06:31 UTC by Lijun Li
Modified: 2022-01-08 07:26 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-08 07:26:59 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Unexpected warning message 'Repository x does not match selected protocol' when adding a new repository in Installation Source (117.57 KB, image/png)
2018-12-06 06:31 UTC, Lijun Li
no flags Details
anaconda.log (1.45 KB, text/plain)
2018-12-10 03:46 UTC, Lijun Li
no flags Details
dbus.log (2.54 KB, text/plain)
2018-12-10 03:47 UTC, Lijun Li
no flags Details
program.log (131 bytes, text/plain)
2018-12-10 03:49 UTC, Lijun Li
no flags Details

Description Lijun Li 2018-12-06 06:31:28 UTC
Created attachment 1511961 [details]
Unexpected warning message 'Repository x does not match selected protocol' when adding a new repository in Installation Source

Description of problem:
Unexpected warning message 'Repository x does not match selected protocol' when adding a new repository in Installation Source

Version-Release number of selected component (if applicable):
anaconda-29.19.0.26-1.el8.x86_64.rpm 

How reproducible:
100%

Steps to Reproduce:
1. Install latest rhel8 build from BaseOS via network installation.
2. Next and click to Installation Source page.
3. Click + to add a new repository under Additional repositories.
4. Input the Name.
5. Copy and paste the AppStream http repo link.

Actual results:
1. Unexpected warning message 'Repository x does not match selected protocol' when adding a new repository in Installation Source.
2. Select any other protocol (ex https://) and then select back to http://, the warning message 'Repository x does not match selected protocol' disappeared.

Expected results:
No such warning message.

Additional info:
Please see the attached screen shot.

Comment 1 Jens Petersen 2018-12-06 06:40:57 UTC
*** Bug 1656703 has been marked as a duplicate of this bug. ***

Comment 2 Jiri Konecny 2018-12-07 09:13:38 UTC
Could you please provide us logs from the installation environment.

You can find them in /tmp/*.log.

Comment 3 Jens Petersen 2018-12-07 09:40:08 UTC
(As I noted in my bug report: this is not a new issue - I think it is
also true for RHEL 7 and likely even 6... and easily reproduced)

Also it is easily worked around, which is likely why noone reported before:
but quite annoying really.

Comment 4 Lijun Li 2018-12-10 03:45:09 UTC
(In reply to Jiri Konecny from comment #2)
> Could you please provide us logs from the installation environment.
> 
> You can find them in /tmp/*.log.

Please see the attachments.

Thanks,
Robert

Comment 5 Lijun Li 2018-12-10 03:46:24 UTC
Created attachment 1512944 [details]
anaconda.log

Comment 6 Lijun Li 2018-12-10 03:47:38 UTC
Created attachment 1512945 [details]
dbus.log

Comment 7 Lijun Li 2018-12-10 03:49:18 UTC
Created attachment 1512946 [details]
program.log

Comment 11 Jan Stodola 2020-02-12 19:22:41 UTC
*** Bug 1753945 has been marked as a duplicate of this bug. ***

Comment 15 RHEL Program Management 2021-02-01 07:30:57 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 16 Jens Petersen 2021-07-08 04:32:13 UTC
Why is this bug not a priority?

Comment 19 RHEL Program Management 2022-01-08 07:26:59 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.