Univention Bugzilla – Full Text Bug Listing |
Summary: | System setup should warn if RAM is insufficient. | ||
---|---|---|---|
Product: | UCS | Reporter: | Arvid Requate <requate> |
Component: | UMC - Setup wizard | Assignee: | Florian Best <best> |
Status: | CLOSED FIXED | QA Contact: | Drees Dormann <dormann> |
Severity: | normal | ||
Priority: | P5 | CC: | damrose, gohmann, gulden, klaeser, walkenhorst |
Version: | UCS 4.0 | ||
Target Milestone: | UCS 4.0-1-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
What kind of report is it?: | --- | What type of bug is this?: | --- |
Who will be affected by this bug?: | --- | How will those affected feel about the bug?: | --- |
User Pain: | Enterprise Customer affected?: | ||
School Customer affected?: | ISV affected?: | ||
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | Bug group (optional): | ||
Max CVSS v3 score: | |||
Bug Depends on: | |||
Bug Blocks: | 50448 | ||
Attachments: |
Screenshot
Screenshot2 Screenshot Warning icon |
Description
Arvid Requate
2014-11-05 18:13:22 CET
Happened again, I've installed UCS with a mailserver and I had only 512 MB. The installation was not successful. Created attachment 6759 [details]
Screenshot
Attached a screenshot. Please give your opinions. Would you like the popup immediately? Or when visiting the summary. It could also be added as text to the summary.
Created attachment 6760 [details]
Screenshot2
(In reply to Florian Best from comment #2) > Would you like the popup immediately? Or when visiting the summary. It could > also be added as text to the summary. I think a dedicated popup is the best solution. It should explicitly state that setup may fail of the user chooses to continue. Bonus: It would be great if we add a "shutdown" button here, to give the user the possibility to exit system setup in a controlled way. I am using 512MB as default value as our quick start guide suggests this: http://docs.univention.de/quickstart-en-4.0.html It is configurable via the UCR variable 'system/setup/boot/minimal_memory' which can be set e.g. in appliance scenarios to the value of MinPhysicalRAM from the ini file. Even if the value is lower than that 512MB is used as the absolute minimum. Should I raise the value from 512 to a higher value as the installation will fail with a mailserver? IMHO we should touch the release notes for that value. (In reply to Erik Damrose from comment #4) > I think a dedicated popup is the best solution. It should explicitly state > that setup may fail of the user chooses to continue. Bonus: It would be > great if we add a "shutdown" button here, to give the user the possibility > to exit system setup in a controlled way. In the first step no shutdown button is added. The implementation of such a button wouldn't be hard (but ACL settings may be). Created attachment 6771 [details]
Screenshot
better?
The message is now displayed when entering the summary page. Fix: svn r59221, r59230 YAML: 2015-03-09-univention-system-setup.yaml Created attachment 6776 [details]
Warning icon
Stylwise, it would be good not to use (obsolete) icons from the oxygen icon set. I attach an alternative in a correct style fitting also the colour scheme.
Message is displayed: OK
text: "... kaputten oder aufgehängten System führen..."
>> maybe better: ".. kaputten oder nicht reagierenden System..."
Yaml: line 12 ...too few
(In reply to Alexander Kläser from comment #8) > Created attachment 6776 [details] > Warning icon > > Stylwise, it would be good not to use (obsolete) icons from the oxygen icon > set. I attach an alternative in a correct style fitting also the colour > scheme. Adapted in UDM (AD-connector warning) and system-setup. (In reply to Drees Dormann from comment #9) > text: "... kaputten oder aufgehängten System führen..." > >> maybe better: ".. kaputten oder nicht reagierenden System..." yes, good suggestion! > Yaml: line 12 ...too few fixed. (In reply to Drees Dormann from comment #9) > Message is displayed: OK > > text: "... kaputten oder aufgehängten System führen..." > >> maybe better: ".. kaputten oder nicht reagierenden System..." "kaputt" seems to be too much colloquial style, IMHO. I'd suggest "... kann zu nicht funktionsfähigen oder nicht mehr reagierenden Sytemen...". Text changes in svn r59346. Package currently builds. Text: OK Yaml: OK |