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.

Bug 2167327

Summary: convert2rhel may fail due to can not visit static.redhat.com in some areas
Product: Red Hat Enterprise Linux 8 Reporter: Mike Cao <bcao>
Component: convert2rhelAssignee: Michal Bocek <mbocek>
Status: CLOSED ERRATA QA Contact: Upgrades and Supportability <upgrades-and-supportability>
Severity: urgent Docs Contact: Miriam Portman <mportman>
Priority: urgent    
Version: 8.6CC: bcao, ddiblik, fgustavs
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-14 10:02:45 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:

Comment 1 Freya Gustavsson 2023-02-06 13:31:53 UTC
Interesting. Are there any other limitations we should be wary of from the Red Hat domains @bcao?

Comment 2 Mike Cao 2023-02-07 01:11:52 UTC
(In reply to Eric Gustavsson from comment #1)
> Interesting. Are there any other limitations we should be wary of from the
> Red Hat domains @bcao?

I don't know what the limitations are exactly, may all redhat domain with http protocol are blocked.
Changing http to https can fix the issue for now.

Below is the patch I tested

--- systeminfo.py	2023-02-07 09:02:42.183894928 +0800
+++ systeminfo.py	2023-02-07 09:03:51.404448218 +0800
@@ -33,7 +33,7 @@
 CHECK_DBUS_STATUS_RETRIES = 3

 # The address that will be used to check if there is a internet connection.
-CHECK_INTERNET_CONNECTION_ADDRESS = "http://static.redhat.com/test/rhel-networkmanager.txt"
+CHECK_INTERNET_CONNECTION_ADDRESS = "https://static.redhat.com/test/rhel-networkmanager.txt"

 # Allowed conversion paths to RHEL. We want to prevent a conversion and minor
 # version update at the same time.
@@ -364,7 +364,7 @@
         """Check whether or not the machine is connected to the internet.

         This method will try to retrieve a web page on the Red Hat network that
-        we know to exist (http://static.redhat.com/test/rhel-networkmanager.txt).
+        we know to exist (https://static.redhat.com/test/rhel-networkmanager.txt).
         If we can successfully access that page, then we decide we are connected
         to the internet.ully access that page, then we decide we are connected
         to the internet.

Comment 3 Freya Gustavsson 2023-02-09 20:20:55 UTC
Thanks for the information Mike. We decided to push for the https approach to land in the v1.2 that is coming in March. Rodolfo Olivieri already fixed this upstream https://github.com/oamg/convert2rhel/pull/736

In the future we hope to allow the user to get around these checks, but that will not land for v1.2 release

Comment 5 Mike Cao 2023-02-10 00:52:12 UTC
(In reply to Eric Gustavsson from comment #3)
> Thanks for the information Mike. We decided to push for the https approach
> to land in the v1.2 that is coming in March. Rodolfo Olivieri already fixed
> this upstream https://github.com/oamg/convert2rhel/pull/736
> 
> In the future we hope to allow the user to get around these checks, but that
> will not land for v1.2 release

I submit a comment in the upstream

The code comment under def _check_internet_access() still mentioned http instead of https, it should be modified as well.

Mike

Comment 12 Daniel Diblik 2023-03-09 16:25:25 UTC
The bug was verified as a part of automated test suite on versions *convert2rhel-1.1-1.el7.noarch.rpm*/*convert2rhel-1.1-1.el8.noarch.rpm* and *convert2rhel-1.2-2.el7.noarch.rpm*/*convert2rhel-1.2-2.el8.noarch.rpm* with their respective results provided in the JIRA issue comments due to BZ comment limitations.

See https://issues.redhat.com/browse/RHELC-891?focusedCommentId=21861576&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-21861576

Comment 14 errata-xmlrpc 2023-03-14 10:02:45 UTC
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 (convert2rhel bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:1196