Bug 2161693

Summary:	podman can not create network directory if it is not exist when it works with cni
Product:	Red Hat Enterprise Linux 8	Reporter:	Joy Pu <ypu>
Component:	podman	Assignee:	Tom Sweeney <tsweeney>
Status:	CLOSED DUPLICATE	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.8	CC:	bbaude, dwalsh, jligon, jnovy, lsm5, mboddu, mheon, pthomas, umohnani
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-17 16:10:10 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 Joy Pu 2023-01-17 16:07:26 UTC

Description of problem:

Podman can not create network directory if it is not exist when it works with cni. So the podman create will failed with "Error: stat /etc/cni/net.d/: no such file or directory"


Version-Release number of selected component (if applicable):
podman-4.4.0-0.1.module+el8.8.0+17823+c4e3c815.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Create a container or pod with podman in a new installed system
# podman create --name test_cni_dir quay.io/libpod/busybox top

Error: stat /etc/cni/net.d/: no such file or directory



Actual results:
The command failed with error no such file or directory

Expected results:
podman command can create the directory and finished succeed. 

Additional info:

Comment 1 Joy Pu 2023-01-17 16:10:10 UTC


*** This bug has been marked as a duplicate of bug 2161682 ***