2057052 – [RFE] Need a proxy to reach RHUI repos during an IPU

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 2057052 - [RFE] Need a proxy to reach RHUI repos during an IPU

Summary: [RFE] Need a proxy to reach RHUI repos during an IPU

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	leapp-repository
Sub Component:
Version:	7.9
Hardware:	x86_64
OS:	All
Priority:	medium
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	Leapp Notifications Bot
QA Contact:	upgrades-and-conversions
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2022-02-22 16:09 UTC by Christophe Besson
Modified:	2023-09-20 15:55 UTC (History)
CC List:	6 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2023-09-12 12:24:40 UTC
Target Upstream Version:
Embargoed:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)

Links
System	ID	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	OAMG-6544	None	None	None	2022-02-22 16:22:11 UTC
Red Hat Issue Tracker	RHEL-3297	None	Migrated	None	2023-09-12 12:19:55 UTC
Red Hat Issue Tracker	RHELPLAN-113061	None	None	None	2022-02-22 16:22:14 UTC
Red Hat Knowledge Base (Solution)	7025838	None	None	None	2023-07-26 12:21:58 UTC

Description Christophe Besson 2022-02-22 16:09:15 UTC

Description of problem:
When RHSM is used during the IPU, the proxy defined in RHSM is used, as it generates the redhat.repo file with the proxy setting.
But in case of RHUI repositories, there is no equivalent. Usually customers choose /etc/yum.conf to define it, but this is not taken into account in the target userspace container (/etc/yum/* are symlinked to /etc/dnf/* but not the main config file).

Version-Release number of selected component (if applicable):
leapp-upgrade-el7toel8-0.15.0-6.el7_9

How reproducible:
Always for AWS

Steps to Reproduce:
1. Try to upgrade a RHEL 7.9 OS (PAYG on AWS, not BYOS) behind a proxy.

Actual results:
Unable to reach RHUI repos.

Additional info:
* to workaround the issue, the proxy has been added to /etc/dnf/dnf.conf, and then the DNF config has been added by patching /usr/share/leapp-repository/repositories/system_upgrade/common/actors/scanfilesfortargetuserspace/libraries/scanfilesfortargetuserspace.py.

* the suggested feature I mentioned in rhbz#2040706 could help

Comment 3 Petr Stodulka 2022-05-03 17:37:53 UTC

Hi Chris, thanks for the report and sorry for delayed answer. The mentioned feature could be the solution / workaround for this bugzilla.

For now as a workaround customer can create a custom actor that does basically the same, so they are not blocked till a solution is delivered.
To see how to create a custom actor follow:
    https://access.redhat.com/articles/4977891#actors

Such an actor.py file could look like this in the simplest example:
~~~
from leapp.actors import Actor
from leapp.models import CopyFile, TargetUserSpacePreupgradeTasks
from leapp.tags import FactsPhaseTag, IPUWorkflowTag


class MyDNFProxyWorkaround(Actor):
    name = 'my_dnf_proxy_workaround'
    consumes = ()
    produces = (TargetUserSpacePreupgradeTasks,)
    tags = (FactsPhaseTag, IPUWorkflowTag)

    def process(self):
        # In case the current /etc/yum.conf file is compatible with DNF
        # from RHEL 8, it can be used in the src instead of the dnf one
        preupgrade_task = TargetUserSpacePreupgradeTasks(copy_files=[
            CopyFile(src='/etc/dnf/dnf.conf', dst='/etc/dnf/dnf.conf'),
        ])
~~~

Ideal solution for this BZ would be migration of the yum configuration file,
but it's unlikely that this happen.



Note: Keeping the feature aside for now as we have some discussions around.

Comment 4 Petr Stodulka 2022-05-03 17:40:35 UTC

The example above expects the /etc/dnf/dnf.conf file is already configured correctly for the RHEL 8 DNF (with the proxy added).

Comment 13 RHEL Program Management 2023-09-12 11:56:17 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 14 RHEL Program Management 2023-09-12 12:24:40 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.