Bug 1158967

Summary:	rhn_check returns 0 after failing to deploy config files
Product:	Red Hat Satellite 5	Reporter:	Lukáš Hellebrandt <lhellebr>
Component:	Client	Assignee:	Tomáš Kašpárek <tkasparek>
Status:	CLOSED DEFERRED	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	570	CC:	tlestach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-09 11:29:36 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:	1158957, 1162131

Description Lukáš Hellebrandt 2014-10-30 15:27:18 UTC

Description of problem:
When the client system is missing deploy capability, upon file deployment, rhn_check -vv complains about not being able to deploy files but returns 0


How reproducible:
Always

Steps to Reproduce:
1. In bug #1158957 , reproduce steps 1 to 10
2. Notice the output of rhn_check -vv:

"D: do_call configfiles.deploy({'files': []},){'cache_only': None}
D: Sending back response(42, 'Local permission not set for action type configfiles.deploy', {})"

3. Notice in events->history, the "Deploy config files to system scheduled by admin" action is marked as failed
4. Therefore, the rhn_check failed and should have returned non-zero. Notice, however, it returned 0.

Actual results:
rhn_check returned 0

Expected results:
It (partly) failed so it should have returned non-zero

Comment 2 Tomas Lestach 2018-04-09 11:29:36 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.