Bug 2002668
Summary: | workstation profile is not applied correctly when installing workstation from netinst | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 35 | CC: | anaconda-maint-list, hdegoede, jonathan, kellin, vanmeeuwen+fedora, vondruch, vponcova, w |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-09-20 15:31: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
Kamil Páral
2021-09-09 13:18:38 UTC
Hi, Anaconda profiles are not chosen based on the software selection, but based on the installation environment. The profiles change the default configuration and we need to be able to finalize it before we run anything else. It should be documented here: https://anaconda-installer.readthedocs.io/en/latest/configuration-files.html The solution you suggest would require a completely different approach. However, I'm afraid it would only cause more confusion. If users choose the Server environment, do the automated partitioning, switch to the Workstation environment and start the installation, they will end up with a mix of configurations for Server and Workstation. That seems worse than the current situation. The profile can be changed with the inst.profile boot option. The easiest fix could be to extend the boot menu of the installation image and add new items for the profiles you want to support. That wouldn't require any changes in Anaconda and avoid issues mentioned above. I just learned about inst.profile. I can confirm that with "inst.profile=fedora-workstation", the netinst boots branded as Fedora Workstation, and the disk layout and grub2 configuration (menu_auto_hide=1) is applied correctly. I was hoping that at least some of those options (like grub configuration) can be applied based on what software selection the user picked. I understand that for e.g. default disk layout that might be more difficult. But if it is overall technically hard to do, that's unfortunate. The boot menu selection is a good idea, though, thank you. *** Bug 2001885 has been marked as a duplicate of this bug. *** |