Bug 2056936 - Installation source page complains about protocols errorneously
Summary: Installation source page complains about protocols errorneously
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: anaconda
Version: 9.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-22 11:54 UTC by Michal Karm Babacek
Modified: 2023-07-23 07:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Installation source page (64.40 KB, image/png)
2022-02-22 11:54 UTC, Michal Karm Babacek
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-114334 0 None None None 2022-03-03 11:07:34 UTC

Description Michal Karm Babacek 2022-02-22 11:54:53 UTC
Created attachment 1862587 [details]
Installation source page

Description of problem:
Installation source page complains about protocols: e.g.
"AppStream url protocol does not match"

The error iterates over all those repos, as you delete/paste again.

There might be some confusion or a race condition with the feature that automatically removes the protocol prefix from the URL I am pasting...

Version-Release number of selected component (if applicable):
9.0.0-20220217.0-BaseOS-x86_64-boot.iso

How reproducible:
Always

Steps to Reproduce:
1. Use new iso in KVM
2. Run graphical installer

Actual results:
It takes re-copy-pasting URLs again, leaving the page and entering the page again to make it work.

Expected results:
It just takes the URL and works.

Additional info:
Screenshot attached with the working state.

Comment 1 Jens Petersen 2022-06-22 08:18:46 UTC
Another workaround is just to change the protocol to https (and switch back to http if you wish).

This is a rather old bug by now... (also happens in RHEL8 of course, and earlier I think)
that ought not to be that hard to fix one would think.


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