Skip to content

fix: update pinned dependency versions for RHOAI 3.4 compatibility#134

Open
adamrdrew wants to merge 1 commit intorh-aiservices-bu:mainfrom
adamrdrew:fix/update-deps-rhoai-3.4
Open

fix: update pinned dependency versions for RHOAI 3.4 compatibility#134
adamrdrew wants to merge 1 commit intorh-aiservices-bu:mainfrom
adamrdrew:fix/update-deps-rhoai-3.4

Conversation

@adamrdrew
Copy link
Copy Markdown
Contributor

The RHOAI 3.4 pypi index no longer carries onnx 1.17.0, onnxruntime 1.19.2, protobuf 5.28.3, boto3 1.35.55, or botocore 1.35.55. Update pins to versions available in the RHOAI 3.4 index. tf2onnx is not in the RHOAI index at all, so install it from PyPI via --extra-index-url.

Tested on a RHOAI 3.4 TensorFlow workbench image — all imports succeed.

1_experiment_train.ipynb:

  • onnx 1.17.0 → 1.20.0
  • onnxruntime 1.19.2 → 1.24.4
  • tf2onnx 1.16.1 → 1.17.0 (via --extra-index-url https://pypi.org/simple/)
  • Remove protobuf==5.28.3 pin (6.31.1 ships in the image and is compatible)

2_save_model.ipynb:

  • boto3 1.35.55 → 1.42.84
  • botocore 1.35.55 → 1.42.84

The RHOAI 3.4 pypi index no longer carries onnx 1.17.0, onnxruntime
1.19.2, protobuf 5.28.3, boto3 1.35.55, or botocore 1.35.55. tf2onnx
is not in the RHOAI index at all. Since the RHOAI workbench images use
index-url (not extra-index-url), packages not in the index cannot be
installed.

1_experiment_train.ipynb:
  - onnx 1.17.0 → 1.20.0
  - onnxruntime 1.19.2 → 1.24.4
  - Replace tf2onnx conversion with manual ONNX graph construction
    using onnx.helper (available in the index). This produces an
    identical model — verified on a RHOAI 3.4 TensorFlow workbench.
  - Remove protobuf==5.28.3 pin (6.31.1 ships in the image)

2_save_model.ipynb:
  - boto3 1.35.55 → 1.42.84
  - botocore 1.35.55 → 1.42.84

Tested: all imports and ONNX conversion verified on RHOAI 3.4
TensorFlow notebook image (keras 3.14, tensorflow 2.21.0+redhat).
ONNX model passes onnx.checker and produces identical predictions
to the Keras model via onnxruntime inference.
@erwangranger erwangranger requested a review from RHRolun April 15, 2026 14:24
@erwangranger
Copy link
Copy Markdown
Collaborator

Thanks.
I'm guessing that for 3.4, we will also need to update the name/version of the workbench image being used. This is what is what the user currently sees for 3.3:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants