Bug 38615

Summary: Profile based d-i installation: Update TEMPLATE
Product: UCS Reporter: Philipp Hahn <hahn>
Component: UCS InstallerAssignee: UCS maintainers <ucs-maintainers>
Status: RESOLVED WONTFIX QA Contact:
Severity: minor    
Priority: P5 CC: birkefeld, gohmann, grandjean, gulden, hahn, s.anders, schwardt, walkenhorst
Version: UCS 4.0   
Target Milestone: UCS 4.0-x   
Hardware: All   
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?: Yes
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: 35537, 36269, 36292, 38248    
Bug Blocks: 36488, 38509    

Description Philipp Hahn univentionstaff 2015-05-28 09:32:45 CEST 
Force auto-partition even on already installed systems and with multiple HD:
 d-i partman-auto/disk string /dev/sda /dev/sdb

Skip installing X-Server:
 d-i pkgsel/include string univention-system-setup-boot
univention-kernel-image openssh-server

ucs401 → ucs402
UCS-4.0-1 → UCS-4.0-2

+++ This bug was initially created as a clone of Bug #35537 +++
Comment 1 Janis Meybohm univentionstaff 2015-07-02 14:33:18 CEST 
For auto-updates:

univention-system-setup-boot update/system/after/setup boolean true
Comment 2 Philipp Hahn univentionstaff 2015-07-09 09:59:14 CEST 
d-i partman-partitioning/default_label select gpt
Comment 3 Florian Best univentionstaff 2017-06-28 14:52:45 CEST 
There is a Customer ID set so I set the flag "Enterprise Customer affected".
Comment 4 Stefan Gohmann univentionstaff 2019-01-03 07:17:20 CET 
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.