This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 1965487 - convert2rhel does not work with a proxy in the environment.
Summary: convert2rhel does not work with a proxy in the environment.
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: convert2rhel
Version: 8.3
Hardware: All
OS: All
high
urgent
Target Milestone: beta
: ---
Assignee: Michal Bocek
QA Contact: upgrades-and-conversions
Miriam Portman
URL:
Whiteboard:
Depends On:
Blocks: 1818088
TreeView+ depends on / blocked
 
Reported: 2021-05-27 19:26 UTC by jcastran
Modified: 2023-09-12 11:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Systems that connect to the Internet using an HTTP proxy server cannot convert using Red Hat CDN or Satellite through RHSM. To work around this problem, enable HTTP proxy for yum and then configure the HTTP proxy for RHSM: Configure yum to use an HTTP proxy as described in How to enable Proxy settings for Yum Command on RHEL? For Oracle Linux conversions, define and enable repositories pointing to the following URLs: Oracle Linux 7: https://cdn-ubi.redhat.com/content/public/ubi/dist/ubi/server/7/7Server/x86_64/os/ Oracle Linux 8: https://cdn-ubi.redhat.com/content/public/ubi/dist/ubi8/8/x86_64/baseos/os/ Install the subscription-manager package. Configure HTTP proxy for RHSM as described in How to configure HTTP Proxy for Red Hat Subscription Management. Prevent the configuration file from being deleted during the conversion: chattr +i /etc/rhsm/rhsm.conf Perform the conversion to RHEL. (BZ#1965487)
Clone Of:
Environment:
Last Closed: 2023-09-12 11:10:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-3282 0 None Migrated None 2023-09-12 11:18:57 UTC
Red Hat Issue Tracker RHELC-559 0 None None None 2022-03-30 06:52:12 UTC
Red Hat Knowledge Base (Solution) 6113661 0 None None None 2021-06-10 21:36:56 UTC

Description jcastran 2021-05-27 19:26:47 UTC 
Description of problem:
We are release locked to 8.3, we have updated to the latest Centos Kernel (4.18.0-240.22.1.el8_3.x86_64). The customer is using satellite and we have triple checked on another RHEL 8 machine registered the same way, that 8.3 AppStream and 8.3 BaseOS are sync'd and available. and we can see that the RHEL kernel*-4.18.0-240.22.1.el8_3.x86_64 is available and provides the same modules.

    # sed -i 's|releasever=8|releasever=8.3|' /usr/share/convert2rhel/configs/centos-8-x86_64.cfg

Customer has a proxy but configures it in the env as http_proxy and https_proxy as well as in /etc/yum.conf. 

Version-Release number of selected component (if applicable):
convert2rhel-0.21-1.el7.noarch


Steps to Reproduce:
1. proxy configured with
# export http_proxy=X.X.X.X
# export https_proxy=X.X.X.X
# echo "proxy=X.X.X.X" >> /etc/yum.conf
2. workaround for 8.3 Centos:
    # sed -i 's|releasever=8|releasever=8.3|' /usr/share/convert2rhel/configs/centos-8-x86_64.cfg
3. convert2rhel --debug --org="Richemont_International_SA" --activationkey $activationkey

Actual results:
CRITICAL - The following kernel modules are not supported in RHEL:
/lib/modules/4.18.0-240.22.1.el8_3.x86_64/kernel/net/netfilter/xt_TRACE.ko.xz
/lib/modules/4.18.0-240.22.1.el8_3.x86_64/kernel/drivers/input/rmi4/rmi_spi.ko.xz
/lib/modules/4.18.0-240.22.1.el8_3.x86_64/kernel/sound/drivers/mpu401/snd-mpu401.ko.xz
/lib/modules/4.18.0-240.22.1.el8_3.x86_64/kernel/drivers/media/usb/gspca/gspca_mr97310a.ko.xz
...
...<listed for every kernel module>

Expected results:
convert2rhel should allow for proxies in the environment. perhaps a --proxy option

An error message related to the connectivity to the repository or something more clear the issue is not related to kernel modules, but with the repository connection.


Additional info:
Comment 2 Michal Bocek 2021-05-27 20:14:44 UTC 
Hi John, thanks for the report. Using proxy is currently not easily possible with Convert2RHEL. I admit the error talking about kernel modules is confusing. We've improved it in upstream (https://github.com/oamg/convert2rhel/pull/285) and it will be part of the next release.

A workaround:

1. Configure /etc/yum.conf to make yum use a proxy per https://access.redhat.com/solutions/4200391
2. Install subscription-manager
 - on CentOS Linux 7 and 8, subscription-manager is available in the standard repos, so just run `yum install subscription-manager`
 - on CentOS Linux 6, enable the contrib repo: `yum install --enablerepo contrib subscription-manager`
 - on Oracle Linux, add the following repositories first: https://github.com/oamg/convert2rhel/blob/v0.21/convert2rhel/subscription.py#L34
3. Edit the proxy settings in /etc/rhsm/rhsm.conf per https://access.redhat.com/solutions/57669
4. Run `chattr +i /etc/rhsm/rhsm.conf` to make it undeletable (convert2rhel is re-installing any installed subscription-manager and the config file would be removed)
5. Run convert2rhel
Comment 3 jcastran 2021-05-27 20:17:54 UTC 
Thanks Michael. I have passed this on to the customer and we're just waiting for the results.


Thanks,
John Castranio
Red Hat
Comment 5 RHEL Program Management 2023-09-12 11:05:03 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 6 RHEL Program Management 2023-09-12 11:10:05 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.