rc/SIENTIAPDE-2167- fix: corrige imagem MinIO indisponível e cobre metadata_id nos testes e2e
This commit is contained in:
@@ -48,8 +48,22 @@ def postgres_container():
|
|||||||
|
|
||||||
@pytest_asyncio.fixture(scope='session')
|
@pytest_asyncio.fixture(scope='session')
|
||||||
def minio_container():
|
def minio_container():
|
||||||
"""MinIO testcontainer used by E2E offload and payload retrieval paths."""
|
"""
|
||||||
minio = MinioContainer()
|
MinIO testcontainer used by E2E offload and payload retrieval paths.
|
||||||
|
|
||||||
|
`MinioContainer`'s default image (`minio/minio:RELEASE.2022-12-02T19-19-22Z`) no longer
|
||||||
|
pulls — Docker Hub removed the `minio/minio` repository entirely after MinIO's licensing
|
||||||
|
change. Production (`sientia-helm-chart`) already moved to Bitnami's post-Broadcom-migration
|
||||||
|
"legacy" namespace; mirroring that image here. Two more adjustments on top of just the image:
|
||||||
|
the image runs as non-root by default and can't write to the container's anonymous volume
|
||||||
|
without `user='root'`; and Bitnami deprecated `MINIO_ACCESS_KEY`/`MINIO_SECRET_KEY` (what
|
||||||
|
`MinioContainer` sets) in favor of `MINIO_ROOT_USER`/`MINIO_ROOT_PASSWORD` — reusing the same
|
||||||
|
values so `get_client()` still works unmodified.
|
||||||
|
"""
|
||||||
|
minio = MinioContainer(image='docker.io/bitnamilegacy/minio:2025.7.23-debian-12-r3')
|
||||||
|
minio.with_env('MINIO_ROOT_USER', minio.access_key)
|
||||||
|
minio.with_env('MINIO_ROOT_PASSWORD', minio.secret_key)
|
||||||
|
minio.with_kwargs(user='root')
|
||||||
minio.start()
|
minio.start()
|
||||||
yield minio
|
yield minio
|
||||||
minio.stop()
|
minio.stop()
|
||||||
|
|||||||
@@ -275,7 +275,7 @@ async def test_scenario_2_2_1_transform_gate_triggers_continue(
|
|||||||
postgres_engine=postgres_engine,
|
postgres_engine=postgres_engine,
|
||||||
model_id=model_id,
|
model_id=model_id,
|
||||||
prediction_confidence=Decimal(10),
|
prediction_confidence=Decimal(10),
|
||||||
comments='Unknown MLFlow API error',
|
comments='Bad data model',
|
||||||
)
|
)
|
||||||
|
|
||||||
|
|
||||||
@@ -403,7 +403,7 @@ async def test_scenario_2_3_1_predict_gate_triggers_continue(
|
|||||||
postgres_engine=postgres_engine,
|
postgres_engine=postgres_engine,
|
||||||
model_id=model_id,
|
model_id=model_id,
|
||||||
prediction_confidence=Decimal(10),
|
prediction_confidence=Decimal(10),
|
||||||
comments='Unknown MLFlow API error',
|
comments='Bad predict model',
|
||||||
)
|
)
|
||||||
|
|
||||||
|
|
||||||
@@ -521,7 +521,7 @@ async def test_scenario_2_4_1_priority_conflict_resolution(
|
|||||||
postgres_engine=postgres_engine,
|
postgres_engine=postgres_engine,
|
||||||
model_id=model_id,
|
model_id=model_id,
|
||||||
prediction_confidence=Decimal(10),
|
prediction_confidence=Decimal(10),
|
||||||
comments='Unknown MLFlow API error',
|
comments='Bad data model',
|
||||||
)
|
)
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user