Bug 1465920 - [RHST] creates public comment when split option used to upload private attachments
[RHST] creates public comment when split option used to upload private attach...
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: redhat-support-tool (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: rc
: ---
Assigned To: Vikas Rathee
BaseOS QE - Apps
Depends On:
  Show dependency treegraph
Reported: 2017-06-28 08:48 EDT by Dwight (Bud) Brown
Modified: 2017-12-06 05:44 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-12-06 05:44:35 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dwight (Bud) Brown 2017-06-28 08:48:46 EDT
Description of problem:
push large >1G file with -s option and -p false creates a series of private comments and private attachments.  When all parts are uploaded a summary comment is created listing all the parts uploaded.  This summary comment is created as a public comment.  It should be created as a private comment.

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

How reproducible:

Steps to Reproduce:

Actual results:
public comment created for private attachment upload

Expected results:
private comment created for private attachment upload

Additional info:
Workaround is to perform splits as separate command and invoke rhst upload for each part.
Comment 2 Jan Kurik 2017-12-06 05:44:35 EST
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:


This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:


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