[BUG] VM not updated
Closed this issue · 7 comments
wes1993 commented
Hello,
i have seen that the update of VM not working.... I have configured the SSH access for just one VM because i want to update just this, the scritp check the VM won't go ahead after the first VM:
[Info] Skipped VM 100 because, QEMU or SSH not initialized
Finished, All Updates Done.
root@pve:~/Proxmox-Updater# qm list | tail -n +2 | cut -c -10
100
101
102
103
104
105
I want to update the 105
root@pve:~/Proxmox-Updater/VMs# pwd
/root/Proxmox-Updater/VMs
root@pve:~/Proxmox-Updater/VMs# ls -latr
total 16
-rw-r--r-- 1 root root 21 Dec 8 12:11 example
-rw-r--r-- 1 root root 18 Dec 12 00:14 105
drwxr-xr-x 2 root root 4096 Dec 12 00:19 .
drwxr-xr-x 5 root root 4096 Dec 12 09:51 ..
Best Regards
Stefano
wes1993 commented
I have seen that if i insert in the config only 105 the update works:
################################################
# Only/Exclude LXC and/or VM #
# Example: ONLY/EXCLUDE="100 110 120" #
################################################
# ! If 'ONLY' is set, 'EXCLUDE' don't work ! #
################################################
ONLY="105"
EXCLUDE=""
################################################
# Update-Checker #
# Example: ONLY/EXCLUDE="100 110 120" #
################################################
# ! If 'ONLY' is set, 'EXCLUDE' don't work ! #
################################################
ONLY_UPDATE_CHECK="105"
EXCLUDE_UPDATE_CHECK=""
[Info] Skipped VM 100 by user
[Info] Skipped VM 101 by user
[Info] Skipped VM 102 by user
[Info] Skipped VM 103 by user
[Info] Skipped VM 104 by user
[Info] Backup Skipped by user for LXC 122
[Info] Updating VM 105 : Frigate
--- APT UPDATE ---
Trovato:1 http://security.debian.org/debian-security bookworm-security InRelease
Trovato:2 http://deb.debian.org/debian bookworm InRelease
Scaricamento di:3 http://deb.debian.org/debian bookworm-updates InRelease [52,1 kB]
Scaricamento di:4 https://nvidia.github.io/libnvidia-container/stable/deb/amd64 InRelease [1.477 B]
Trovato:5 https://download.docker.com/linux/debian bookworm InRelease
Recuperati 53,6 kB in 2s (23,1 kB/s)
Lettura elenco dei pacchetti...
--- APT UPGRADE ---
Lettura elenco dei pacchetti...
Generazione albero delle dipendenze...
Lettura informazioni sullo stato...
Calcolo dell'aggiornamento...
I seguenti pacchetti sono stati mantenuti alla versione attuale:
ETC...
Probably could be this return?
else
echo -e "${BL}[Info] Skipped VM $VM because, QEMU or SSH not initialized${CL}\n\n"
return
Best Regards
Stefano
BassT23 commented
you are right, let me brain how to reset "return" correctly ;)
wes1993 commented
OK perfect :-D Thanks for your wonderful work :-D
BassT23 commented
So, now I set up a testing envirenment :)
after rearranged my nodes, my old testing container/VMs are gone :)
now I set up a excluded testing area.
I set up a node with 2 vms inside and tested the master branch.
output:
*** Mode: Host ***
*** Interactive ***
Script is UpToDate
Version: 3.9
[Info] Updating Host : 192.168.XXX.131 | (pve1)
--- APT UPDATE ---
Hit:1 http://download.proxmox.com/debian/pve bookworm InRelease
Hit:2 http://security.debian.org bookworm-security InRelease
Hit:3 http://ftp.de.debian.org/debian bookworm InRelease
Hit:4 http://ftp.de.debian.org/debian bookworm-updates InRelease
Reading package lists...
--- APT UPGRADE ---
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
--- APT CLEANING ---
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Info] Backup Skipped by user for LXC
[Info] Updating VM 900 : test-ubuntu-server-VM1
SSH or QEMU guest agent is not initialized on VM
If you want to update VM, you must set up it by yourself!
For ssh (harder, but nicer output), check this: <https://github.com/BassT23/Proxmox/blob/master/ssh.md>
For QEMU (easy connection), check this: <https://pve.proxmox.com/wiki/Qemu-guest-agent>
[Info] Backup Skipped by user for LXC
[Info] Updating VM 901 : test-ubuntu-server-VM2
SSH or QEMU guest agent is not initialized on VM
If you want to update VM, you must set up it by yourself!
For ssh (harder, but nicer output), check this: <https://github.com/BassT23/Proxmox/blob/master/ssh.md>
For QEMU (easy connection), check this: <https://pve.proxmox.com/wiki/Qemu-guest-agent>
output from beta branch:
*** Mode: Host ***
*** You are on beta branch ***
Version: 3.9.4
[Info] Updating Host : 192.168.XXX.131 | (pve1)
--- APT UPDATE ---
Hit:1 http://download.proxmox.com/debian/pve bookworm InRelease
Hit:2 http://security.debian.org bookworm-security InRelease
Hit:3 http://ftp.de.debian.org/debian bookworm InRelease
Hit:4 http://ftp.de.debian.org/debian bookworm-updates InRelease
Reading package lists...
--- APT UPGRADE HEADLESS ---
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
--- APT CLEANING ---
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Info] Try to create snapshot, otherwise could make a backup for VM 900
[Info] Snapshot created
[Info] Updating VM 900 : test-ubuntu-server-VM1
SSH or QEMU guest agent is not initialized on VM
If you want to update VM, you must set up it by yourself!
For ssh (harder, but nicer output), check this: <https://github.com/BassT23/Proxmox/blob/beta/ssh.md>
For QEMU (easy connection), check this: <https://pve.proxmox.com/wiki/Qemu-guest-agent>
[Info] Try to create snapshot, otherwise could make a backup for VM 901
[Info] Snapshot created
[Info] Updating VM 901 : test-ubuntu-server-VM2
SSH or QEMU guest agent is not initialized on VM
If you want to update VM, you must set up it by yourself!
For ssh (harder, but nicer output), check this: <https://github.com/BassT23/Proxmox/blob/beta/ssh.md>
For QEMU (easy connection), check this: <https://pve.proxmox.com/wiki/Qemu-guest-agent>
so its time to know more about your setup ;)
please give me output from your config file and update status
first make an
update uninstall
then reinstall with
bash <(curl -s https://raw.githubusercontent.com/BassT23/Proxmox/master/install.sh)
after all update to beta branch with
update beta -up
and try again after all
BassT23 commented
ok, now I can reproduce the problem :)
will fix it as soon, as possible
wes1993 commented
Ok perfect!!! :)
BassT23 commented
fixed in latest development version (v3.9.5)