Description of problem: Package upload fails with larger rpms (30MB+) in UI with "Error during upload: undefined" How reproducible: Always Steps to Reproduce: 1. upload large rpm to a repository (such as jre) Actual results: Error message with "Error during upload: undefined" Expected results: Either success or advise to use hammer cli to uplaod the large file Additional info:
Moving to POST since upstream bug http://projects.theforeman.org/issues/7554 has been closed ------------- David Davis Applied in changeset commit:katello|78b88cf834d014091d62673ebc0cbc99c6921572.
*** This bug is verified in upstream. This fix should eventually land in future downstream builds *** RHEL65 / RHEL7 Error message recieved: Error during upload: File too large. Please use the CLI instead Version Tested: foreman-proxy-1.8.0-0.develop.201411121327gitab6edc2.el7.noarch yttrium.idmqe.lab.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-gce-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-selinux-1.8.0-0.develop.201410280941git10de1c5.el7.noarch foreman-vmware-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-release-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman_discovery-1.4.0-2.el7.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410git163c264.git.0.988ca80.el7.noarch foreman-postgresql-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman_docker-0.2.0-2.el7.noarch rubygem-hammer_cli_foreman-0.1.3-1.201411121216git9381fc5.el7.noarch foreman-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-ovirt-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman-tasks-0.6.9-1.el7.noarch foreman-libvirt-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-compute-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman_bootdisk-4.0.0-1.el7.noarch yttrium.idmqe.lab.eng.bos.redhat.com-foreman-client-1.0-1.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7.noarch
Hi, with very large RPM's say 250MB the CLI does not work either. I was able to workaround the issue during a customer engagement by creating repositories with "createrepo" on the local filesystem and use file:///<path-to-repo> as the URL.
This bug is slated to be released with Satellite 6.1.
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://access.redhat.com/errata/RHSA-2015:1592
Not resolved in 6.2 of Satellite
Just tried with a 48MB file. This is not resolved as of 6.3.1 either.
I tried to reproduce it again to be sure, and the 2nd time it worked, 3rd and 4th and 5th it didnt. So maybe its something more nuanced. We also have a kbase on it and people are claiming there it its still a problem as recent as March: https://access.redhat.com/solutions/1754913