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

Wrong cluster ID on VM history after cluster reorganization #2226

Open
7 tasks
AdriMenendezM opened this issue Jun 27, 2018 · 2 comments · May be fixed by OpenNebula/docs#3139
Open
7 tasks

Wrong cluster ID on VM history after cluster reorganization #2226

AdriMenendezM opened this issue Jun 27, 2018 · 2 comments · May be fixed by OpenNebula/docs#3139
Assignees
@paczerny
Labels
Category: Core & System Community Priority: Normal Status: Accepted Type: Bug
Milestone
Release 6.10.3

Comments

@AdriMenendezM
Copy link

Enhancement Request

Description

VMs deployed on a host which has been moved to another cluster, maintain the previous cluster ID on the last history record. Actions like attach nic to a network which is not part of the old cluster fail.
It would be very useful to add a new histroy record to log the new cluster ID.

To reproduce:
Two clusters with one host and some vnets and VMs on each one.
Reorganize hosts moving one of them to the other cluster.
Try to attach nic to a VM on a vnet of the new cluster.

Use case

You need to manually update the last history record of each VM of the moved host.

Interface Changes

N/A

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches
@juanmont juanmont added this to the Release 5.8 milestone Sep 10, 2018
@rsmontero rsmontero modified the milestones: Release 5.8, Release 5.10 Jan 3, 2019
@rsmontero rsmontero modified the milestones: Release 5.10, Release 5.12 Sep 4, 2019
@paczerny
Copy link
Member

paczerny commented Feb 6, 2024

In case somebody runs into this issue, here is command how to fix the cluster ID in the VM history record:

onedb change-history --id <vm-id> --seq <history-last-id> '/HISTORY/CID' <new-cluster-id>

@tinova tinova added this to the Release 7.0 milestone Feb 12, 2024
@paczerny paczerny self-assigned this Jan 7, 2025
@paczerny
Copy link
Member

paczerny commented Jan 7, 2025

For master branch solved by #6342
Need fix for 6.10 branch

@paczerny paczerny modified the milestones: Release 7.0, Release 6.10.3 Jan 9, 2025
paczerny added a commit to OpenNebula/docs that referenced this issue Jan 9, 2025
@paczerny
B OpenNebula/one#2226: Update resolved issues (cluster id)
9c56c2a
@paczerny paczerny linked a pull request Jan 9, 2025 that will close this issue
B OpenNebula/one#2226: Update resolved issues (cluster id) OpenNebula/docs#3139
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@paczerny paczerny

Labels
Category: Core & System Community Priority: Normal Status: Accepted Type: Bug
Projects
None yet
Milestone
Release 6.10.3
Development

Successfully merging a pull request may close this issue.

B OpenNebula/one#2226: Update resolved issues (cluster id) OpenNebula/docs
5 participants
@tinova @rsmontero @juanmont @AdriMenendezM @paczerny