Bug 1927170

Summary:	foreman-maintain quits the actual run for backup commands, with unavailable option n(no) as same as q(quit).
Product:	Red Hat Satellite	Reporter:	Gaurav Talreja <gtalreja>
Component:	Satellite Maintain	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Gaurav Talreja <gtalreja>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.9.0	CC:	apatel, aupadhye, kgaikwad
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:	2022-10-28 18:02:59 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 Gaurav Talreja 2021-02-10 09:31:40 UTC

Description of problem:
From, https://bugzilla.redhat.com/show_bug.cgi?id=1640974#c9
For foreman-maintain backup commands, where q(quit) option is available and unavailable option n(no) is also working as same as q(quit).
And however, if type any other letter then it keeps on looping the question, with an improper warning.   


Version-Release number of selected component (if applicable):
Satellite 6.9.0 Snap 12
Version: rubygem-foreman_maintain-0.7.4-1.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. # foreman-maintain backup offline /tmp/
  <snip>
    Do you want to proceed?, [y(yes), q(quit)] n
                                                                        
    [ABORTED]
   ----------------------------------------------------------------------------- 
   Scenario [Backup] failed.

    The processing was aborted by user during the following steps:

     [backup-accessibility-confirmation]


    Running Failed backup cleanup
  </snip>

2. # foreman-maintain backup online /tmp/
  <snip>
    Do you want to proceed?, [y(yes), q(quit)] n
                                                                        
    [ABORTED]
  ------------------------------------------------------------------------------
   Scenario [Backup] failed.

   The processing was aborted by user during the following steps:

     [backup-online-safety-confirmation]


   Running Failed backup cleanup
  </snip>

3. # foreman-maintain backup online(or offline) /tmp/
   <snip>
    Do you want to proceed?, [y(yes), q(quit)] xyz
    *** WARNING: <warning-msg>
    Do you want to proceed?, [y(yes), q(quit)] xyz
    *** WARNING: <warning-msg>
    Do you want to proceed?, [y(yes), q(quit)]
   </snip>
   

Actual results:
option n(no) is working as same as q(quit)

Expected results:
option 'n' should also keep asking the question, as it's happening now for any invalid options.

Additional info:

Comment 2 Brad Buckingham 2022-09-02 20:25:18 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 3 Brad Buckingham 2022-09-02 20:30:13 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 4 Brad Buckingham 2022-10-28 18:02:59 UTC

Thank you for your interest in Red Hat Satellite. 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.