Subcategories

• Management

  VMs, hosts, pools, networks and all other usual management tasks.
  493 Topics

  4k Posts

  M

  When trying to disconnect one or multiple SRs from all hosts using the bulk action in Xen Orchestra 5 (XO5), the operation does not seem to execute. The issue occurs when selecting one or more Storage Repositories from the Storage list, choosing "Disconnect from all hosts", and confirming the action by clicking OK. After confirmation, nothing happens. The selected Storage Repositories remain connected to the hosts. However, if I open each Storage Repository individually and perform the Disconnect action from its own page, the operation works as expected. Steps to reproduce Open Xen Orchestra 5. Navigate to the Storage Repositories list. Select one or multiple Storage Repositories. Choose "Disconnect from all hosts" from the available actions. Click OK to confirm the operation. Observe that nothing happens and the Storage Repositories remain connected. Expected behavior The selected Storage Repositories should be disconnected from all hosts after confirming the bulk action. Actual behavior Nothing happens after clicking OK. The Storage Repositories remain connected to the hosts. The only workaround is to open each Storage Repository individually and disconnect it from there. Could you please confirm whether this is a known issue or a bug in the current XO5 interface?
• Advanced features

  ACLs, Self-service, Cloud-init, Load balancing...
  107 Topics

  874 Posts

  P

  @dknight-bg the Feeder post you linked asks for two things: sending audit events to syslog, which is what this PR does, and recording successful logins, which as far as I can tell the PR doesn't touch. If others reading this need either one, a vote on https://feedback.vates.tech/posts/88/audit-log-forward-events-to-remote-syslog-record-successful-logins is the easiest way to show it. The PR is still waiting for a reviewer, as far as I can see.
• Backup

  All XO backup features: full and incremental, replication, mirrors...
  547 Topics

  6k Posts

  Z

  @poddingue Quick update: I disabled “Purge snapshot data when using CBT” in the XO replication job. I still see NBD+CBT displayed in the XO task manager during replication, but after letting the jobs run for a few cycles, last night’s Veeam backups completed without any CBT warnings or fallback to full. I’m going to add a couple more VMs and continue monitoring. We use Veeam as part of our overall backup strategy for regular VM backups, and switching away from it would be a fairly large project. Veeam doesn’t provide the XCP-ng replication we need, so we’re using XO specifically to maintain replicas at our other site which is why we are using both products.
• REST API

  Everything related to Xen Orchestra's REST API
  89 Topics

  656 Posts

  P

  Hi, This was fixed in Latest. But if you need to stay on Stable, you can open a ticket to have a patch.
• Infrastructure as Code

  Terraform, Packer or any tool to do IaC
  54 Topics

  507 Posts

  D

  For anyone else who steps through this, I've also installed the latest xen-guest-agent with the below process. Repeat for each host in the environment, 1 at a time from your Helper VM. ### ssh into your helper ### oc debug node/fedora-cmp-1/2/3 chroot /host cd /var/tmp curl -LO https://gitlab.com/xen-project/xen-guest-agent/-/jobs/6041686376/artifacts/raw/RPMS/x86_64/xen-guest-agent-0.4.0-0.fc37.x86_64.rpm sudo rpm-ostree install /var/tmp/xen-guest-agent-0.4.0-0.fc37.x86_64.rpm mkdir /var/tmp/xga && cd /var/tmp/xga rpm2cpio ../xen-guest-agent-0.4.0-0.fc37.x86_64.rpm | cpio -idmv ### From your helper... DRAIN YOUR WORKERS ### oc adm drain fedora-cmp-1/2/3 --ignore-daemonsets --delete-emptydir-data ### log back into fedora-cmp-1/2/3... ### sudo systemctl reboot ### from helper ### oc adm uncordon fedora-cmp-1/2/3 ### login to fedora-cmp-1/2/3 ### chroot /host sudo systemctl enable --now xen-guest-agent And then from XO this is what your VMs will look like. [image: image.jpeg]