Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to upgrade tenant with two pools due to race condition caused by startupProbe in v4.5.2 #1311

Closed
astraldawn opened this issue Oct 11, 2022 · 6 comments
Assignees

Comments

@astraldawn
Copy link

astraldawn commented Oct 11, 2022

Expected Behavior

  1. Update .spec.image in tenant with two pools
  2. StatefulSet for each pool restarts with updated image

Current Behavior

  1. Update .spec.image in tenant with two pools
  2. StatefulSet for each pool stuck with status:
Pod StatefulSet 0 StatefulSet 1
0 Running Running
1 Running Running
2 Running Running
3 Unavailable (Notready) Unavailable (Notready)
  1. Indicative logs for the unavailable pods:
StatefulSet 0-3 StatefulSet 1-3
lookup tenant-ss-1-3... no such host (*net.DNSError) lookup tenant-ss-0-3... no such host (*net.DNSError)

Possible Solution

Downgrade to v4.5.1

We considered modifying tenant spec but this is not possible as startupProbe is hardcoded (https://github.com/minio/operator/pull/1284/files#diff-dd388a34c55183c615d3aed4bb2004c13ad10d64c2163370890a0746b00cd707R365)

Steps to Reproduce (for bugs)

See current behavour

Context

Unable to upgrade tenant with 2 pools. Not sure if this impacts a tenant with > 2 pools.

Regression

Yes, operator v4.5.2, due to #1284

Upgrade operation was run on these operator versions no issues:

  • v4.4.17
  • v4.5.1

Your Environment

  • Version used (minio-operator): v4.5.2
  • Environment name and version (e.g. kubernetes v1.17.2): v1.19.16
@stale
Copy link

stale bot commented Jan 16, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.

@cesnietor
Copy link
Contributor

we'll try to reproduce

@astraldawn
Copy link
Author

Should be fixed by #1315

@stale stale bot removed the stale label Oct 30, 2023
@cesnietor
Copy link
Contributor

@astraldawn were you able to test it with latest operator? thanks for responding.

@astraldawn
Copy link
Author

Tested with v4.5.8

@cniackz
Copy link
Contributor

cniackz commented Dec 1, 2023

Yes, this is a known issue in version v4.5.2 that has been corrected. Thank you for testing, and please continue upgrading the Operator to the latest available version. You can find more information in the documentation here: https://github.com/minio/wiki/wiki/DNSError-in-Operator-version-4.5.2

@cniackz cniackz closed this as completed Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants