Bug 1877933
Summary: | kata-operator deploy does not clean up after itself when install fails | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Cameron Meadors <cmeadors> |
Component: | sandboxed-containers | Assignee: | Jens Freimann <jfreiman> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Cameron Meadors <cmeadors> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 4.6 | CC: | aadam, aos-bugs, jfreiman |
Target Milestone: | --- | ||
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: | 2021-04-12 09:08:49 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
Cameron Meadors
2020-09-10 19:24:44 UTC
I created a PR [1] to clean up the temporary directories automatically when the pods are stopped. [1] https://github.com/openshift/kata-operator/pull/8 My way of reproducing a failed install seems to have been completely resolved, https://bugzilla.redhat.com/show_bug.cgi?id=1877934. Install works with either v1.0 or 4.6 as versions. This is expected and good, but make this bug hard to verify. Any suggestions on how to get a failed install? I could provide you a private build of the commit before PR #8 was merged. Would that help? If that is no trouble, yes. Then I could positively verify this and close it. Just hit this again. Failed install, uninstalled, and reinstalled with the error in the original description. I suspect a build issue is giving me an older version where this is not fixed. I am changing this back to Verified until I know otherwise. Forgot that I VERIFIED based on so assumptions, like we had a good install. Since we still see operator install failures I am going to put this in ON_QA until I am actually confirm it is fixed. and kata-operator-daemon: https://github.com/harche/kata-operator-daemon/pull/18 I have retested on our latest build for kata-operator (commit 723d90e) on 4.6 rc4. I have installed and interrupted the install a various points by deleting the kataconfig and subsequent installs still work. Developer testing was more specific but on a dev environment. With that I am saying this is tested well enough for 4.6. |