-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
[Storage] Build manila-operator correctly for OCP with FIPS enabled
-
False
-
-
False
-
OSPRH-787FIPS Support in OSO 18.0
-
Committed
-
No Docs Impact
-
To Do
-
OSPRH-787 - FIPS Support in OSO 18.0
-
manila-operator-bundle-container-1.0.0-44
-
Committed
-
Committed
-
0% To Do, 0% In Progress, 100% Done
-
Release Note Not Required
-
Regression Only
-
-
-
Approved
According to scan with check-payload tool manila-operator is not build properly for OCP with FIPS enabled. Scan results:
- upstream image
+---------------------------+-----------------+------------------------------+-------------------------------------------------+ | OPERATOR NAME | EXECUTABLE NAME | STATUS | IMAGE | +---------------------------+-----------------+------------------------------+-------------------------------------------------+ | | | openssl library not present | quay.io/openstack-k8s-operators/manila-operator | | manila-operator-container | /manager | go binary is not CGO_ENABLED | quay.io/openstack-k8s-operators/manila-operator | +---------------------------+-----------------+------------------------------+-------------------------------------------------+
- downstream image
+---------------------------+-----------------+------------------------------+--------------------------------------------------------------------+ | OPERATOR NAME | EXECUTABLE NAME | STATUS | IMAGE | +---------------------------+-----------------+------------------------------+--------------------------------------------------------------------+ | manila-operator-container | /manager | go binary is not CGO_ENABLED | registry.redhat.io/rhosp-dev-preview/manila-rhel9-operator:0.1.2-7 | +---------------------------+-----------------+------------------------------+--------------------------------------------------------------------+
- is depended on by
-
OSPRH-1035 Implement FIPS compliance in Manila
- Closed