Univention Bugzilla – Full Text Bug Listing |
Summary: | No automatic UCC rollout when a previous version is already installed | ||
---|---|---|---|
Product: | Z_Univention Corporate Client (UCC) | Reporter: | Erik Damrose <damrose> |
Component: | Client management | Assignee: | Erik Damrose <damrose> |
Status: | CLOSED FIXED | QA Contact: | Lukas Walter <walter> |
Severity: | normal | ||
Priority: | P5 | CC: | jmm |
Version: | unspecified | Keywords: | interim-2 |
Target Milestone: | UCC 2.0 | ||
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: |
Description
Erik Damrose
2013-02-13 17:11:39 CET
As it happens, there already is such a boot option - force_partition. It was just implemented erroneously. QA should check if an UCC client can always be forced to repartition/reinstall - with PXE or local boot. After verification, we should document this boot parameter r49525 univention-ucc-initramfs 3.0.0-11.100.201404231333 Boot option "force_partition" is working fine, overriding the "continuation_prompt" parameter contained in the image build configuration file. Changelog: ok. VERIFIED UCC 2.0 has been released: http://docs.univention.de/release-notes-ucc-2.0.html If this error occurs again, please use "Clone This Bug". |