project-codeflare / project-codeflare/codeflare-sdk
CodeFlare Notebook has FIPS Failure messages
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 35
- Forks
- 66
- Avg merge
- 48m
- Merged PRs (30d)
- 7
Description
Describe the Bug
Running the ./check-payload scan operator --spec quay.io/project-codeflare/notebook:v0.10.1 from https://github.com/openshift/check-payload.git results in FIPS failures:
--- Failure Report
+---------------------+--------------------------+-----------------------------------------------------------------------------------+--------------------------------------------+
| OPERATOR NAME | EXECUTABLE NAME | STATUS | IMAGE |
+---------------------+--------------------------+-----------------------------------------------------------------------------------+--------------------------------------------+
| python-39-container | /opt/app-root/bin/oc | could not find dependent openssl version within container image: libcrypto.so.1.1 | quay.io/project-codeflare/notebook:v0.10.1 |
| python-39-container | /opt/app-root/bin/py-spy | executable is not dynamically linked | quay.io/project-codeflare/notebook:v0.10.1 |
+---------------------+--------------------------+-----------------------------------------------------------------------------------+--------------------------------------------+
F1102 15:07:08.448138 81575 main.go:259] Error: run failed
Similar issues have been opened up for the CodeFlare operator https://github.com/red-hat-data-services/codeflare-operator/issues/4 and KubeRay https://github.com/red-hat-data-services/codeflare-operator/issues/5
Codeflare Stack Component Versions
Please specify the component versions in which you have encountered this bug.
Codeflare SDK: notebook:v0.10.1
MCAD: n/a
Instascale:n/a
Codeflare Operator: codeflare-operator:v1.0.0
Other:
Steps to Reproduce the Bug
with [check-payload](https://github.com/openshift/check-payload.git) built,
./check-payload scan operator --spec quay.io/project-codeflare/notebook:v0.10.1
Expected Behavior
No failure messages on the check-payload scan
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the scan with check-payload using quay.io/project-codeflare/notebook:v0.10.1 and review the reported failures for /opt/app-root/bin/oc and /opt/app-root/bin/py-spy. The work is done when the check-payload operator scan completes without FIPS failure messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100