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

[BUG] Sequential auto-migration for cluster not working #588

Open
cpinjani opened this issue Jul 2, 2024 · 5 comments
Open

[BUG] Sequential auto-migration for cluster not working #588

cpinjani opened this issue Jul 2, 2024 · 5 comments
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@cpinjani
Copy link

cpinjani commented Jul 2, 2024

What steps did you take and what happened?

Description:
Sequential v3 auto-migration not working

What steps did you take and what happened?

  • Install turtles v0.8.0 (v3 option disabled) and import CAPI cluster
    image

  • Upgrade turtles to latest v0.9.0 by keeping settings to default (v3 is auto-enabled to true)
    image

  • Update turtles settings and set managementv3-cluster-migration to true and let the operation complete.
    The migrated v3 cluster is Unavailable in Rancher.
    image

What did you expect to happen?

Sequential migration ie. managementv3-cluster = true, managementv3-cluster-migration = false -> managementv3-cluster = true, managementv3-cluster-migration = true should work.

How to reproduce it?

Steps mentioned above.

Rancher Turtles version

v0.9.0

Anything else you would like to add?

While upgrade from v0.8.0 if both managementv3-cluster, managementv3-cluster-migration = true, then migration completes successfully.
image

Label(s) to be applied

/kind bug

@cpinjani
Copy link
Author

cpinjani commented Jul 2, 2024

logs.tar.gz

@cpinjani cpinjani added the kind/bug Something isn't working label Jul 2, 2024
@cpinjani cpinjani added this to the July release milestone Jul 2, 2024
@Danil-Grigorev
Copy link
Contributor

Should be caused by #587

@furkatgofurov7
Copy link
Contributor

Should be caused by #587

Exactly, yes. We have noticed it while testing it with @salasberryfin

@furkatgofurov7
Copy link
Contributor

@cpinjani #587 was fixed which we think was causing the issues you were reporting here. Would you be able to verify if that fixes the issue for you?

@Danil-Grigorev
Copy link
Contributor

@cpinjani I moved this issue into “To Test”. Can you please validate, so we can close it?

@cpinjani cpinjani self-assigned this Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Development

No branches or pull requests

3 participants