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

upgrade: 3.4.0 to 3.6.0, statefulset for graphd needs to be recreated manually for now #402

Open
wey-gu opened this issue Nov 22, 2023 · 0 comments
Labels
affects/none PR/issue: this bug affects none version. severity/none Severity of bug type/bug Type: something is unexpected

Comments

@wey-gu
Copy link
Contributor

wey-gu commented Nov 22, 2023

Describe the bug (required)

It seems we should fix for the upgrade from 3.4.0 to 3.6.0 or highlight extra manual steps in docs?

Your Environments (required)

3.4.0 to 3.6.0

How To Reproduce(required)

Steps to reproduce the behavior:

ref: https://community-chat.nebula-graph.io/t/16075817/hello-nebula-users-i-m-trying-to-update-k8s-nebula-from-3-4-#5c279531-807a-4249-acec-3528086d2f61

Additional context

Róbert Kuzma 11/21/2023, 8:32 PM

We solved it with delete nebula-graphd statefulSet, after recreate graphd pods start without error.

Jeremy Simpson 11/22/2023, 12:59 AM
Ah yeah I completely forgot about this. I too encountered this same issue before. It’s because during the upgrade from 3.4->3.6 the fqdn was changed, but it was not updated in the statefulset (because it’s immutable iirc). So the solution is to delete the SS then it will be re-recreated properly.

@wey-gu wey-gu added the type/bug Type: something is unexpected label Nov 22, 2023
@github-actions github-actions bot added affects/none PR/issue: this bug affects none version. severity/none Severity of bug labels Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects/none PR/issue: this bug affects none version. severity/none Severity of bug type/bug Type: something is unexpected
Projects
None yet
Development

No branches or pull requests

1 participant