Description of problem: Attempt to list pod sandboxes with crictl fails. Version-Release number of selected component (if applicable): cri-tools-1.11.0-2.dev.git19b7255.fc29.x86_64 cri-o-1.12.0-12.dev.gitc4f232a.fc29.x86_64 runc-1.0.0-68.dev.git6635b4f.fc29.x86_64 How reproducible: Deterministic. Steps to Reproduce: 1. dnf install -y runc cri-o crictl 2. systemctl start crio 3. crictl pods Actual results: FATA[0000] listing pod sandboxes failed: unsupported output format "" Expected results: POD ID CREATED STATE NAME NAMESPACE ATTEMPT Additional info:
Is this caused by a mismatch of versions? Do we need to update the released version of cri-o to 1.13?
this seems to be an issue in crictl. Could you try overriding the output, something like: crictl pods --output=table
# crictl pods --output=table POD ID CREATED STATE NAME NAMESPACE ATTEMPT
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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.
Updating version because we have a reason to believe the issue is still present on Fedora 30. Unfortunately, on Fedora 30, we are currently blocked by bug 1743017 a.k.a. bug 1754170 a.k.a. but 1740730, so I couldn't test there.
Hi Jan, For the issue on Fedora 30, the crio path set in the crio and crio-wipe service doesn't match where crio is actually installed. We are getting this fixed in the package for fedora 30. For the Fedora 29 issue with crictl pods, I am unable to reproduce with the steps outlined in the description. I am also not seeing this issue on a Fedora 30 box. If you have a box I can ssh onto to further debug, that would be helpful.
Just checked and the fix is in cri-o-1.14.12-2.module_f30+8228+c27616c5.x86_64. Can you run the beaker job again to pick up the newer cri-o package and see if it is successful.