Bug 1328707

Summary:	[RFE] make it possible to run katello-remove unattended
Product:	Red Hat Satellite	Reporter:	Jan Hutař <jhutar>
Component:	Foreman Proxy	Assignee:	Chris Roberts <chrobert>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.2.0	CC:	amdas, bkearney, chrobert, jcallaha
Target Milestone:	6.4.0	Keywords:	FutureFeature, RFE, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
URL:	http://projects.theforeman.org/issues/16003
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-16 15:26:14 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 Jan Hutař 2016-04-20 06:27:56 UTC

Description of problem:
I was about to uninstall about 17 capsules and had to do it manually. I would expect option like `capsule-remove --I-really-know-what-Iam-doing-so-do-not-ask-me`


Version-Release number of selected component (if applicable):
foreman-installer-katello-3.0.0.18-1.el7sat.noarch


How reproducible:
always


Steps to Reproduce:
1. `capsule-remove --help` or `man capsule-remove`


Actual results:
Tool have to be run manually.


Expected results:
There should be option for unattended run of the tool.

Comment 1 Bryan Kearney 2016-07-08 20:41:39 UTC

Per 6.3 planning, moving out non acked bugs to the backlog

Comment 6 Chris Roberts 2017-12-12 17:29:53 UTC

*** Bug 1481107 has been marked as a duplicate of this bug. ***

Comment 7 Peter Ondrejka 2018-07-02 09:37:43 UTC

Verifed on Sat 6.4 snap 10, katello-remove is now shipped with functioning -y option

Comment 9 errata-xmlrpc 2018-10-16 15:26:14 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927