https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/COE-43 coe <p>In <a href="https://jira.opendaylight.org/browse/COE-36" title="Get CoE as-is manually running on K8s an OpenStack (RDO) Cloud" class="issue-link" data-issue-key="COE-36"><del>COE-36</del></a> we noticed that "ovs-vsctl show" shows <tt>veth</tt> ports with Interface <tt>error: "could not open network device veth9e3d3ff1 (No such device)"</tt> ... according to <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=k.faseela" class="user-hover" rel="k.faseela">k.faseela</a>:</p> <blockquote><p>These veth ports error won't cause any issue for you, they are actually stale veth ports that remain. I have seen the same issue, but have not clearly seen when they start showing up, but ofcourse this is a bug.</p></blockquote> COE-43

veth interface error: "could not open network device veth9e3d3ff1 (No such device)"

Bug Medium Verified Done Faseela K Michael Vorburger Wed, 5 Dec 2018 16:24:36 +0000 Wed, 23 Jan 2019 04:53:55 +0000 Mon, 21 Jan 2019 06:54:56 +0000 0 3 <p><tt>sudo ovs-vsctl del-port veth741cafb2</tt> let's one manually delete such ports. We suspect that they are for some reason left over after a <tt>kubectl delete pod</tt> (see also <a href="https://jira.opendaylight.org/browse/COE-45" title="CoE Pod deletion causes ervice-mode-ingress}] does not exist. Cannot apply modification to its children." class="issue-link" data-issue-key="COE-45">COE-45</a>, although <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=k.faseela" class="user-hover" rel="k.faseela">k.faseela</a> says that "that exception will not cause port not to be deleted from switch").</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=serngawy" class="user-hover" rel="serngawy">serngawy</a>, on IRC <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=k.faseela" class="user-hover" rel="k.faseela">k.faseela</a> suggested that I assign this to you...</p> <p><a href="https://jira.opendaylight.org/browse/COE-45" title="CoE Pod deletion causes ervice-mode-ingress}] does not exist. Cannot apply modification to its children." class="issue-link" data-issue-key="COE-45">COE-45</a> may be related to this?</p> <p>This happen because of changing the iface-id to (cluster-id and podname) instead of (namespace and podname) check <span class="error">&#91;0&#93;</span>. I don't really understand what is the purpose of doing that, you still can create 2 pods with the same name in the same cluster under 2 different namespace. "cluster-id and podname" is not a unique identifier. </p> <p><span class="error">&#91;0&#93;</span> <a href="https://github.com/opendaylight/coe/blob/master/odlCNIPlugin/odlovs-cni/ovs_odl.go#L196" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/opendaylight/coe/blob/master/odlCNIPlugin/odlovs-cni/ovs_odl.go#L196</a></p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=Karthika_rp" class="user-hover" rel="Karthika_rp">Karthika_rp</a> : Could you please verify if the issue is not reproducible on latest master CSIT and close this JIRA?</p> Blocks COE-46 Development Rank 0|i03lbz: