Getting errors when migrating 4 out 5 VMGuest

Danp

You need to run yarn followed by yarn build. FYI, you can combine them into a single command like this --

yarn; yarn build

ashinobi

Here is what I got after running yarn:

admin@xen-orchestra:/opt/xo/xo-src/xen-orchestra$ sudo yarn;yarn build
[sudo] password for admin:
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning "@commitlint/cli > @commitlint/load > cosmiconfig-typescript-loader@5.0.0" has unmet peer dependency "@types/node@*".
warning "@commitlint/cli > @commitlint/load > cosmiconfig-typescript-loader@5.0.0" has unmet peer dependency "typescript@>=4".
warning "@vue/eslint-config-typescript > @typescript-eslint/eslint-plugin > ts-api-utils@1.0.3" has unmet peer dependency "typescript@>=4.2.0".
warning "workspace-aggregator-04a3b3bf-f2de-4fa4-8c4d-af65746d82b1 > @vates/node-vsphere-soap > soap@1.0.0" has incorrect peer dependency "axios@^0.27.2".
warning "workspace-aggregator-04a3b3bf-f2de-4fa4-8c4d-af65746d82b1 > @vates/event-listeners-manager > tap > @tapjs/test > @isaacs/ts-node-temp-fork-for-pr-2009@10.9.5" has unmet peer dependency "@types/node@*".
warning "workspace-aggregator-04a3b3bf-f2de-4fa4-8c4d-af65746d82b1 > @vates/event-listeners-manager > tap > @tapjs/asserts > tcompare > react-element-to-jsx-string@15.0.0" has unmet peer dependency "react@^0.14.8 || ^15.0.1 || ^16.0.0 || ^17.0.1 || ^18.0.0".
warning "workspace-aggregator-04a3b3bf-f2de-4fa4-8c4d-af65746d82b1 > @vates/event-listeners-manager > tap > @tapjs/asserts > tcompare > react-element-to-jsx-string@15.0.0" has unmet peer dependency "react-dom@^0.14.8 || ^15.0.1 || ^16.0.0 || ^17.0.1 || ^18.0.0".
warning Workspaces can only be enabled in private projects.
[5/5] Building fresh packages...
$ husky install
husky - Git hooks installed
Done in 185.69s.
yarn run v1.22.19
$ turbo run build --scope xo-server --scope xo-server-'*' --scope xo-web
 ERROR  run failed: IO error: failed to create directory `/opt/xo/xo-src/xen-orchestra/node_modules/.cache/turbo`
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Danp

Try it like this --

sudo bash
yarn; yarn build

ashinobi

@Danp

Thanks. I have successfully run it

root@xen-orchestra:/opt/xo/xo-src/xen-orchestra# yarn; yarn build
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
$ husky install
husky - Git hooks installed
Done in 4.22s.
yarn run v1.22.19
$ turbo run build --scope xo-server --scope xo-server-'*' --scope xo-web
• Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-backup-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test, xo-server-test-plugin, xo-server-transport-email, xo-server-transport-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web
• Running build in 22 packages
• Remote caching disabled
 WARNING  Failed to check if we can skip restoring outputs for xo-lib#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-auth-saml#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-transport-xmpp#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-remote-parser#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-auth-github#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-auth-google#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-transport-slack#build: GrpcFailure(Cancelled). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-transport-icinga2#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-server-transport-email#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for xo-collection#build: GrpcFailure(DeadlineExceeded). Proceeding to check cache

 Tasks:    25 successful, 25 total
Cached:    0 cached, 25 total
  Time:    4m46.846s

Done in 287.74s.

perform the migration test but I am still having the same error message.

olivierlambert

Have you restarted XO server after?

ashinobi

@olivierlambert

No, but I am rebooting it now. I'll update you once the server is up and tested the migration.

olivierlambert

If you don't restart xo-server after a rebuild, you won't be using the latest version you just did rebuild Let us know!

ashinobi

@olivierlambert

Hi, apologies for the late reply, I did restart XO and still have the same problem. Also just to make sure I have restarted both XCP-NG host as well and perform the migrate and still has the same problem.

[05:27 home-hypervisor ~]# uptime
 05:51:29 up 27 min,  1 user,  load average: 0.41, 0.37, 0.20
[05:51 home-hypervisor ~]# hostname
home-hypervisor


[05:44 xcp-ng-Server2 ~]# uptime
 05:51:25 up 15 min,  1 user,  load average: 0.90, 0.64, 0.35
[05:51 xcp-ng-Server2 ~]# hostname
xcp-ng-Server2

