Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1142301

Summary: Uploading puppet module via Red Hat Satellite v 6 web-ui, it fails with error - "No such file or directory - /tmp/RackMultipartxxxx"
Product: Red Hat Satellite Reporter: Johan Swensson <jswensso>
Component: Content ManagementAssignee: Ivan Necas <inecas>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: high Docs Contact:
Priority: high    
Version: 6.0.4CC: achan, ahumbe, bthurber, cwelton, dcleal, ggillies, jmontleo, michele, mmccune, pmoravec, sthirugn, xdmoon
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/7915
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Uploading a puppet module or rpm to a repository in the webUI failed with error : "No such file or directory - /tmp/RackMultipartxxxx" on a Satellite Server installed on a Red Hat Enterprise Linux 7 host. The module/rpm are now pre-copied in a private tmp folder and should successfully upload.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-13 22:29:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1115190, 1139277    
Attachments:
Description Flags
Foreman log none

Description Johan Swensson 2014-09-16 14:24:08 UTC
Created attachment 938041 [details]
Foreman log

Description of problem:
Uploading an rpm or puppet module or rpm to a repository fails with the following error:
Error during upload: Task accbe8fe-4d30-47ff-8e44-aa5ee0021a45: Errno::ENOENT: No such file or directory - /tmp/RackMultipart20140916-17443-bv0m8b


How reproducible:
Every time

Steps to Reproduce:
1. Install a minimal RHEL7
2. Follow the installation guide to install Satellite 6 i.e: yum install katello; katello-installer
In the Satellite6 web console:
3. Add a product
4. Add a repository in that product
5. Upload package or puppet module(depending on which repo type you choose).


Actual results:
The task pauses and the upload fails.

Expected results:
File should be uploaded successfully.

Additional info:

Comment 1 RHEL Program Management 2014-09-16 14:33:16 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Dominic Cleal 2014-09-17 12:21:31 UTC
*** Bug 1142791 has been marked as a duplicate of this bug. ***

Comment 6 Brad Buckingham 2014-09-23 22:16:32 UTC
I am able to reproduce this issue when uploading puppet modules using the UI with a RHEL 7 server, but not with a RHEL 6.5 server.

As a workaround, I was able to upload puppet modules using the hammer cli.  E.g.

hammer> repository upload-content --organization-label Default_Organization --id 1 --path /root/theforeman-git-1.3.0.tar.gz
Successfully uploaded file 'theforeman-git-1.3.0.tar.gz'.

hammer> repository upload-content --organization-label Default_Organization --id 1 --path /root/theforeman-git-1.3.1.tar.gz
Successfully uploaded file 'theforeman-git-1.3.1.tar.gz'.

hammer> puppet-module list --repository-id 1
-------------------------------------|------|------------|--------
ID                                   | NAME | AUTHOR     | VERSION
-------------------------------------|------|------------|--------
6970d3bf-a9fe-439b-9c32-2aceadcf18e0 | git  | theforeman | 1.3.1  
7cc71580-9849-46a6-9f67-5437800e8b99 | git  | theforeman | 1.3.0  
-------------------------------------|------|------------|--------

Comment 7 Ivan Necas 2014-10-13 12:04:27 UTC
Created redmine issue http://projects.theforeman.org/issues/7915 from this bug

Comment 8 Bryan Kearney 2014-10-13 14:06:05 UTC
Upstream bug assigned to inecas

Comment 9 Bryan Kearney 2014-10-14 14:04:20 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/7915 has been closed
-------------
Ivan Necas
Applied in changeset commit:katello|a5af25564fe2f7d643e83196fcfc13db6b7c5013.

Comment 10 Ivan Necas 2014-10-14 14:18:23 UTC
https://github.com/Katello/katello/pull/4736

Comment 11 jcallaha 2014-10-17 18:43:41 UTC
able to successfully upload with 6.5 server.

*** Verified ***

foreman-release-1.7.0-0.develop.201410150839gitb948163.el6.noarch
foreman-gce-1.7.0-0.develop.201410150839gitb948163.el6.noarch
foreman-selinux-1.7.0-0.develop.201409301113git2f345de.el6.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410gitc96619d.git.0.37f3704.el6.noarch
qe-foreman-rhel65.usersys.redhat.com-foreman-proxy-1.0-1.noarch
foreman-postgresql-1.7.0-0.develop.201410150839gitb948163.el6.noarch
qe-foreman-rhel65.usersys.redhat.com-qpid-broker-1.0-1.noarch
qe-foreman-rhel65.usersys.redhat.com-qpid-client-cert-1.0-1.noarch
foreman-1.7.0-0.develop.201410150839gitb948163.el6.noarch
foreman-ovirt-1.7.0-0.develop.201410150839gitb948163.el6.noarch
foreman-vmware-1.7.0-0.develop.201410150839gitb948163.el6.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el6.noarch
ruby193-rubygem-foreman_discovery-1.4.0-0.1.rc4.el6.noarch
rubygem-hammer_cli_foreman-0.1.3-1.201410151235gitbc8c449.el6.noarch
ruby193-rubygem-foreman_bootdisk-4.0.0-1.el6.noarch
foreman-proxy-1.7.0-0.develop.201410101404git7961640.el6.noarch
qe-foreman-rhel65.usersys.redhat.com-puppet-client-1.0-1.noarch
qe-foreman-rhel65.usersys.redhat.com-foreman-client-1.0-1.noarch
qe-foreman-rhel65.usersys.redhat.com-apache-1.0-1.noarch
qe-foreman-rhel65.usersys.redhat.com-parent-cert-1.0-1.noarch
foreman-compute-1.7.0-0.develop.201410150839gitb948163.el6.noarch
ruby193-rubygem-foreman-tasks-0.6.10-1.el6.noarch
foreman-libvirt-1.7.0-0.develop.201410150839gitb948163.el6.noarch

