Bug 1733239

Summary:	foremain-maintain backup whitelist does a skip instead of ignore failures
Product:	Red Hat Satellite	Reporter:	Peter Vreman <peter.vreman>
Component:	Satellite Maintain	Assignee:	Anurag Patel <apatel>
Status:	CLOSED WONTFIX	QA Contact:	Lucie Vrtelova <lvrtelov>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.5.0	CC:	apatel, inecas, jpathan, kgaikwad, mbacovsk, ofalk, patalber
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-09 17:02:24 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:	1122832

Description Peter Vreman 2019-07-25 13:48:19 UTC

Description of problem:
Using the recommended whitelist after finding chagnes to pulp files and config files that still might change online. Instead of executing and ignoreing the error it just skips the whole step. Found a simaliar remark in https://bugzilla.redhat.com/show_bug.cgi?id=1673908#c3





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


How reproducible:


Steps to Reproduce:
1. foreman-maintain backup online -y --whitelist=backup-pulp,backup-config-files /backup
2.
3.

Actual results:
Pulp data and config files are not included in the backup


Expected results:
Pulp data and config file included in backup


Additional info:

Comment 3 Mike McCune 2021-07-09 17:02:24 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.