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

Update minio container #772

Open
7 of 21 tasks
ferschubert-hm opened this issue Jan 6, 2025 · 1 comment
Open
7 of 21 tasks

Update minio container #772

ferschubert-hm opened this issue Jan 6, 2025 · 1 comment
Labels
should have Should be done, medium priority for now

Comments

@ferschubert-hm
Copy link
Contributor

ferschubert-hm commented Jan 6, 2025

Description

We are currently using a 2021 release. but latest available is RELEASE.2024-12-18T13-15-44Z.

From a security perspective we are several critical security fixes behind. Latest sec fix is https://github.com/minio/minio/releases/tag/RELEASE.2024-12-13T22-19-12Z

A quick attempt to upgrade to the latest caused errors:

FATAL Unable to use the drive /data: drive not found: Invalid arguments specified 

Probably due to https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html

Acceptance Criteria

  • Upgrade minio and fix all errors to use the recent RELEASE.2024-12-18T13-15-44Z version
  • Test locally on a new installation: open and login to MinIO web UI, CRUD operations from Altis on images stored on the persistent volume, check persistency between container cycle.
  • Test locally on an existing installation: open and login to MinIO web UI, CRUD operations from Altis on images stored on the persistent volume, check persistency between container cycle. Check if existing data is kept/can be migrated

For Altis Team Use

Ready for Work Checklist

Is this ticket ready to be worked on? See
the Play Book Definition of Ready

  • Is the title clear?
  • Is the description clear and detailed enough?
  • Are acceptance criteria listed?
  • Have any dependencies been identified? (Optional)
  • Have any documentation/playbook changes been identified? (Optional)
  • Is an estimate or time box assigned?
  • Is a priority label assigned?
  • Is this ticket added to a milestone?
  • Is this ticket added to an epic? (Optional)

Completion Checklist

Is this ticket done? See
the Play Book Definition of Done

  • Has the acceptance criteria been met?
  • Is the documentation updated (including README)?
  • Do any code/documentation changes meet project standards?
  • Are automatic tests in place to verify the fix or new functionality?
    • Or are manual tests documented (at least on this ticket)?
  • Are any Playbook/Handbook pages updated?
  • Has a new module release (patch/minor) been created/scheduled?
  • Have the appropriate backport labels been added to the PR?
  • Is there a roll-out (and roll-back) plan if required?
@ferschubert-hm
Copy link
Contributor Author

Hey team! Please add your planning poker estimate with Zenhub @jerico @mikelittle @wisyhambolu

@ferschubert-hm ferschubert-hm added the should have Should be done, medium priority for now label Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
should have Should be done, medium priority for now
Projects
None yet
Development

No branches or pull requests

1 participant