rrivera_admin@xen-orchestra:~$ uptime
 05:51:20 up 6 min,  1 user,  load average: 0.13, 0.19, 0.11
rrivera_admin@xen-orchestra:~$ hostname
xen-orchestra

Danp

@ashinobi You previously indicated that the migration worked from the VM screen. Is that still accurate?

Can you post a screenshot of your XO About screen so that we can confirm the commit in use?

ashinobi

@Danp

In regards to migration to vm screen, I confirm that is still working.

In regards to the screenshot of the about page:

I saw this morning there were 12 commits so I just updated to it as well.

Danp

@ashinobi That shows that you are on the master branch. You can confirm that by checking the output of git rev-parse --abbrev-ref HEAD (needs to be run from the correct directory ).

Did you forget to check out the alternate branch before you issued the Yarn commands?

ashinobi

@Danp

Here is what I got from running "rev-parse --abbrev-ref HEAD"

admin@xen-orchestra:/opt/xo/xo-src/xen-orchestra$ sudo git rev-parse --abbrev-ref HEAD
[sudo] password for admin:
xo5/fix-bulk-migration

It shows that I am using the alternate branch which is the "fix-bulk-migration"

Danp

@ashinobi Are you sure that XO is running from that directory? The commit shown above isn't included in xo5/fix-bulk-migration.

ashinobi

@Danp

As you know that I am using XenOrchestraInstallerUpdater script so I will be dependent on its config file. Base on the config file the installation is located at /opt/xo

# Base dir for installation and future updates
INSTALLDIR="/opt/xo"

so I assume that is the directory where XO is running and if I go to /opt directory there is only one folder in there which is "xo"

admin@xen-orchestra:/opt$ ls -ltrh
total 4.0K
drwxr-xr-x 4 root root 4.0K Feb  9 06:25 xo

If I check the status of "xo-server.service" it is pointing to the "/opt/xo" where it is running

admin@xen-orchestra:/opt$ systemctl status xo-server.service
● xo-server.service - XO Server
     Loaded: loaded (/etc/systemd/system/xo-server.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2024-02-09 06:25:48 ACDT; 4h 51min ago
   Main PID: 4769 (node)
      Tasks: 11 (limit: 9359)
     Memory: 163.9M
        CPU: 7min 13.551s
     CGroup: /system.slice/xo-server.service
             └─4769 node /opt/xo/xo-server/dist/cli.mjs

Feb 09 08:45:48 xen-orchestra xo-server[4769]:   network: 'PrivateNetwork2',
Feb 09 08:45:48 xen-orchestra xo-server[4769]:   host: 'xcp-ng-Server2',
Feb 09 08:45:48 xen-orchestra xo-server[4769]:   pool: ''
Feb 09 08:45:48 xen-orchestra xo-server[4769]: }
Feb 09 08:45:48 xen-orchestra xo-server[4769]: 2024-02-08T22:15:48.527Z xo:xo-server:sdn-controller:private-network INFO Host added {
Feb 09 08:45:48 xen-orchestra xo-server[4769]:   privateNetwork: '0ad66652-81c9-4c67-b484-286a1621c23e',
Feb 09 08:45:48 xen-orchestra xo-server[4769]:   network: 'PrivateNetwork1',
Feb 09 08:45:48 xen-orchestra xo-server[4769]:   host: 'xcp-ng-Server2',
Feb 09 08:45:48 xen-orchestra xo-server[4769]:   pool: ''
Feb 09 08:45:48 xen-orchestra xo-server[4769]: }

Danp

@ashinobi That all looks fine. Probably just need to pull the source with git pull.

Also, I just took at look at that script and it seems that you can edit the BRANCH line in the config file to select a different branch for the script to use.

ashinobi

@Danp

do I change "Branch=MASTER" to "Branch=xo5/fix-bulk-migration"? to make it work?

Danp

@ashinobi I believe so

ashinobi

@Danp

Unfortunately I am still having the same issue. I have rebooted XO and both host as well:

Danp

@ashinobi That commit is still from the wrong branch, so I'm not sure what isn't working correctly on your end.

I just rebuilt my XO VM on that branch using these commands --

sudo bash
cd /opt/xen-orchestra/
git checkout xo5/fix-bulk-migration
git pull
yarn; yarn build
sudo systemctl restart xo-server.service

This is my About screen now, which matches the values I would expect for this branch --

ashinobi

@Danp

That is weird, if that is still from the wrong branch because when I ran the script it showed it is trying to download from the branch I specified:

I will try your method, unfortunately my backups for my VM Guest just kicked in so I'll update you once the backup has finished and I was able to run the command you have provided

Regards