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

delta backup failed after last update - no alias references VHD #7771

Open
TristisOris opened this issue Jun 22, 2024 · 6 comments
Open

delta backup failed after last update - no alias references VHD #7771

TristisOris opened this issue Jun 22, 2024 · 6 comments

Comments

@TristisOris
Copy link

TristisOris commented Jun 22, 2024

Are you using XOA or XO from the sources?

XO from the sources

Which release channel?

None

Provide your commit number

222ec

Describe the bug

some job just never complited Error: the job (8b3f311e-90dd-495d-8626-819df32958f6) is already running

updated to #7763, that fix only CR backup.

Error message

delta ndb https://pastebin.com/qW7S0jaK

To reproduce

  1. Go to '...'
  2. Click on '...'
  3. Scroll down to '...'
  4. See error

Expected behavior

No response

Screenshots

No response

Node

20

Hypervisor

8.2.1

Additional context

No response

@TristisOris TristisOris changed the title backup failed after last update - no alias references VHD delta backup failed after last update - no alias references VHD Jun 22, 2024
@TristisOris
Copy link
Author

2 days later almost all backups fixed without reason. 1 still failed with Error: VDI must be free or attached to exactly one VM.

@TristisOris
Copy link
Author

it works for a day and failed again.
some jobs running with cbt, some not. I don't enabled CBT anywhere, but it enabled on some VM i dunno why.

image

@TristisOris
Copy link
Author

after 6ee7a27 CBT references removed from backup window.

NBD backups looks working now. One job finally succeed.

Toolstack restart fixed stuck backup tasks.

@julien-f
Copy link
Member

Thanks for all your feedbacks, next week will be dedicated to fix all the remaining issues in CBT before merging it again.

@TristisOris
Copy link
Author

also API call: sr.getAllUnhealthyVdiChainsLength not dissapear from XO tasks.

@julien-f
Copy link
Member

also API call: sr.getAllUnhealthyVdiChainsLength not dissapear from XO tasks.

Yes, this is completely unrelated, it's an old issue that has been revealed by the new logging system for API calls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants