Skip to content

Upgrade of S3 service doesn't work without 'mc admin update' command #70

Description

@bartversluijs

Hi,

I was trying to update the S3 service from v2.9.9 to v2.10.3, but I got some JSON-RPC errors.
After some investigation, I had to run the command following command inside the container:

$ mc admin update localhost

Everything works fine after that!

But for an automated update process, should the service execute this command or should it be a manual step when you're upgrading the service?

Thanks in advance!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions