Bug 1928326

Summary: Fedora-IoT Cannot Install cockpit-machines
Product: [Fedora] Fedora Reporter: u297b.fas
Component: IoTAssignee: Peter Robinson <pbrobinson>
Status: CLOSED EOL QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 33CC: dustymabe, jlebon, jonathan, lucab, miabbott, philip.wyett, robertthomasfairley, travier, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-30 18:00:53 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 u297b.fas 2021-02-13 02:18:26 UTC
Description of problem:

Some recent release broke the ability of Fedora-IoT to install cockpit-machines package. 

I have confirmed this by installing a fresh install into a VM and get the same error as on the production machine.

Version-Release number of selected component (if applicable):

NAME=Fedora
VERSION="33.20210128.0 (IoT Edition)"

#rpm-ostree status

* ostree://fedora-iot:fedora/stable/x86_64/iot
                   Version: 33.20210128.0 (2021-01-28T20:38:24Z)
                BaseCommit: 584b407eed8d529368b6ad67b67336eddaf951d923ece168032c468e0b45b5e3
              GPGSignature: Valid signature by 963A2BEB02009608FE67EA4249FD77499570FF31
           LayeredPackages: cockpit cockpit-composer htop virt-install

How reproducible:

Always

Steps to Reproduce:
1. Install Fedora-Iot
2. rpm-ostree install cockpit-machines


Actual results:

Here is the error:

# rpm-ostree install cockpit-machines

Checking out tree 584b407... done
Enabled rpm-md repositories: fedora-cisco-openh264 fedora updates
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2020-08-25T19:10:34Z
rpm-md repo 'fedora' (cached); generated: 2020-10-19T23:27:19Z
rpm-md repo 'updates' (cached); generated: 2021-02-12T01:27:30Z
Importing rpm-md... done
Resolving dependencies... done
error: Could not depsolve transaction; 1 problem detected:
 Problem: conflicting requests
  - package cockpit-machines-229-1.fc33.noarch requires libvirt-daemon-kvm, but none of the providers can be installed
  - package cockpit-machines-237-1.fc33.noarch requires libvirt-daemon-kvm, but none of the providers can be installed
  - package libvirt-daemon-kvm-6.6.0-2.fc33.x86_64 requires libvirt-daemon-driver-qemu = 6.6.0-2.fc33, but none of the providers can be installed
  - package libvirt-daemon-kvm-6.6.0-5.fc33.x86_64 requires libvirt-daemon-driver-qemu = 6.6.0-5.fc33, but none of the providers can be installed
  - package libvirt-daemon-driver-qemu-6.6.0-2.fc33.x86_64 requires systemd-container, but none of the providers can be installed
  - package libvirt-daemon-driver-qemu-6.6.0-5.fc33.x86_64 requires systemd-container, but none of the providers can be installed
  - package systemd-container-246.6-3.fc33.i686 requires libpthread.so.0, but none of the providers can be installed
  - package systemd-container-246.6-3.fc33.i686 requires libpthread.so.0(GLIBC_2.0), but none of the providers can be installed
  - package systemd-container-246.6-3.fc33.i686 requires libpthread.so.0(GLIBC_2.1), but none of the providers can be installed
  - package systemd-container-246.6-3.fc33.i686 requires libpthread.so.0(GLIBC_2.2), but none of the providers can be installed
  - package systemd-container-246.6-3.fc33.i686 requires ld-linux.so.2, but none of the providers can be installed
  - package systemd-container-246.6-3.fc33.i686 requires ld-linux.so.2(GLIBC_2.3), but none of the providers can be installed
  - package systemd-container-246.6-3.fc33.i686 requires libc.so.6(GLIBC_2.30), but none of the providers can be installed
  - package systemd-container-246.10-1.fc33.i686 requires libpthread.so.0, but none of the providers can be installed
  - package systemd-container-246.10-1.fc33.i686 requires libpthread.so.0(GLIBC_2.0), but none of the providers can be installed
  - package systemd-container-246.10-1.fc33.i686 requires libpthread.so.0(GLIBC_2.1), but none of the providers can be installed
  - package systemd-container-246.10-1.fc33.i686 requires libpthread.so.0(GLIBC_2.2), but none of the providers can be installed
  - package systemd-container-246.10-1.fc33.i686 requires ld-linux.so.2, but none of the providers can be installed
  - package systemd-container-246.10-1.fc33.i686 requires ld-linux.so.2(GLIBC_2.3), but none of the providers can be installed
  - package systemd-container-246.10-1.fc33.i686 requires libc.so.6(GLIBC_2.30), but none of the providers can be installed
  - package systemd-container-246.6-3.fc33.x86_64 requires systemd(x86-64) = 246.6-3.fc33, but none of the providers can be installed
  - package systemd-container-246.10-1.fc33.x86_64 requires systemd(x86-64) = 246.10-1.fc33, but none of the providers can be installed
  - glibc-2.32-1.fc33.i686 has inferior architecture
  - glibc-2.32-4.fc33.i686 has inferior architecture
  - cannot install both systemd-246.6-3.fc33.x86_64 and systemd-246.7-2.fc33.x86_64
  - cannot install both systemd-246.10-1.fc33.x86_64 and systemd-246.7-2.fc33.x86_64
  - cannot install both glibc-2.32-1.fc33.x86_64 and glibc-2.32-3.fc33.x86_64
  - cannot install both glibc-2.32-4.fc33.x86_64 and glibc-2.32-3.fc33.x86_64

Comment 1 Jonathan Lebon 2021-02-16 22:06:55 UTC
Whenever you see "cannot install both ...", this means it's an instance of https://github.com/coreos/fedora-coreos-tracker/issues/400 (see also https://github.com/coreos/rpm-ostree/issues/415).
This is fixed in FCOS and Fedora Silverblue by shipping the archive repo:
- https://github.com/coreos/fedora-coreos-config/pull/673
- https://pagure.io/workstation-ostree-config/pull-request/184

Fedora IoT should probably do the same thing (i.e. ship the archive repo in the OSTree).
For now, upgrading before installing should help.

Comment 2 Ben Cotton 2021-11-04 16:04:46 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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.

Comment 3 Ben Cotton 2021-11-30 18:00:53 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.