Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1854324

Summary: Add 'Abort' option after warning messages during installation
Product: [oVirt] ovirt-setup-lib Reporter: Asaf Rachmani <arachman>
Component: RFEsAssignee: Asaf Rachmani <arachman>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.3.0CC: bugs
Target Milestone: ovirt-4.4.1   
Target Release: 1.3.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-setup-lib-1.3.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-05 06:24:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1826875    

Description Asaf Rachmani 2020-07-07 07:55:49 UTC
Description of problem:

In some cases during the installation, there is an option to choose 'Yes' to continue or 'No' to change the value.
An 'Abort' option is missing (in order to abort the installation).


Example:
...
...
          Please specify the number of virtual CPUs for the VM (Defaults to appliance OVF value): [4]:
[WARNING] Minimum requirements not met by available memory: Required: 4096 MB. Available: 2283 MB
          Please specify the memory size of the VM in MB (Defaults to maximum available): [2283]:
[WARNING] Minimum requirements for memory size not met
          Continue with specified memory size? (Yes, No) [No]:

Comment 1 Petr Matyáš 2020-07-14 10:01:42 UTC
Verified on python3-ovirt-setup-lib-1.3.2-1.el8ev.noarch

Comment 2 Sandro Bonazzola 2020-08-05 06:24:49 UTC
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE.

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