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.

<jbrooks> walters, I'm having trouble getting lorax to use the newer anaconda pkg. I tried incrementing the version from -5 to -6, I've tried various other things, but it wants to stick w/ the version of anaconda in the main repo
<jbrooks> I don't know where the breakage is

... snip 20 minutes of debugging ...

Then I notice it's using COPR's default of an https:// baseurl...

<walters> wait this is triggering a memory for me
<walters> https://github.com/rhinstaller/lorax/commit/611cef1823c43fb5320f79c796ea5e77eb14681f
<walters> and before that commit they were silently ignored
<walters> oh yes
<walters> that commit didn't make it to rhel7-branch
<walters> love when i fix a problem and then a year and a half later i debug it again
<walters> because there were layers and layers of branches and manual integration
<walters> so anyways for now i guess allow anyone with the capability to MITM traffic on the internet to run arbitrary code by just changing it to http://
<walters> (or mirror the repos securely, then use http://, or backport the lorax patch)
<walters> you know what's actually astounding is how many people do yum repos with http://
<walters> i've been tempted to change ostree to explicitly barf if you do this without gpg enabled either

Verified in lorax-19.6.74-1.el7, patch is backported.

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, 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://rhn.redhat.com/errata/RHBA-2016-2165.html