Bug 1656702

Summary: Unexpected warning message 'Repository x does not match selected protocol' when adding a new repository in Installation Source
Product: Red Hat Enterprise Linux 9 Reporter: Lijun Li <lijli>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.0CC: jkonecny, jrusz, jstodola, lijli, peter, petersen, qe-i18n-bugs, zveleba
Target Milestone: betaKeywords: Improvement, Reopened
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-08 07:26:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Unexpected warning message 'Repository x does not match selected protocol' when adding a new repository in Installation Source
none
anaconda.log
none
dbus.log
none
program.log none

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.