Bug 2149236 - allow installation of the operator in any namespace
Summary: allow installation of the operator in any namespace
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: lvm-operator
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.13.0
Assignee: Nitin Goyal
QA Contact: Shay Rozen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-29 10:05 UTC by Nitin Goyal
Modified: 2023-08-09 16:46 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-13 16:36:00 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage lvm-operator pull 296 0 None Merged allow installation of the operator in any namespace 2022-12-13 12:28:34 UTC
Github red-hat-storage lvm-operator pull 298 0 None open Bug 2149236:[release-4.12] allow installation of the operator in any namespace 2022-12-13 12:28:34 UTC

Description Nitin Goyal 2022-11-29 10:05:36 UTC
Description of problem (please be detailed as possible and provide log
snippets):
Currently, lvmo is only installable in the openshift-storage namespace. Allow installation in any namespace using the OLM.

Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 6 Mudit Agarwal 2022-12-23 03:37:35 UTC
Late in the cycle.


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