Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2119788 - F38FailsToInstall: kubernetes-kubeadm
Summary: F38FailsToInstall: kubernetes-kubeadm
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kubernetes
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anthony Rabbito
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2045288
Blocks: F38FailsToInstall
TreeView+ depends on / blocked
 
Reported: 2022-08-19 12:47 UTC by Miro Hrončok
Modified: 2022-08-20 00:10 UTC (History)
11 users (show)

Fixed In Version: cri-tools-1.24.2-1.fc38
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-19 20:48:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2022-08-19 12:47:13 UTC
Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

Your package (kubernetes) Fails To Install in Fedora 38:

can't install kubernetes-kubeadm:
  - nothing provides cri-tools needed by kubernetes-kubeadm-1.24.4-1.fc38.x86_64
  
If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.


If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.


P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock:

    $ mock -r fedora-38-x86_64 --config-opts mirrored=False install kubernetes-kubeadm


P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages

Thanks!

Comment 1 Maxwell G 2022-08-19 20:48:30 UTC
cri-tools-1.24.2-1.fc38 has been built in rawhide. It was available in f37, but it seems not to have been branched properly.

Comment 2 Brad Smith 2022-08-19 22:04:42 UTC
Thanks for the assist. If I understand the cri-o module correctly, cri-tools is packaged as part of the cri-o module, although as far as I can tell cri-tools is not modularized per se. Will the cri-o module need to be refreshed to pick up the cri-tools update?

Comment 3 Maxwell G 2022-08-19 22:46:34 UTC
(In reply to Brad Smith from comment #2)
> Thanks for the assist. If I understand the cri-o module correctly, cri-tools
> is packaged as part of the cri-o module, although as far as I can tell
> cri-tools is not modularized per se. Will the cri-o module need to be
> refreshed to pick up the cri-tools update?

I did not see this comment before I wrote my comment about modules on the other issue.

The modular and non-modular packages are built separately. I only touched the non-modular package. I'm not sure about the history of these packages or why they were built as modules in the first place. I am not really a maintainer of this package. I saw it pop up on the list of Go packages that failed to build from source in the F37 Rebuild and performed the latest update as a member of the Go SIG.

Comment 4 Brad Smith 2022-08-20 00:10:19 UTC
(In reply to Maxwell G from comment #3)
 
> I did not see this comment before I wrote my comment about modules on the
> other issue.
> 
> The modular and non-modular packages are built separately. I only touched
> the non-modular package. I'm not sure about the history of these packages or
> why they were built as modules in the first place. I am not really a
> maintainer of this package. I saw it pop up on the list of Go packages that
> failed to build from source in the F37 Rebuild and performed the latest
> update as a member of the Go SIG.
 
Much appreciated! Hopefully Peter will have a spare cycle soon and provide clarity on what is needed. I added a comment on https://bugzilla.redhat.com/show_bug.cgi?id=2045288 that reflects my understanding of versioning for cri-tools, cri-o and kubernetes (basically they should be in sync on majrr:minor versions).


Note You need to log in before you can comment on or make changes to this bug.