Bug 2139776 - operator does not show up in the disconnected env page in the operatorhub
Summary: operator does not show up in the disconnected env page in the operatorhub
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
unspecified
Target Milestone: ---
: ODF 4.12.0
Assignee: Nitin Goyal
QA Contact: Shay Rozen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-03 11:46 UTC by Nitin Goyal
Modified: 2023-08-09 16:46 UTC (History)
8 users (show)

Fixed In Version: 4.12.0-100
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-08 14:06:28 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage lvm-operator pull 285#issuecomment-1301978270 0 None Merged fix: add dissconected env annotation to the CSV 2022-11-03 11:47:59 UTC
Github red-hat-storage lvm-operator pull 286 0 None open Bug 2139776:[release-4.12] fix: add dissconected env annotation to the CSV 2022-11-03 11:57:45 UTC

Description Nitin Goyal 2022-11-03 11:46:24 UTC
Description of problem (please be detailed as possible and provide log
snippests):
operator does not show up in the disconnected env page in the operatorhub

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 4 Shay Rozen 2022-11-29 11:17:33 UTC
Please add steps to verify this BZ

Comment 5 Nitin Goyal 2022-11-29 11:35:05 UTC
This can be verified in the operator hub's UI. When we check the box 'disconnected env' in the operator hub, we should see an LVM operator.


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