Bug 1861848
| Summary: | Error: in /etc/cni/net.d/87-podman-bridge.conflist: error parsing configuration list: unexpected end of JSON input | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Maciej Relewicz <mrelewicz> |
| Component: | tripleo-ansible | Assignee: | OSP Team <rhos-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Joe H. Rahme <jhakimra> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 16.1 (Train) | CC: | amcleod, cjeanner, cpippin, dmacpher, drosenfe, hbrock, jslagle, mburns, rhos-maint, rurena |
| Target Milestone: | beta | Keywords: | Triaged |
| Target Release: | 17.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tripleo-ansible-3.0.1-0.20210221001954.c739f33.el8ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-09-21 12:11:25 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
Maciej Relewicz
2020-07-29 17:46:08 UTC
Thank you for this report! The issue is here: https://opendev.org/openstack/tripleo-ansible/src/branch/master/tripleo_ansible/roles/tripleo_podman/tasks/tripleo_podman_install.yml#L46 If we ensure it's a valid, empty JSON, we should be covered. I'll push a change shortly against master. Cheers, C. Hello,
Some news about this issue:
- I had to revert my patch - podman has a strict(er) JSON parser, so we can't just put an empty "{}" in the file.
- OSP doesn't use the CNI bridge, since it's using the "network=host" feature. The removal was in order to ensure there isn't any network overlap. The removal first involved the file removal itself, but apparently this might lead to other issues with RPM directly[1].
So the best thing to do is to move this BZ to Doc, so that a note is created (KB, or within some page about podman usage in OSP) stating that "podman network subcommands are not supported within an OSP deployment".
@Maciej: is this OK with you? Any use-case for that `podman network ls' on an OSP environment?
@Doc Team: feel free to ping me if you need more info or any confirmation
Moving this to Doc, setting as New and removing the "Triaged" kw.
Cheers,
C.
[1] https://review.opendev.org/#/c/630625 you can see the comments about this issue
is there an update on which z-stream this fix will be available? Rafael Ureña Technical Account Manager We don't support running any containers with a podman network at this time. IN OSP17, we will stop removing this default network and there will be a default network 10.255.255.0/24 with a gateway 10.255.255.1. We will still likely not support any containers leveraging this, but that does mean that the `podman network` commands will no longer error. Requests for backports to 16.x will need to go through PM. sudo podman network ls does not display an error: (undercloud) [stack@undercloud-0 ~]$ sudo podman network ls NETWORK ID NAME DRIVER 2f259bab93aa podman bridge 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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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/RHEA-2022:6543 |