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 2129767 - ADD Dockerfile reference is not validating HTTP status code [rhel8-8.7.0]
Summary: ADD Dockerfile reference is not validating HTTP status code [rhel8-8.7.0]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: buildah
Version: 8.6
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Joy Pu
URL:
Whiteboard:
Depends On: 2102140
Blocks: 2129766
TreeView+ depends on / blocked
 
Reported: 2022-09-26 09:36 UTC by Jindrich Novy
Modified: 2022-11-08 13:02 UTC (History)
8 users (show)

Fixed In Version: buildah-1.27.2-1.el8_7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2102140
Environment:
Last Closed: 2022-11-08 11:30:44 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers buildah pull 4287 0 None Merged [release-1.19] add: fail on bad `HTTP` response instead of writing to container for `URL` sources 2022-09-26 09:38:48 UTC
Red Hat Issue Tracker RHELPLAN-134875 0 None None None 2022-10-01 01:24:07 UTC
Red Hat Product Errata RHSA-2022:7822 0 None None None 2022-11-08 11:31:28 UTC

Comment 11 Joy Pu 2022-10-24 05:06:55 UTC
Test with buildah-1.27.2-2.module+el8.7.0+16994+ed730e67.x86_64 and it report 404 error as expected. So move this to verified:
# buildah bud .
STEP 1/2: FROM registry.fedoraproject.org/fedora:36
Trying to pull registry.fedoraproject.org/fedora:36...
Getting image source signatures
Copying blob 62946078034b done  
Copying config 2ecb6df959 done  
Writing manifest to image destination
Storing signatures
STEP 2/2: ADD https://mirror.init7.net/fedora/fedora/linux/releases/36/Server/x86_64/iso/Fedora-Server-netinst-x86_64-36-1.5.foo /
error building at STEP "ADD https://mirror.init7.net/fedora/fedora/linux/releases/36/Server/x86_64/iso/Fedora-Server-netinst-x86_64-36-1.5.foo /": error reading "https://mirror.init7.net/fedora/fedora/linux/releases/36/Server/x86_64/iso/Fedora-Server-netinst-x86_64-36-1.5.foo": invalid response status 404

Comment 15 errata-xmlrpc 2022-11-08 11:30:44 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 (Low: container-tools:rhel8 security, 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/RHSA-2022:7822


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