Commit 5870395
authored
fix(ci): run gen_lockfile.py in container for OpenSSL compat (#518)
## Summary
- Run `gen_lockfile.py` inside a UBI9 container via
`run_gen_lockfile.sh` in the `regenerate-artifacts` action, matching the
approach already used by the `update-lockfiles` workflow (#510)
The nightly schedule builds (`redhat-distro-container.yml`) have been
failing since late June at the "Regenerate distribution artifacts" step
with:
```
ImportError: libcrypto.so.3: version `OPENSSL_3.2.0' not found
(required by cryptography/hazmat/bindings/_rust.abi3.so)
```
The RHAI Python index provides a `cryptography` package built against
OpenSSL 3.2+, but GitHub Actions runners (Ubuntu 24.04) ship OpenSSL
3.0.x. PR #510 fixed this same issue for the `update-lockfiles` workflow
by running `gen_lockfile.py` inside the `odh-midstream-python-base-3-12`
container (which has OpenSSL 3.5), but the `regenerate-artifacts` action
was not updated.
This is one of the root causes behind RHOAIENG-70548 (OGX build failures
blocking downstream Konflux snapshots and Crimson E2E tests).
## Verification
Tested via `workflow_dispatch` on a fork
([run](https://github.com/EleanorWho/ogx-distribution/actions/runs/29821075660)):
the OpenSSL error is resolved and the midstream lockfile
(`requirements-lock.txt`) generates successfully. The downstream
lockfile (`requirements-lock-konflux.txt`) fails due to a separate issue
— `opentelemetry-instrumentation-structlog==0.65b0` is missing from the
RHAI index — which is unrelated to this change.
## Test plan
- [x] `workflow_dispatch` on fork confirms OpenSSL error is fixed
- [ ] Midstream lockfile generates successfully (verified in fork run)
- [ ] Nightly schedule build passes the "Regenerate distribution
artifacts" step after merge1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
24 | 24 | | |
25 | 25 | | |
26 | 26 | | |
27 | | - | |
| 27 | + | |
28 | 28 | | |
0 commit comments