Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: OP-2.3.0.GA
Affects Version/s: None
Component/s: OpenShift
Labels:
- operator

Blocked:
False
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

OP-2.3.0.GA
Git Pull Request:
http://pkgs.devel.redhat.com/cgit/containers/eap73-rhel-8-operator-bundle/commit/?h=jb-eap-2.3-operator-dev-rhel-8&id=fed6a9cc1cf6acceac2f6d369ae1553aad690803
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Based on https://docs.engineering.redhat.com/display/CFC/Delivery, the supported architectures for operator must be specified in .metadata.labels but the CSV for the EAP Operator specifies them in .spec.labels.

This prevents to properly list the EAP Operator in the OperatorHub on OCP for Z & P

is cloned by

JBEAP-23267 [2.2] Multiarch labels are not specified in the right field.

Closed

is incorporated by

CLOUD-4076 EAP Operator not listed in Operator hub on OCP on series-z

Closed

JBEAP-23103 EAP Operator 2.3 release

Closed

Assignee:: Jeff Mesnil

Reporter:: Jeff Mesnil

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2022/02/16 12:55 PM

Updated:: 2024/08/19 1:56 PM

Resolved:: 2022/03/03 11:58 AM