This repository has been archived by the owner on May 12, 2021. It is now read-only.
When createNetwork failed, it should rollback the NetNs it created #508
Comments
lifupan
added a commit
to hyperhq/kata-runtime
that referenced
this issue
Jul 24, 2018
When createNetwork failed, cleanup the NetNs if it created. Fixes: kata-containers#508 Signed-off-by: fupan <[email protected]>
lifupan
added a commit
to hyperhq/kata-runtime
that referenced
this issue
Jul 24, 2018
When createNetwork failed, cleanup the NetNs if it created. Fixes: kata-containers#508 Signed-off-by: fupan <[email protected]>
devimc
pushed a commit
to jcvenegas/runtime
that referenced
this issue
Jul 25, 2018
When createNetwork failed, cleanup the NetNs if it created. Fixes: kata-containers#508 Signed-off-by: fupan <[email protected]>
egernst
pushed a commit
that referenced
this issue
Aug 22, 2018
When createNetwork failed, cleanup the NetNs if it created. Fixes: #508 Signed-off-by: fupan <[email protected]>
egernst
pushed a commit
that referenced
this issue
Aug 23, 2018
When createNetwork failed, cleanup the NetNs if it created. Fixes: #508 Signed-off-by: fupan <[email protected]>
zklei
pushed a commit
to zklei/runtime
that referenced
this issue
Jun 13, 2019
channel: Check for channel type in kernel cmdline options
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When createNetwork failed, it should rollback the NetNs it created
When createNetwork failed, kata will leave the redundant NetNs in the system
Expected result
When createNetwork failed, it should rollback the NetNs it created
Actual result
(replace this text with details of what actually happened)
(replace this text with the output of the
kata-collect-data.shscript, afteryou have reviewed its content to ensure it does not contain any private
information).
The text was updated successfully, but these errors were encountered: