local:xxxxxx.iso does not exist

[nVane]

I upgraded some packages for the first time in several months after changing my apt source, and I am now having a problem where I cannot change the CDROM on any VMs. I get the error "local:xxxx.iso does not exists". The odd thing is I can add the CDROM on the initial creating of a VM, but I cannot change it after.

Contents of /etc/pve/storage.cfg:

dir: local
path /var/lib/vz
content backup,iso,vztmpl
maxfiles 1
shared 0

zfspool: local-zfs
pool rpool/data
content images,rootdir
sparse 1

root@proxmox1:/# ls /var/lib/vz/template/iso/virtio-win-0.1.185.iso
/var/lib/vz/template/iso/virtio-win-0.1.185.iso


Trying with command line:
root@proxmox1:~# qm set 105 -cdrom /var/lib/vz/template/iso/virtio-win-0.1.185.iso
update VM 105: -cdrom /var/lib/vz/template/iso/virtio-win-0.1.185.iso
volume local:iso/virtio-win-0.1.185.iso does not exists


From syslog:
Jul 16 19:51:13 proxmox1 pvedaemon[1043]: <root@pam> update VM 105: -ide1 local:iso/virtio-win-0.1.185.iso,media=cdrom
Jul 16 19:51:13 proxmox1 pvedaemon[1043]: VM 105 creating disks failed

But there's also these lines:
Jul 16 19:27:42 proxmox1 postfix/local[7217]: warning: hash:/etc/aliases is unavailable. open database /etc/aliases.db: No such file or directory
Jul 16 19:27:42 proxmox1 postfix/local[7217]: warning: hash:/etc/aliases: lookup of 'root' failed

Not sure if they're related. Any help would be much appreciated!!

 

[aaron]

Hmm, I suspect that the upgrade did not go that well.

How did you upgrade? Via the GUI or manually on the CLI? If the latter, which commands did you use?

 

[nVane]

Hi Aaron,

I use apt-get update and apt-get upgrade which I think I understand is a mistake now. Unfortunately I already bit the bullet and rebuilt my Proxmox install using VM backups so I'm not sure I'll ever know what went wrong.

 

[aaron]

Okay, well, for other people stumbling over this thread here, in case you do an upgrade with apt-get upgrade or apt upgrade you might end up with a somewhat broken installation. The reason is that these commands will only install new versions of already installed packages but will not handle changing dependencies which would need some packages to be removed and other, new packages, to be fetched to satisfy the new dependencies.

Therefore, the commands to install upgrades should be apt-get dist-upgrade or apt full-upgrade. If you did end up with a somewhat broken installation, it usually works by running apt-get dist-upgrade or the apt equivalent to get everything back to where it should be.