Bug 2019381 - creation of multiple kataconfigs is possible but fails silently
Summary: creation of multiple kataconfigs is possible but fails silently
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: sandboxed-containers
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Ariel Adam
QA Contact: Cameron Meadors
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-02 13:03 UTC by Cameron Meadors
Modified: 2022-08-26 14:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-26 14:45:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker KATA-1497 0 None None None 2022-04-14 11:54:08 UTC
Red Hat Issue Tracker KATA-725 0 None None None 2021-11-02 13:03:17 UTC

Description Cameron Meadors 2021-11-02 13:03:17 UTC 
It is possible to create multiple instances of the KataConfig.  The action succeeds but if you did into the new kataconfig instance there is an error.  The error is that another KataConfig CR already exists.  This error needs to show as an error to the user more directly.  So far I don't see any impact from creating the additional instance as it failed for all intents and purposes.
Note You need to log in before you can comment on or make changes to this bug.