Comment 14 Pavel Moravec 2014-10-30 07:56:57 UTC
(In reply to jcallaha from comment #11)
> able to successfully upload with 6.5 server.
> 
> *** Verified ***
> 
> foreman-release-1.7.0-0.develop.201410150839gitb948163.el6.noarch
> foreman-gce-1.7.0-0.develop.201410150839gitb948163.el6.noarch
> foreman-selinux-1.7.0-0.develop.201409301113git2f345de.el6.noarch
> rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410gitc96619d.git.0.
> 37f3704.el6.noarch
> qe-foreman-rhel65.usersys.redhat.com-foreman-proxy-1.0-1.noarch
> foreman-postgresql-1.7.0-0.develop.201410150839gitb948163.el6.noarch
> qe-foreman-rhel65.usersys.redhat.com-qpid-broker-1.0-1.noarch
> qe-foreman-rhel65.usersys.redhat.com-qpid-client-cert-1.0-1.noarch
> foreman-1.7.0-0.develop.201410150839gitb948163.el6.noarch
> foreman-ovirt-1.7.0-0.develop.201410150839gitb948163.el6.noarch
> foreman-vmware-1.7.0-0.develop.201410150839gitb948163.el6.noarch
> ruby193-rubygem-foreman_hooks-0.3.7-2.el6.noarch
> ruby193-rubygem-foreman_discovery-1.4.0-0.1.rc4.el6.noarch
> rubygem-hammer_cli_foreman-0.1.3-1.201410151235gitbc8c449.el6.noarch
> ruby193-rubygem-foreman_bootdisk-4.0.0-1.el6.noarch
> foreman-proxy-1.7.0-0.develop.201410101404git7961640.el6.noarch
> qe-foreman-rhel65.usersys.redhat.com-puppet-client-1.0-1.noarch
> qe-foreman-rhel65.usersys.redhat.com-foreman-client-1.0-1.noarch
> qe-foreman-rhel65.usersys.redhat.com-apache-1.0-1.noarch
> qe-foreman-rhel65.usersys.redhat.com-parent-cert-1.0-1.noarch
> foreman-compute-1.7.0-0.develop.201410150839gitb948163.el6.noarch
> ruby193-rubygem-foreman-tasks-0.6.10-1.el6.noarch
> foreman-libvirt-1.7.0-0.develop.201410150839gitb948163.el6.noarch

FYI this bug appears _only_ on RHEL7 (at least from my observation). So when you will be verifying it, please do so on RHEL7 and not on RHEL6.

Comment 15 Johan Swensson 2014-10-30 08:05:03 UTC
(In reply to Pavel Moravec from comment #14)
> FYI this bug appears _only_ on RHEL7 (at least from my observation). So when
> you will be verifying it, please do so on RHEL7 and not on RHEL6.

Correct, this is a RHEL7 issue.

Comment 17 jcallaha 2014-10-31 13:56:55 UTC
** Re-Verified against Z-Stream **

Satellite-6.0.4-RHEL-7-20141029.5

foreman-1.6.0.47-1.el7sat.noarch
foreman-compute-1.6.0.47-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.5-2.el7sat.noarch
foreman-gce-1.6.0.47-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-1.3.0-2.el7sat.noarch
foreman-libvirt-1.6.0.47-1.el7sat.noarch
foreman-proxy-1.6.0.30-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.0.4-2.el7sat.noarch
foreman-vmware-1.6.0.47-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3-3.el7sat.noarch
foreman-selinux-1.6.0.15-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.9-1.1.el7sat.noarch
foreman-ovirt-1.6.0.47-1.el7sat.noarch
foreman-postgresql-1.6.0.47-1.el7sat.noarch
qe-sat6-rhel7.usersys.redhat.com-foreman-proxy-1.0-1.noarch
qe-sat6-rhel7.usersys.redhat.com-foreman-client-1.0-1.noarch
rubygem-hammer_cli_foreman-0.1.1-16.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-2.0.6-1.1.el7sat.noarch

Comment 19 errata-xmlrpc 2014-11-13 22:29:13 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, 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/RHBA-2014:1857