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.
Description of problem: after scaling the image-registry to `--replicas=2` new digests fails to push with a golang `panic: d.nx != 0`.
Version-Release number of selected component (if applicable): 4.3.8
How reproducible: attempted to replicate the issue described on two separate AWS clusters (with 2 registry replicas), and both attempts completed successfully.
Steps to Reproduce:
1. Scale image-registry to `--replicas=2`.
2. Push a new image to the image-registry.
Actual results: image push fails with golang `panic: d.nx != 0`
Expected results: image push to succeed.
Additional info:
- Scaling the image registry to `--replicas=1` avoids the issue.
- HTTP proxy used in the cluster.
- AWS cluster with persistent S3 storage set for the image registry.
Robert,
I'm not familiar with the --replicas option, I think that's something in OpenShift. From what I can see in the stack trace, there's no evidence of any Buildah bits in there. Can you tell me how you did the push and why you think this is a Buildah issue?
Nalin any thoughts?
Hi Oleg.
The issue has been confirmed as resolved by the customer, after setting up the `httpSecret` to a random string.
Closing the bug. Thank you for your help.
Checked the source code of podman with podman-2.0.3-1.module+el8.3.0+7505+fe51f0c6.src.rpm, and the pullreq already included, So set this to verified. Details:
# find . -name "upload_reader.go"
./vendor/github.com/containers/image/v5/internal/uploadreader/upload_reader.go
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 (Moderate: 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-2020:4694