Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    5k Posts
    M
    @rzr Installed those security update candidates in my XCP-ng test environment. So far no issues whatsoever. Basic operations all work. VMs running etc.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    nathanael-hN
    @pszelestey Hi, yes, we've pushed an initial commit and a few more here https://github.com/vatesfr/cluster-api-provider-vates/ it is moging every day. Ping us in Matrix/Discord devops if you want to chat live while trying
  • 3k Topics
    28k Posts
    E
    Had some time today, so went to update my home XCP-ng with the latest updates, on both the base and XOA. After rebooting I wasn't able to connect to the XOA appliance UI. ssh'ing into XOA and poking around, I find this in the logs: Jun 09 18:57:31 xoa systemd[1]: Started xo-server.service - XO Server. Jun 09 18:57:31 xoa (o-server)[557]: xo-server.service: Failed to locate executable /usr/local/bin/xo-server: No such file or directory I've looked through the update notes and don't see anything related. Did I miss something, or did my updates screw up somehow. How do I recover this. I did find one write up on deleting the XOA appliance and reinstalling, but the delete fails with: [17:15 xcp-ng ~]# xe vm-destroy uuid="3d80a504-3460-96ab-d438-2e6f2e9e0487" You attempted an operation that was explicitly blocked (see the blocked_operations field of the given object). ref: 3d80a504-3460-96ab-d438-2e6f2e9e0487 (XOA) code: true [17:15 xcp-ng ~]# ***** Update ***** Was able to delete and re-create the XOA appliance. So now I'd just like to understand what happened. Cheers.
  • Our hyperconverged storage solution

    47 Topics
    752 Posts
    olivierlambertO
    Yes, there's a weird issue when using both XOSTOR and HA, probably due to the HA mechanism itself. @Team-Storage is on it
  • 35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !