If zone is not set, we also check the pending changes for a zone key,
since it is set as pending when the Vnet settings have not yet been
applied.
Signed-off-by: Stefan Hanreich
---
src/PVE/API2/Network/SDN/Vnets.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/API2
Because it is needed later in this patch series, the method
pbs_api_connect is moved earlyer in the code
Signed-off-by: Philipp Hufnagl
---
src/PVE/Storage/PBSPlugin.pm | 63 ++--
1 file changed, 32 insertions(+), 31 deletions(-)
diff --git a/src/PVE/Storage/PBSP
This adds a check if the datastore and the namespace is valid when a
user attempts to add a new PBS datastore.
Since the namespace only can be checked after the datastore is
validated, the datastore will be checked as well, regardless that it
will be done later in the superclass anyway.
The funct
Parts contained in activate_storage are needed to be run to fix #5008,
however, implementing a namespace check there would cause unneeded
overhead.
Therefore, this patch extracts the method check_datastore_exists from
activate storage.
Signed-off-by: Philipp Hufnagl
---
src/PVE/Storage/PBSPlugi
This adds a check if the datastore and the namespace is valid when a
user attempts to add a new PBS datastore.
Since the namespace only can be checked after the datastore is
validated, the datastore will be checked as well, regardless that it
will be done later in the superclass anyway.
The funct
It would be nice to reuse an existing PBS connection for scan_datastore.
Because scan_datastore is used multiple in the code, it can not be
changed without breaking existing code.
This change add an optional connection parameter to scan_datastore. If
it is passed it will use this connection. If no
caused by a lapic timer interrupt getting lost.
Already queued for 6.5.13:
https://lore.kernel.org/stable/20231124172031.920738...@linuxfoundation.org/
Reported in the community forum:
https://forum.proxmox.com/threads/136992/
Signed-off-by: Fiona Ebner
---
...c-timer-interrupt-lost-after-load
On 27.11.23 18:39, Fiona Ebner wrote:
> caused by a lapic timer interrupt getting lost.
>
> Already queued for 6.5.13:
> https://lore.kernel.org/stable/20231124172031.920738...@linuxfoundation.org/
>
> Reported in the community forum:
> https://forum.proxmox.com/threads/136992/
>
> Signed-off-by
some (old) systems might have efivars, but don't have the SecureBoot one.
Signed-off-by: Fabian Grünbichler
---
Notes:
reported on the forum for a Dell server from 2009(!):
https://forum.proxmox.com/threads/error-failed-to-read-secure-boot-state-from-pveproxy-since-updating-to-6-5-11-4-
