Open karypid opened 2 months ago
travier
commented
2 months ago Thanks a lot for doing this. I'll look at why those packages are not included in Silverblue even though they are in Workstation. I think we should just add them if it's the case.
travier
commented
2 months ago The sum of all the sizes mentioned above is 3735426 so about 3MB which is negligible for Silverblue so definitely voting in favor of inclusion.
travier
commented
2 months ago From the comps groups:
<group>
<id>domain-client</id>
<_name>Domain Membership</_name>
<_description>Support for joining a FreeIPA or Active Directory Domain</_description>
<default>false</default>
<packagelist>
<packagereq type="mandatory">adcli</packagereq>
<packagereq type="mandatory">freeipa-client</packagereq>
<packagereq type="mandatory">oddjob-mkhomedir</packagereq>
<packagereq type="mandatory">samba-common-tools</packagereq>
<packagereq type="mandatory">samba-winbind</packagereq>
<packagereq type="mandatory">sssd-ad</packagereq>
<packagereq type="mandatory">sssd-ipa</packagereq>
<packagereq type="default">libsss_autofs</packagereq>
<packagereq type="default">libsss_sudo</packagereq>
<packagereq type="default">sssd-nfs-idmap</packagereq>
</packagelist>
</group>I'm tempted to add all of those.
travier
commented
2 months ago <environment>
<id>workstation-product-environment</id>
<!-- Translators: Don't translate this product name -->
<_name>Fedora Workstation</_name>
<_description>Fedora Workstation is a user friendly desktop system for laptops and PCs.</_description>
<display_order>2</display_order>
<!-- Keep this list in sync with the list in fedora-workstation-common.ks. -->
<grouplist>
<groupid>container-management</groupid>
<groupid>core</groupid>
<groupid>desktop-accessibility</groupid>
<groupid>firefox</groupid>
<groupid>fonts</groupid>
<groupid>gnome-desktop</groupid>
<groupid>guest-desktop-agents</groupid>
<groupid>hardware-support</groupid>
<groupid>libreoffice</groupid>
<groupid>multimedia</groupid>
<groupid>networkmanager-submodules</groupid>
<groupid>printing</groupid>
<groupid>workstation-product</groupid>
</grouplist>
<optionlist>
<groupid>arm-tools</groupid>
<groupid>domain-client</groupid>
<groupid default="true">base-x</groupid>
</optionlist>
</environment>It's in the optionlist here. Not sure what this means.
From https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups:
All optional groups (defined by the group keyword) for that environment (listed in the environment's optionlist) are shown at the top of the right-hand pane.
travier
commented
2 months ago travier
commented
2 months ago Precision: I did a fresh install of Fedora Workstation 40 and it's not installed by default.
AdamWill
commented
2 months ago On Workstation and other non-atomic installs, if you try to enrol into a realm via realmd - e.g. via the button on gnome-initial-setup for this, or using cockpit, or running realm join at a console - realmd will automatically install the appropriate client packages (it doesn't install this package group, it has its own list of appropriate packages for different types of realm on different distros, and uses packagekit directly to install whatever it decides is appropriate. which I hate because it isn't logged anywhere, but that's by the by!)
karypid
commented
2 months ago Apologies, I simply assumed that Workstation just had the required packages pre-installed.
This is an interesting situation, I wonder how an "atomic" distro should handle this...
Should I close this bug then? Let the discussion resume in https://github.com/fedora-silverblue/issue-tracker/issues/320
AdamWill
commented
2 months ago no, no, I think it's fairly reasonable for Silverblue to just bake the packages in since they can't be installed on-demand, as the PR does. at least for now, until maybe the OCI stuff is further along and we can say it's totally normal to layer the additional packages in, or something.
travier
commented
2 months ago That's the direction I'm leaning as well (including until we move to OCI images).
Please try to answer the following questions about the package you are requesting:
Is the package installed by default in Fedora Workstation? YES
What, if any, are the additional dependencies on the package?
In order to join an active directory domain and perform "Enterprise Login", Fedora needs these packages. In Fedora Workstation they are present and you can do this without issue. In Silverblue the GUI hangs with no error, and the system log shows that the reason it's not working is these missing packages.
Bug: https://github.com/fedora-silverblue/issue-tracker/issues/320 Discussions thread: https://discussion.fedoraproject.org/t/bug-in-f40-packages-missing-for-ad-integration/112410/3
I am not sure.
No (n/a)
Yes, provided you are investigating AD networking problems. The samba-common-tools package has the "net" command which has useful utilities for domain operations. Same for adcli which allows you to check users, computer accounts, etc.
rpm-ostree install <package>? Explain why or why not.Yes, this is what I do in order to get things to work. I am able to join the domain and login using AD accounts.
My 5 cents is that Silverblue should pick a consistent option, that is either:
1) Include these to be in-sync with Fedora workstation 2) Modify the GNOME settings panel for Users to include auto-installing "on the fly" if the user chooses to join a domain. This way they are not 3) At least show a proper message if the user tries to add an Enterprise Login account, explaining that the packages are missing and the user must install them manually.