Hi all,
Is it working as designed that Proxmox is no longer directly integrated after an inplace-upgrade from 12.3.2 to version 13.0.1?
My Proxmox workloads can no longer be activated, and I'm also unable to add Proxmox Hosts within the VBR Console.
The VeeamPVESvc service is present and running and the plugin for Proxmox is installed in version 13.3.0.237.
It's my Lab/NFR environment - so no big deal for me - just curious...
Anyone else can confirm this?
The upgrade to 13.0.1 was successful without any issues.
The Plugin was upgraded within the VBR upgrade procedure, from PVE 12.1.3.217 -> 13.3.0.237
A reboot was done after the upgrade.
Case #07892920
-
Dynamic
- Veeam Vanguard
- Posts: 50
- Liked: 16 times
- Joined: Mar 02, 2017 2:43 pm
- Full Name: Markus Hartmann
- Contact:
No PVE Hypervisor workloads after inplace upgrade
Markus Hartmann | Veeam Vanguard | Veeam Legend 2024 | VMCA 2024 & VMCE 2024 | VMware Certified Implementation Expert - Data Center Virtualization 2024 | https://markushartmann.blog/
-
Gostev
- Chief Product Officer
- Posts: 32868
- Liked: 8046 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: No PVE Hypervisor workloads after inplace upgrade
It's not expected, thanks for opening a support case.
-
Regnor
- VeeaMVP
- Posts: 1092
- Liked: 343 times
- Joined: Jan 31, 2011 11:17 am
- Full Name: Max
- Contact:
Re: No PVE Hypervisor workloads after inplace upgrade
Hi Markus,
In addition to the support case take a look at this article. And also try to restart the PVE service after all other services are started.
https://www.veeam.com/kb4687
In addition to the support case take a look at this article. And also try to restart the PVE service after all other services are started.
https://www.veeam.com/kb4687
Who is online
Users browsing this forum: No registered users and 14 guests