Bug 1477999 - wrong exit code when uploading file is too large
Summary: wrong exit code when uploading file is too large
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Configuration Management
Version: 580
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Dobes
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: sat58-nth
TreeView+ depends on / blocked
 
Reported: 2017-08-03 12:28 UTC by Pavel Studeník
Modified: 2018-04-09 15:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-09 15:35:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pavel Studeník 2017-08-03 12:28:05 UTC
Description of problem:
I created big file and I tried to push to configure channel. The file was not uploaded, but the application finished with exit code 0.

Change max size of file:

web.maximum_config_file_size=1031072 >> /etc/rhn/rhn.conf

Version-Release number of selected component (if applicable):
rhncfg-management-5.10.87-10.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. >> dd if=/dev/urandom of=10Mfile bs=1M count=10
2. >> rhncfg-manager add 10Mfile -c mychannel
Using server name satellite.example.com
Pushing to channel mychannel:
Error pushing file:  10Mfile too large (10485760 bytes, 131072 bytes max allowed)
3. >> echo $?
0

Actual results:
exit code 0

Expected results:
correct exit code

Comment 1 Tomas Lestach 2018-04-09 15:35:10 UTC
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.


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