Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2087060

Summary:	Make "Create knmstate instance" a part of the operator installation process (UI)
Product:	OpenShift Container Platform	Reporter:	Aleksandra Malykhin <amalykhi>
Component:	Networking	Assignee:	Petr Horáček <phoracek>
Networking sub component:	kubernetes-nmstate-operator	QA Contact:	Aleksandra Malykhin <amalykhi>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	low
Priority:	medium	CC:	bnemec, cstabler, mocohen
Version:	4.10
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:	2086301	Environment:
Last Closed:	2022-11-09 21:57:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2087063

Description Aleksandra Malykhin 2022-05-17 08:39:19 UTC

[Improvement]

Steps to Reproduce:
1. Follow the instructions to install KNMState (tried with both GUI and CLI install)
2. Click the button "create instance" in the operator page


Actual results:
When installation is completed, the user needs to go to the operator page and create the nmstate instance (it is not needed, additional step)


Expected results:
The instance should be created during installation proccess (and ask for permission for it)

Comment 1 Ben Nemec 2022-05-17 16:32:35 UTC

*** Bug 2087063 has been marked as a duplicate of this bug. ***

Comment 2 Ben Nemec 2022-05-17 16:37:57 UTC

This is not a bug, it's an RFE. I'm also not sure how much benefit there is to it. We can provide a resource to be created automatically at installation time, but all it does is add a new field with a button to create the resource. We already have that on the operator page that users are redirected to after the operator is installed. As far as I'm aware, the Operator Hub doesn't provide a way to have the resource just created as part of the install.

I will also note that we had this enabled at one point and it broke the operator completely. We'd need to figure out how to test it before merging anything like this again.

My suggestion would be to close this and open a Jira ticket so it can be planned appropriately.

Comment 4 Ben Nemec 2022-11-09 21:57:44 UTC

Per my previous comment, I've converted this to a Jira story: https://issues.redhat.com/browse/OPNET-167