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 1111484 - Hammer: production.log filled up with garbage data when we upload contents to selected repo
Summary: Hammer: production.log filled up with garbage data when we upload contents to...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Dustin Tsang
QA Contact: sthirugn@redhat.com
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-20 07:08 UTC by Sachin Ghai
Modified: 2019-09-26 18:12 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-11 12:19:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Logs from production.log that contains garbage data, Not sure if its expected, but I don't think log file should include such data (14.90 KB, text/x-log)
2014-06-20 07:08 UTC, Sachin Ghai
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 6411 0 None None None 2016-04-22 15:10:06 UTC

Description Sachin Ghai 2014-06-20 07:08:32 UTC
Created attachment 910661 [details]
Logs from production.log that contains garbage data, Not sure if its expected, but I don't think log file should include such data

Description of problem:
I was trying to upload contents to selected repo via hammer. Contents are uploaded successfully, however while uploading, the production.log filled up with some garbage data.

Processing by Katello::Api::V2::ContentUploadsController#create as application/json;version=2
  Parameters: {"api_version"=>"v2", "repository_id"=>"17", "content_upload"=>{}}
Expire fragment views/tabs_and_title_records-1 (0.3ms)
Authorized user admin(Admin User)
Completed 200 OK in 171ms (Views: 0.7ms | ActiveRecord: 26.0ms)
Processing by Apipie::ApipiesController#apipie_checksum as JSON
  Parameters: {"apipy"=>{}}
  Rendered /opt/rh/ruby193/root/usr/share/gems/gems/apipie-rails-0.1.2/app/views/apipie/apipies/apipie_checksum.json.erb (0.2ms)
Completed 200 OK in 4ms (Views: 3.5ms | ActiveRecord: 0.0ms)
Processing by Katello::Api::V2::ContentUploadsController#update as application/json;version=2
  Parameters: {"offset"=>"0", "content"=>"\u001F\x8B\b\u0000tdTR\u0000\u0003\xED=ks\xDB8\x92\xF3\x99\xBF\u0002\xE7\xA4J\xF6\x94-\xF3%R\xD2]\xA6Λ8\x89\xEB2v\xCANfkk*\xE5\u0005I\xD0\xE6\x86\"u$\u0015Ǘ\xF2\xFD\xF6\xEBƃ\")J\xB2c\x8D\x92Kػ\u0013K \xD0\xDD\xE8\a\u001A@\x83\xD0t6\x9D\xB2\"\xA6^~\x90ͼ\xDB\u0003\xBDo\xF4\xF5\xC3_6\n\xBA\xAE\xBB\x83\u0001\xE1\u007F\u001D\xF1W7m\xF1W\u00021L\xD3\u001C\xE8\x8Ei86э\x81=\xD0\u007F!\x83Ͳ\xD1\u000E\xB3\xBC\xA0\u0019\xB0B\xA7,I\xD8\xED\xD2zP-\fW\xE0\x91\xFD(\xFF\xFE?\x81i\xAB\xFE\x9F\xBF>:}u\xFC\xE6\xEC\xD5Fh\x80<\u001C\xDB^\xAE\xFF\x81\xD3Կ\xE38\xD6/D\xDF\b\xF55\xF0\x93\xEB\xDF\xD4\r\xEB\xC0\xD0\u000F\xF4!9 \u007F\xB0,\x8F҄p#д\x8B\xD9dB\xB3۱\xA6\x9D\xB3\x98ќ\u0011\x9A\x90\xD94\xA0\u0005\v\xC8'Y7\rIq\u001D\xE5}\xF2:\xBA\xBA\x8E\xE1\xBF\"'Q\xE2dz\x80\x913\x90\xE9\xC5\xFB\x8Bch\u0017\x90+\x96\xB0\x8C\xC6Z>͢\xE4\x8A\xF8\x801\xC1\u000FA\x9A0\xE2ݒt\x96\x91\x9B4\tX\u0016\xCEb⧓\xC9,\x89\x8A[2a\u0013\u000Fh\xFD\x9B\xA6\xBDd\xB4\x98e,\u001Fk\as\xD49\u0018p\x9A\u0015Pt\u0014\xC7\xE9\r\xF9'\x9A\xF1\u0015\x9B\xE4\x97S\xEA\u007F\xA4W\xEC\x9F$\u0005^\xB3(`}\xAC\u0014 '\x93\xEBt\xC2HH\xFDB\x95e\u0011\x91\xF5\xFB@(\xFA,\xA8\xBC\x89\x92\x

Version-Release number of selected component (if applicable):
sat6 beta snap10

How reproducible:
always

Steps to Reproduce:
hammer repository upload-content --id 17 --organization-id 1 --path /var/tmp/puppetlabs-ruby-0.1.0.tar.gz 
Successfully uploaded file 'puppetlabs-ruby-0.1.0.tar.gz'.

check production.log

Actual results:


Expected results:
production.log should not be filled up with above garbage data.

Additional info:

Comment 1 Sachin Ghai 2014-06-20 07:11:40 UTC
This happens in both cases, when we upload rpms to yum repo as well as when we upload puppet modules to puppet repo

Comment 3 Dustin Tsang 2014-06-26 23:11:55 UTC
redmine issue created

Comment 4 Dustin Tsang 2014-07-11 17:09:36 UTC
2 pull requests:

foreman: https://github.com/theforeman/foreman/pull/1548
katello: https://github.com/Katello/katello/pull/4364

Comment 6 sthirugn@redhat.com 2014-09-04 18:17:52 UTC
Verified.

Version Tested:
GA Snap 7 - Satellite-6.0.4-RHEL-6-20140829.0

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.23-1.el6_5.noarch
* candlepin-common-1.0.1-1.el6_5.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.9.23-1.el6_5.noarch
* candlepin-tomcat6-0.9.23-1.el6_5.noarch
* elasticsearch-0.90.10-6.el6sat.noarch
* foreman-1.6.0.42-1.el6sat.noarch
* foreman-compute-1.6.0.42-1.el6sat.noarch
* foreman-gce-1.6.0.42-1.el6sat.noarch
* foreman-libvirt-1.6.0.42-1.el6sat.noarch
* foreman-ovirt-1.6.0.42-1.el6sat.noarch
* foreman-postgresql-1.6.0.42-1.el6sat.noarch
* foreman-proxy-1.6.0.30-1.el6sat.noarch
* foreman-selinux-1.6.0.14-1.el6sat.noarch
* foreman-vmware-1.6.0.42-1.el6sat.noarch
* katello-1.5.0-30.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.6-1.el6sat.noarch
* katello-installer-0.0.62-1.el6sat.noarch
* openldap-2.4.23-34.el6_5.1.x86_64
* openldap-devel-2.4.23-34.el6_5.1.x86_64
* pulp-katello-0.3-4.el6sat.noarch
* pulp-nodes-common-2.4.1-0.5.rc1.el6sat.noarch
* pulp-nodes-parent-2.4.1-0.5.rc1.el6sat.noarch
* pulp-puppet-plugins-2.4.1-0.5.rc1.el6sat.noarch
* pulp-puppet-tools-2.4.1-0.5.rc1.el6sat.noarch
* pulp-rpm-plugins-2.4.1-0.5.rc1.el6sat.noarch
* pulp-selinux-2.4.1-0.5.rc1.el6sat.noarch
* pulp-server-2.4.1-0.5.rc1.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch

Comment 7 Bryan Kearney 2014-09-11 12:19:33 UTC
This was delivered with Satellite 6.0 which was released on 10 September 2014.


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