podman 1.5 - json-file logging specified but not supported. Choosing k8s-file logging instead
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Cédric Jeanneret |
Bug Description
Description
===========
Overcloud deployment fails with below error when using overcloud-full.tar image which downloaded from rdo_trunk [https:/
```
ERROR: 28409 -- ['/usr/bin/podman', 'start', '-a', u'container-
```
I think this is related to podman version 1.5, which doesn't have json-file logging driver. The image includes this version.
The undercloud has podman version 1.4 and if I built the overcloud-full image in undercloud then overcloud nodes have this version as well.
Steps to reproduce
==================
1 - Build container images with `openstack tripleo container image prepare default --local-
2 - Install overcloud
3 - Check undercloud's podman version:
```
(undercloud) [stack@undercloud ~]$ sudo podman info
host:
BuildahVersion: 1.9.0
Conmon:
package: podman-
path: /usr/libexec/
version: 'conmon version 0.3.0, commit: unknown'
```
3 - Check one of the container's LogConfig information by inspecting it.
```
(undercloud) [stack@undercloud ~]$ sudo podman inspect 99dfb9997f099
},
```
3 - Download overcloud-full image from rdo_trunk and upload it to glance.
```
(undercloud) [stack@undercloud ~]$ cd ~/images
(undercloud) [stack@undercloud ~]$ curl -o ironic-
(undercloud) [stack@undercloud ~]$ curl -o overcloud-full.tar https:/
for x in overcloud-full.tar ironic-
```
4 - Run overcloud deployment.
Expected result
===============
Podman should run the containers on overcloud nodes.
Actual result
=============
Deployment fails with an error about to logging driver.
```
ERROR: 28409 -- ['/usr/bin/podman', 'start', '-a', u'container-
```
Environment
===========
1. Version: Stein
Changed in tripleo: | |
importance: | Undecided → High |
milestone: | none → train-rc1 |
Fix proposed to branch: master /review. opendev. org/683937
Review: https:/