First post on here, so hello everyone 
I've just purchased the single CPU subscription, but when I try to upgrade from 3.2 to 3.3, I'm getting the below:
All containers have been stopped, and there are no errors connecting to the enterprise repository
Any advise on how to get past this would be greatly appreciated.
I've just purchased the single CPU subscription, but when I try to upgrade from 3.2 to 3.3, I'm getting the below:
Code:
Reading package lists... DoneBuilding dependency tree
Reading state information... Done
The following packages have been kept back:
ceph-common fence-agents-pve glusterfs-client glusterfs-common libpve-access-control librados2 librbd1 proxmox-ve-2.6.32 pve-manager pve-qemu-kvm python-ceph qemu-server
0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.All containers have been stopped, and there are no errors connecting to the enterprise repository
Code:
# pveversion -vproxmox-ve-2.6.32: 3.2-132 (running kernel: 2.6.32-31-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-31-pve: 2.6.32-132
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-15
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-23
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1Any advise on how to get past this would be greatly appreciated.
