Bug 1056975
Summary: | oVirt live on CentOS - ugly warnings on the Terminal screen | ||
---|---|---|---|
Product: | [Retired] oVirt | Reporter: | Oved Ourfali <oourfali> |
Component: | ovirt-live | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Antonin Pagac <apagac> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.4 | CC: | eedri, gklein, iheim, oschreib, sbonazzo, ybronhei |
Target Milestone: | --- | Keywords: | UserExperience |
Target Release: | 3.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | integration | ||
Fixed In Version: | ovirt-3.5.0-beta2 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-09-23 10:28:02 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
Oved Ourfali
2014-01-23 09:34:10 UTC
Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc. not only that, when picking interactive it prints: Excecuting gnome-terminal --command="sudo /usr/bin/engine-setup";sleep 20 Failed to parse arguments: Argument to "--command/-e" is not a valid command: Text ended before matching quote was found for ". (The text was '"sudo') and if this bug is about ugly warnings, when picking automatic installation (oVirt-Live-1.1), we have the print : [WARNING] Warning: Not enough memory is available on the host. Minimum requirement is 4096MB, and 16384MB is recommended. without the actual size of memory the host contain, I'd add it to the print. This is an automated message. oVirt 3.4.1 has been released. This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed. This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step. If you think this bug should be verified by QE, please set its severity to high and move it back to ON_QA |