Bug 2069968 - Kataconfig deletion through CLI while a pod with kata runtime is still running should throw the failure error instead of the success message
Summary: Kataconfig deletion through CLI while a pod with kata runtime is still runnin...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: sandboxed-containers
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.9.z
Assignee: Ariel Adam
QA Contact: Cameron Meadors
URL:
Whiteboard:
Depends On: 2060448 2060449
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-30 07:12 UTC by Abhishek Banerjee
Modified: 2022-05-23 11:24 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2060449
Environment:
Last Closed: 2022-05-23 11:24:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker KATA-1465 0 None None None 2022-03-31 21:02:28 UTC

Comment 1 mkenigsb 2022-03-31 20:40:12 UTC 
Since no abnormal MCO behavior has been identified and it seems the problem is likely with the kataconfig, moving to sandboxed-containers
Comment 3 Greg Kurz 2022-05-23 11:24:52 UTC 
Jira KATA-1465 moved to CLOSED/WONTFIX with the following comment :

"... the pods needs to be removed first.
It's documented in the prereq section - https://docs.openshift.com/container-platform/4.10/sandboxed_containers/uninstalling-sandboxed-containers.html#sandboxed-containers-deleting-operator-deployment-cr_uninstalling-sandboxed-containers"

Closing.
Note You need to log in before you can comment on or make changes to this bug.