Bug 1854324 - Add 'Abort' option after warning messages during installation
Summary: Add 'Abort' option after warning messages during installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-setup-lib
Classification: oVirt
Component: RFEs
Version: 1.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.4.1
: 1.3.2
Assignee: Asaf Rachmani
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks: 1826875
TreeView+ depends on / blocked
 
Reported: 2020-07-07 07:55 UTC by Asaf Rachmani
Modified: 2020-08-05 06:24 UTC (History)
1 user (show)

Fixed In Version: ovirt-setup-lib-1.3.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-05 06:24:49 UTC
oVirt Team: Integration
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 110126 0 master MERGED queryEnvKey: Add 'Abort' option for warning message 2020-07-12 14:29:40 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.