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.

Sign up for GitHub

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

Jump to bottom

Upgrade to v3.5.0 (from v3.4.0) never comples #5562

Closed
porscheme opened this issue May 26, 2023 · 5 comments
Closed

Upgrade to v3.5.0 (from v3.4.0) never comples #5562

porscheme opened this issue May 26, 2023 · 5 comments
Labels
affects/none PR/issue: this bug affects none version. process/fixed Process of bug severity/none Severity of bug type/bug Type: something is unexpected

Comments

@porscheme
Copy link

Describe the bug (required)
Nebula upgrade to v3.5.0 never completes, only metad upgrade to v3.5.0

  • We tried to upgrade Nebula cluster t v3.5.0 from v3.4.0
  • Below are the exact sequence of steps
    -- Upgrade Nebula operator to v1.4.2
    -- upgrade CRDs
    -- Make sure Nebula operator is healthy
    -- Upgrade to Nebula cluster to v3.5.0
  • All the metad nodes upgraded successfully
  • Notice storaged and graphd nodes never upgrade to v3.5.0, even after 24 hrs

@wey-gu can you help us.
@porscheme porscheme added the type/bug Type: something is unexpected label May 26, 2023
@github-actions github-actions bot added affects/none PR/issue: this bug affects none version. severity/none Severity of bug labels May 26, 2023
@wey-gu
Copy link
Contributor

wey-gu commented May 26, 2023

@MegaByte875 what could possibly stop pod from updating?

@wey-gu wey-gu mentioned this issue May 27, 2023
Closed
@porscheme
Copy link
Author

@wey-gu Any update on this?

@wey-gu
Copy link
Contributor

wey-gu commented May 30, 2023 •
edited
Loading

Sorry @porscheme, for the late response, I just checked with @MegaByte875 offline to know that 3.5.0 is not yet supported by the operator now, which will be done later.

vesoft-inc/nebula-operator#201

@porscheme
Copy link
Author

Oh, thanks for reply @wey-gu
Does it mean we should rollback to v3.4.0?

@wey-gu
Copy link
Contributor

wey-gu commented May 30, 2023

Yes, we should roll back to the 3.4.0/3.4.1 image tag before it's supported.

@QingZ11 QingZ11 closed this as completed Aug 2, 2023
@github-actions github-actions bot added the process/fixed Process of bug label Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects/none PR/issue: this bug affects none version. process/fixed Process of bug severity/none Severity of bug type/bug Type: something is unexpected
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wey-gu @porscheme @QingZ11