-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhoai-3.3
-
None
-
None
-
False
-
-
False
-
-
Problem
The AIPCC-packaged version of kfp 2.15.2 in the RHOAI 3.3 index does not properly declare docstring-parser as a dependency, causing runtime failures when using Elyra's KFP pipeline processor.
Evidence
Upstream kfp 2.15.2 declares docstring-parser as required:
From PyPI kfp 2.15.2 metadata:
"requires_dist": [ "click>=8.1.8", "click-option-group==0.5.7", "docstring-parser[1,]=0.7.3", <-- THIS IS MISSING IN AIPCC "google-api-core...", ... ]
AIPCC index has docstring-parser available:
$ python scripts/list_aipcc_packages.py --package docstring-parser h1. Index: CPU (https://console.redhat.com/api/pypi/public-rhai/rhoai/3.3/cpu-ubi9/simple/) docstring-parser: 0.17.0
The package exists in the index but is not being pulled in by dependency resolution.
Resulting error at runtime:
[E 2026-01-30 16:19:27.584 ElyraApp] Error registering kfp processor "elyra.pipeline.kfp.processor_kfp.KfpPipelineProcessor" - No module named 'docstring_parser'
CI failure:
See GitHub Actions run for PR #2879.
Root Cause
The AIPCC-repackaged kfp-2.15.2 wheel likely has modified or missing dependency metadata that does not include docstring-parser in its METADATA or requires.txt file.
Impact
- Elyra KFP pipeline processor fails to load
- Users cannot create Kubeflow pipelines from JupyterLab
- Affects all workbenches using AIPCC 3.3 index
Workaround
Explicitly add docstring-parser to the pyproject.toml dependencies:
dependencies = [
...
"docstring-parser~=0.17.0", # Workaround for AIPCC kfp missing dependency
...
]
Request
Please update the kfp package in AIPCC 3.3 index to properly declare docstring-parser as a required dependency, matching the upstream PyPI package metadata.
- is related to
-
AIPCC-9539 builder: click-option-group package request
-
- New
-
- links to