Bug 1373095

Summary: Task export shall add extracted log files in foreman-debug
Product: Red Hat Satellite Reporter: Lukas Zapletal <lzap>
Component: Foreman DebugAssignee: Ivan Necas <inecas>
Status: CLOSED NOTABUG QA Contact: Adam Ruzicka <aruzicka>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.0CC: aruzicka, bbuckingham, ehelms, jcallaha
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/14878
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-23 11:48:56 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:

Description Lukas Zapletal 2016-09-05 07:22:36 UTC
Task exported creates a tar.gz file which is then added to foreman-debug via add_file statement, but the contract requires only plain text (log) files to be added. There is additional filtering going on underneath, which fails for tarballs creating an output file in invalid format (broken tar).

We need to change the task export foreman-debug statement to create those files unextracted. They can be added all via

add_files /path/to/foreman-export/directory/*
Everything will be compressed, there is no need to create tarballs or compressed tarballs.

TRIAGE NOTES: We need to backport this to improve debug experience for 6.2.

See also: https://bugzilla.redhat.com/show_bug.cgi?id=1274694

Comment 3 Bryan Kearney 2016-09-05 10:19:03 UTC
Upstream bug assigned to inecas

Comment 4 Bryan Kearney 2016-09-05 10:19:05 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/14878 has been resolved.

Comment 5 Adam Ruzicka 2017-08-23 11:48:56 UTC
This is not relevant anymore, 6.3 dropped task export in favor of csv export[1], 6.2.z has this fixed and verified as [2]

[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1416119
[2] - https://bugzilla.redhat.com/show_bug.cgi?id=1370224