Bug 1583591
Summary: | Podman should be installed in all nodes using cri-o | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Eduardo Minguez <eminguez> |
Component: | Containers | Assignee: | Mrunal Patel <mpatel> |
Status: | CLOSED ERRATA | QA Contact: | weiwei jiang <wjiang> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.9.0 | CC: | aos-bugs, dmoessne, hongli, jokerman, mmccomas, mpatel, wmeng |
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
Feature: Add podman to rhcos.
Reason: Help debugging and troubleshooting.
Result: Added.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:40:21 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1589013 |
Description
Eduardo Minguez
2018-05-29 10:16:15 UTC
Also cri-tools should be installed. Antonio was already looking at adding this for 3.10. Sorry, meant to provide more info before sending this over. It looks like cri-tools shipped in OCP 3.9 and newer channels. And podman is in RHEL 7.5 channels so both packages should be readily available. we don't have full podman integration with CRI-O right now right? crictl should be enough for debugging afaict. Dan wdyt? Mrunal, agree this is not a 3.10 blocker? podman's libpod isn't yet integrated with CRI-O so it isn't ready for debugging CRI-O yet. It can be used to manage images but not the runtime side. It shouldn't be a blocker for 3.10. Verified according to https://bugzilla.redhat.com/show_bug.cgi?id=1583591#c11 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758 |