Please don't double post. Other thread in https://forum.proxmox.com/threads/netapp-e-series-multipath-configuration-attach-multipath-iscsi-to-proxmox.170079/
Thanks for the feedback and the report!
We improved the check for the boot-loader issues (but it's still not available on our public repositories) - https://lore.proxmox.com/pve-devel/20250814120807.2653672-1-s.ivanov@proxmox.com/T/#t
I'd...
please check/post the journal after booting when the cards are not available - new kernel/new systemd version might change the names of the NICs - the journal should tell you if there's a problem there.
physically available means that they are...
Looking through our bugzilla (which is the place where feature requests and bug-reports are tracked) I found:
https://bugzilla.proxmox.com/show_bug.cgi?id=5538
which should align with your issue - please note your suggestion there (it gets more...
hmm - check if there are some files in `/etc/ssh/ssh_config.d/` - or even a bit more general run - `grep -rE 'ssh-dss' /etc/` - check this on all nodes in your cluster!
if that does not point to the issue - please open a new thread (feel free to...
Can you post the output of ip a as well? Would be interesting to see if ens6f0 still has enp3s0f0 as altname. Because then there is probably an error in the logic of ifupdown2 that sets the MTU, where altnames do not yet get resolved.
edit: a...
as @LnxBil said - it would help a lot to know which commands you ran to get in that situation?
(and to provide /var/log/apt/term.log and history.log from that upgrade)
a very blind guess: did you maybe run `apt upgrade` instead of `apt...
What command did you use to upgrade the OS? You just showed the error message, but not what lead to the error.
The missing file should be at /usr/lib/x86_64-linux-gnu/perl5/5.40/AptPkg/Config.pm in Trixie.
No - the permission system in PMG is not domain aware - and for a very large part of the administration/configuration the settings are global (e.g. rules, most postfix configuration,...)
I hope this helps!
Contributions are very welcome - thanks for the suggestion!
We use a mail-based workflow - see https://pve.proxmox.com/wiki/Developer_Documentation for submitting patches.
from a quick look at the code: https://git.proxmox.com/?p=pve-container.git;a=blob;f=src/PVE/LXC/Setup/Base.pm;h=dbfc775c6f4769609c50caa6c8a7b91a91566080;hb=HEAD#l294
It should be set to true, if you set the containers IPv6 config to 'auto'...
send a patch for this just yesterday: https://lore.proxmox.com/pbs-devel/20250818194026.840749-2-s.ivanov@proxmox.com/T/#u
:)
Thanks for the report in any case!
Just a nitpick running pbs3to4:
SKIP: System booted in legacy-mode - no need for additional pacckages.
should be
SKIP: System booted in legacy-mode - no need for additional packages.
(One less c in packages!)
see: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine - v320.pre is handled by the templateing system.
I hope this helps!
Yes! (systems not using proxmox-boot-tool should have it mounted on /boot/efi)
proxmox-boot-tool is (currently) used for all installations which are not using Ext4/XFS (with LVM) - it was initially added to handle ESPs for machines with multiple...
See: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine - the postfix configuration is done via templates.
127.0.0.1 is also called the loop-back ip (localhost) and is e.g. used to speak with services on the same...