Skip to content

Conversation

DaveCTurner
Copy link
Contributor

Relates minio/minio#21456
Closes #131742

@DaveCTurner DaveCTurner added >test Issues or PRs that are addressing/adding tests :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs auto-backport Automatically create backport pull requests when merged v9.2.0 v9.1.1 v8.19.1 v9.0.5 v8.18.5 labels Jul 24, 2025
@elasticsearchmachine elasticsearchmachine added the Team:Distributed Coordination Meta label for Distributed Coordination team label Jul 24, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination)

Copy link
Contributor

@DiannaHohensee DiannaHohensee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

// However the 2025-05-24 release is also buggy, see https://github.com/minio/minio/issues/21377, and this has no workaround
public static final String DOCKER_BASE_IMAGE = "minio/minio:RELEASE.2025-06-13T11-33-47Z";
// NB releases earlier than 2025-05-24 are buggy, see https://github.com/minio/minio/issues/21189, and #127166 for a workaround.
// However the 2025-05-24 release is also buggy, see https://github.com/minio/minio/issues/21377, and this has no workaround.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minio/minio#21377 appears to be resolved. Is it mentioned here because it wasn't released in the 2025-07-23 build?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, that should be fixed in 2025-07-23. The specific MinIO version in use has come up in some conversations with customers so I'm keeping track of the known issues in older versions here. We may end up having to run these tests against multiple MinIO versions in which case we'll need this info - clearly we can extract it from history but it's going to be easier if we have a summary here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, sounds good then 👍

// NB releases earlier than 2025-05-24 are buggy, see https://github.com/minio/minio/issues/21189, and #127166 for a workaround
// However the 2025-05-24 release is also buggy, see https://github.com/minio/minio/issues/21377, and this has no workaround
public static final String DOCKER_BASE_IMAGE = "minio/minio:RELEASE.2025-06-13T11-33-47Z";
// NB releases earlier than 2025-05-24 are buggy, see https://github.com/minio/minio/issues/21189, and #127166 for a workaround.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is minio/minio#21189 mentioned because the bug wasn't fixed properly, leading to you filing 21456?

I'm wondering if it's worth mentioning resolved bugs. But if it still relates, then that seems helpful, maybe mentioned in that way.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure, I suspect minio/minio#21456 might be something different albeit with similar symptoms.

.setting("xpack.security.enabled", "false")
// Skip listing of pre-existing uploads during a CAS because MinIO sometimes leaks them; also reduce the delay before proceeding
// TODO do not set these if running a MinIO version in which https://github.com/minio/minio/issues/21189
// and https://github.com/minio/minio/issues/21456 are both fixed
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does minio/minio#21189 need to be mentioned, since it is closed already?

Also, should the testing change made in https://github.com/elastic/elasticsearch/pull/127166/files be returned, since the fix did not take? IIUC that minio/minio#21189 didn't actually fix the bug, leading to you filing minio/minio#21456?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the testing change from #127166, it's just that we're applying it to the correct test suite here 🤦

Copy link
Contributor

@DiannaHohensee DiannaHohensee Jul 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah 😄 Then we're good to go 🙃

@DaveCTurner DaveCTurner added the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Jul 30, 2025
@elasticsearchmachine elasticsearchmachine merged commit c04e6e5 into elastic:main Jul 30, 2025
33 checks passed
@DaveCTurner DaveCTurner deleted the 2025/07/24/minio-21456-workaround branch July 30, 2025 11:48
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Jul 30, 2025
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Jul 30, 2025
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
9.1
8.19
9.0 Commit could not be cherrypicked due to conflicts
8.18 Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 131815

DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Jul 30, 2025
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Jul 30, 2025
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Jul 30, 2025
elasticsearchmachine pushed a commit that referenced this pull request Jul 30, 2025
elasticsearchmachine pushed a commit that referenced this pull request Jul 30, 2025
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Sep 8, 2025
DaveCTurner added a commit that referenced this pull request Sep 9, 2025
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Sep 9, 2025
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Sep 9, 2025
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Sep 9, 2025
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Sep 9, 2025
elasticsearchmachine pushed a commit that referenced this pull request Sep 9, 2025
elasticsearchmachine pushed a commit that referenced this pull request Sep 9, 2025
elasticsearchmachine pushed a commit that referenced this pull request Sep 9, 2025
elasticsearchmachine pushed a commit that referenced this pull request Sep 9, 2025
rjernst pushed a commit to rjernst/elasticsearch that referenced this pull request Sep 9, 2025
Kubik42 pushed a commit to Kubik42/elasticsearch that referenced this pull request Sep 9, 2025
sarog pushed a commit to portsbuild/elasticsearch that referenced this pull request Sep 11, 2025
sarog pushed a commit to portsbuild/elasticsearch that referenced this pull request Sep 11, 2025
sarog pushed a commit to portsbuild/elasticsearch that referenced this pull request Sep 19, 2025
sarog pushed a commit to portsbuild/elasticsearch that referenced this pull request Sep 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs Team:Distributed Coordination Meta label for Distributed Coordination team >test Issues or PRs that are addressing/adding tests v8.18.5 v8.19.1 v9.0.5 v9.1.1 v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CI] MinioRepositoryAnalysisRestIT testRepositoryAnalysis failing

3 participants