Created attachment 1346651 [details] errors on install freeipa module Description of problem: dnf module install freeipa fails. See the attachment for error logs. Version-Release number of selected component (if applicable): Image built with (KOJI composes): GIT: https://github.com/container-images/boltron-27 Base: Fedora-Modular-27-20171101.n.0 Image running aginst (KOJI Composes): Base: Fedora-Modular-27-20171101.n.1
Yes, this is known, being worked on, and should be fixed in tomorrow's nightly compose.
Proposed as a Blocker for 27-server-beta by Fedora user sgallagh using the blocker tracking app because: "The core functional requirements for all Featured Server Roles must be met, without any workarounds being necessary." Domain Controller (FreeIPA) is a Featured Server Role.
Discussed during blocker review [1]: AcceptedBlocker (Server Beta) - clear violation of Basic criterion "Release-blocking roles and the supported role configuration interfaces must meet the core functional Role Definition Requirements to the extent that supported roles can be successfully deployed, started, stopped, brought to a working configuration, and queried" [1] https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2017-11-02/
Should be fixed in the latest compose (Fedora-Modular-27-20171103.n.1)
Freeipa failed installation on Fedora-Modular-27-20171106.n.0 freeipa => Problem: problem with installed package coreutils-single-8.28-1.module_8a5444d0.x86_64n - package coreutils-8.28-1.module_8a5444d0.x86_64 conflicts with coreutils-single provided by coreutils-single-8.28-1.module_8a5444d0.x86_64n - package autofs-1:5.1.3-4.module_f875bec9.x86_64 requires sh-utils, but none of the providers can be installedn - package freeipa-client-4.6.1-3.module_f875bec9.x86_64 requires autofs, but none of the providers can be installed - conflicting requests See: [1] https://ci.centos.org/job/fedora-qa-compose-tests/134/artifact/compose-tests/mod_install_results.log [2] https://ci.centos.org/job/fedora-qa-compose-tests/134/artifact/compose-tests/error.log
For coreutils error, please consider if it's the same as for platform: https://github.com/modularity-modules/platform-placeholder/issues/2#issuecomment-339092727
(In reply to Irina Gulina from comment #5) > Freeipa failed installation on Fedora-Modular-27-20171106.n.0 > > freeipa => Problem: problem with installed package > coreutils-single-8.28-1.module_8a5444d0.x86_64n > - package coreutils-8.28-1.module_8a5444d0.x86_64 conflicts with > coreutils-single provided by coreutils-single-8.28-1.module_8a5444d0.x86_64n > > - package autofs-1:5.1.3-4.module_f875bec9.x86_64 requires sh-utils, but > none of the providers can be installedn > - package freeipa-client-4.6.1-3.module_f875bec9.x86_64 requires autofs, but > none of the providers can be installed > - conflicting requests > > See: > [1] > https://ci.centos.org/job/fedora-qa-compose-tests/134/artifact/compose-tests/ > mod_install_results.log > [2] > https://ci.centos.org/job/fedora-qa-compose-tests/134/artifact/compose-tests/ > error.log Could you please describe *exactly* what you did that failed? I can run `dnf install freeipa-server freeipa-server-dns` just fine. We do know that there is a lag with mirrors; it may be that you need to set the baseurl for the yum repo to the master compose path.
I can't reproduce this error; running `dnf module install freeipa` works fine for me on compose Fedora-Modular-27-20171105.n.3.
Created attachment 1348871 [details] dnf module install freeipa logs
@=(In reply to Stephen Gallagher from comment #8) > I can't reproduce this error; running `dnf module install freeipa` works > fine for me on compose Fedora-Modular-27-20171105.n.3. Please see the attachment in the previous comment.
(In reply to Irina Gulina from comment #10) > @=(In reply to Stephen Gallagher from comment #8) > > I can't reproduce this error; running `dnf module install freeipa` works > > fine for me on compose Fedora-Modular-27-20171105.n.3. > > Please see the attachment in the previous comment. Oh, so this is unique to the Docker container? We should probably revisit this as a Beta Blocker, then. The container base image is non-blocking for release.
It looks like the issue with 'coreutils' vs. 'coreutils-single'. Two implementations of the same thing, so they are conflicting with each other. AFAIK, all images ship with 'coreutils' exept for the docker image which uses 'coreutils-single'. And freeipa probably explicitly requires 'coreutils', and that's why it fails.
(In reply to Adam Samalik from comment #12) > It looks like the issue with 'coreutils' vs. 'coreutils-single'. Two > implementations of the same thing, so they are conflicting with each other. > > AFAIK, all images ship with 'coreutils' exept for the docker image which > uses 'coreutils-single'. And freeipa probably explicitly requires > 'coreutils', and that's why it fails. I just did some analysis. I'm reassigning it to coreutils because this will be a general issue with container images and is not specific to the modular release. autofs has `Requires: sh-util` which coreutils has as `Provides: sh-util` but coreutils-single does not have. So as of right now, it's not possible to install autofs on any system that is running coreutils-single. This is just one more in a long line of mistakes where the two subpackages don't Provides: the same content even though they are shipping the same functionality.
Ok, I will fix it.
Dropping "AcceptedBlocker" as this appears to only be an issue on non-blocking media at the moment.
Agreed, -1 blocker with new info. openQA confirms that FreeIPA role deployment on installs from the modular Server DVD works with recent composes.
-1 blocker since this is only for non-blocking media
"FreeIPA role deployment on installs from the modular Server DVD works with recent composes" = not-a-blocker from me.
If it wasn't clear, I'm also -1 blocker
Therefore rejected as a blocker.
The error changed: > sudo docker run bikeshed bash -l -c "dnf module install freeipa -y" ------------------------------- DNF ---------------------------------- Installed Packages dnf.noarch 2.7.3-1.module_bf3f917d.modularity.5.4edc03e @anaconda libdnf.x86_64 0.11.1-1.module_c8380439 @anaconda ---------------------------------------------------------------------- Image built with (KOJI composes): GIT: https://github.com/container-images/boltron-27 Base: Fedora-Modular-27-20171109.n.0 Image running aginst (KOJI Composes): Base: Fedora-Modular-27-20171109.n.0 Fedora Modular Server 27 - x86_64 - Test Update 141 kB/s | 20 kB 00:00 Fedora Modular Server 27 - x86_64 - Updates 142 kB/s | 20 kB 00:00 Fedora Modular Server 27 - x86_64 1.6 MB/s | 4.0 MB 00:02 Problem 1: package freeipa-server-4.6.1-3.module_f875bec9.x86_64 requires open-sans-fonts, but none of the providers can be installed - conflicting requests - nothing provides fontpackages-filesystem needed by open-sans-fonts-1.10-6.module_f875bec9.noarch Problem 2: package freeipa-server-dns-4.6.1-3.module_f875bec9.noarch requires freeipa-server = 4.6.1-3.module_f875bec9, but none of the providers can be installed - package freeipa-server-4.6.1-3.module_f875bec9.x86_64 requires open-sans-fonts, but none of the providers can be installed - conflicting requests - nothing provides fontpackages-filesystem needed by open-sans-fonts-1.10-6.module_f875bec9.noarch Problem 3: package freeipa-server-trust-ad-4.6.1-3.module_f875bec9.x86_64 requires freeipa-server = 4.6.1-3.module_f875bec9, but none of the providers can be installed - package freeipa-server-4.6.1-3.module_f875bec9.x86_64 requires open-sans-fonts, but none of the providers can be installed - conflicting requests - nothing provides fontpackages-filesystem needed by open-sans-fonts-1.10-6.module_f875bec9.noarch Problem 4: problem with installed package coreutils-single-8.28-1.module_8a5444d0.x86_64n - package coreutils-8.28-1.module_8a5444d0.x86_64 conflicts with coreutils-single provided by coreutils-single-8.28-1.module_8a5444d0.x86_64n - package autofs-1:5.1.3-4.module_f875bec9.x86_64 requires sh-utils, but none of the providers can be installed - package freeipa-client-4.6.1-3.module_f875bec9.x86_64 requires autofs, but none of the providers can be installed - conflicting requests
Discussed at 2017-11-09 Server Beta Go/No-Go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2017-11-09/f27-final-and-server-beta-go-no-go-meeting.2017-11-09-18.02.html . The new issue here is accepted as a 0-day blocker for Server Beta, as a clear violation of the requirement that release-blocking roles be deployable. In the past we have insisted on issues like this being fixed on the media, however we agreed that for the first Beta release of Modular Server it's okay to relax this a bit and allow for the issue to be fixed with a 0-day update; in practice we believe role deployment is more commonly done post-install (when it will pull from the repositories) than during installation (when only the packages from the media may be available).
This should be fixed in the repos as of Friday. I request that a QA person verify this so we can make sure it's ready for tomorrow.
>> sudo docker run bikeshed bash -l -c "dnf --allowerasing install coreutils -y && dnf module install freeipa -y && dnf module list" successfully installs freeipa on Fedora-Modular-27-20171113.n.0 <...> Complete! Non-fatal <unknown> scriptlet failure in rpm package nfs-utils Non-fatal <unknown> scriptlet failure in rpm package nfs-utils Non-fatal <unknown> scriptlet failure in rpm package nfs-utils Non-fatal <unknown> scriptlet failure in rpm package nfs-utils Non-fatal POSTIN scriptlet failure in rpm package freeipa-server-trust-ad Non-fatal POSTIN scriptlet failure in rpm package freeipa-server-trust-ad Last metadata expiration check: 0:15:04 ago on Mon 13 Nov 2017 01:29:28 PM UTC. Fedora Modular Server 27 - x86_64 Name Stream Version Profiles 389-ds 1.3 [d][e] 20171102233352 default X11-base f27 [d][e] 20171103131108 default apache-commons f27 [d][e] 20171018085030 default autotools f27 [d][e] 20171018090442 default bind 9 [d][e] 20171018084824 client, default, ... cloud-init f27 [d][e] 20171017101923 default fonts f27 [d][e] 20171109145641 default, everything freeipa 4.6 [d][e] 20171104182858 default [i] hardware-support f27 [d] 20171017135323 host f27 [d][e] 20171107172526 <...> tomcat master [d][e] 20170905122033 default udisks2 2 [d] 20171101182156 default Hint: [d]efault, [e]nabled, [i]nstalled, [l]ocked
openQA FreeIPA tests passed on the 2017113.n.1 compose, so looks good.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
We just never closed this...