[SOLVED] Proxmox 3.x to 4.4 upgrade failed (usermod: invalid option -- 'v')

plofkat

Active Member
Mar 20, 2013
51
2
28
Clean install of ProxMox 3.1 on test server
Upgrade to 3.4 (deb http://download.proxmox.com/debian wheezy pve-no-subscription)

Upgraded no issues.
reboot
apt-get update && apt-get dist-upgrade
apt-get remove proxmox-ve-2.6.32 pve-manager corosync-pve openais-pve redhat-cluster-pve pve-cluster pve-firmware
sed -i 's/wheezy/jessie/g' /etc/apt/sources.list
sed -i 's/wheezy/jessie/g' /etc/apt/sources.list.d/pve-no-subscription.list
apt-get update
apt-cache search pve-kernel | sort
apt-get install pve-kernel-4.4.44-1-pve pve-firmware
apt-get upgrade
reboot


No issues so far

apt-get install proxmox-ve

...

Starting AppArmor profiles:Mounting securityfs on /sys/kernel/security...Warning from stdin (line 1): /sbin/apparmor_parser: cannot use or update cache, disable, or force-complain via stdin
.
Setting up lxc-pve (2.0.7-4) ...
usermod: invalid option -- 'v'
Usage: usermod [options] LOGIN

Options:
-c, --comment COMMENT new value of the GECOS field
-d, --home HOME_DIR new home directory for the user account
-e, --expiredate EXPIRE_DATE set account expiration date to EXPIRE_DATE
-f, --inactive INACTIVE set password inactive after expiration
to INACTIVE
-g, --gid GROUP force use GROUP as new primary group
-G, --groups GROUPS new list of supplementary GROUPS
-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
him/her from other groups
-h, --help display this help message and exit
-l, --login NEW_LOGIN new value of the login name
-L, --lock lock the user account
-m, --move-home move contents of the home directory to the
new location (use only with -d)
-o, --non-unique allow using duplicate (non-unique) UID
-p, --password PASSWORD use encrypted password for the new password
-R, --root CHROOT_DIR directory to chroot into
-s, --shell SHELL new login shell for the user account
-u, --uid UID new UID for the user account
-U, --unlock unlock the user account
-Z, --selinux-user SEUSER new SELinux user mapping for the user account

dpkg: error processing package lxc-pve (--configure):
subprocess installed post-installation script returned error exit status 2
Setting up pve-firewall (2.0-33) ...
Installing new version of config file /etc/init.d/pvefw-logger ...
Failed to get D-Bus connection: Unknown error -1
dpkg: error processing package pve-firewall (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on pve-firewall; however:
Package pve-firewall is not configured yet.

dpkg: error processing package qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-container:
pve-container depends on lxc-pve; however:
Package lxc-pve is not configured yet.

dpkg: error processing package pve-container (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on qemu-server (>= 1.1-1); however:
Package qemu-server is not configured yet.
pve-manager depends on pve-firewall; however:
Package pve-firewall is not configured yet.
pve-manager depends on pve-container; however:
Package pve-container is not configured yet.

dpkg: error processing package pve-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.
proxmox-ve depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Setting up dmsetup (2:1.02.93-pve3) ...
update-initramfs: deferring update (trigger activated)
Setting up lvm2 (2.02.116-pve3) ...
Installing new version of config file /etc/init.d/lvm2 ...
Installing new version of config file /etc/lvm/lvm.conf ...
Setting up LVM Volume Groups...done.
update-initramfs: deferring update (trigger activated)
Setting up libpve-storage-perl (4.0-76) ...
Setting up libpve-guest-common-perl (1.0-2) ...
dpkg: dependency problems prevent configuration of pve-ha-manager:
pve-ha-manager depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.19-18+deb8u7) ...
Processing triggers for initramfs-tools (0.109.1) ...
update-initramfs: Generating /boot/initrd.img-4.4.44-1-pve
Processing triggers for dbus (1.8.22-0+deb8u1) ...
Processing triggers for systemd (215-17+deb8u6) ...
Errors were encountered while processing:
lxc-pve
pve-firewall
qemu-server
pve-container
pve-manager
proxmox-ve
pve-ha-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)


Unable to proceed any further


 
how do your /etc/apt/sources.list and /etc/apt/sources.list.d/* files look?

it seems the upgrade to jessie did not really complete because usermod has definitely a -v option in jessie
 
cat /etc/apt/sources.list
deb http://ftp.debian.org/debian jessie main contrib

# security updates
deb http://security.debian.org/ jessie/updates main contrib

cat /etc/apt/sources.list.d/pve-no-subscription.list
deb http://download.proxmox.com/debian jessie pve-no-subscription

cat /etc/apt/sources.list.d/pve-enterprise.list.dpkg-new
# deb https://enterprise.proxmox.com/debian jessie pve-enterprise

Re-running apt-get update and apt-get upgrade just to be sure, going to check the logs to see if I missed some error or made a mistake
 
you need to do a "apt-get dist-upgrade" after switching your sources to jessie and "apt-get update", otherwise you have a mix of wheezy and jessie packages..
 
you need to do a "apt-get dist-upgrade" after switching your sources to jessie and "apt-get update", otherwise you have a mix of wheezy and jessie packages..

Thanks, seems I missed that rather important step somehow.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!