[PVE-User] Proxmox VE 5.3 released!

Stoiko Ivanov s.ivanov at proxmox.com
Tue Dec 4 15:17:03 CET 2018


Hi,

to me the most strage thing is the removal of grub (which in turn
probably leads to the removal of proxmox-ve)

could you please post the complete output of `apt update`?
do you have any other repositories configured
(/etc/apt/sources.list, /etc/apt/sources.list.d/*)?

Thanks,
stoiko



On Tue, 4 Dec 2018 23:59:41 +1000
Lindsay Mathieson <lindsay.mathieson at gmail.com> wrote:

> One server has upgraded clean so far, but the 2nd one wants to remove
> pve :(
> 
> apt-get dist-upgrade
> The following packages were automatically installed and are no longer 
> required:
>    apparmor ceph-fuse criu ebtables fonts-font-awesome hdparm ipset 
> libapparmor-perl libboost-iostreams1.55.0
> libboost-program-options1.55.0 libboost-random1.55.0
>    libboost-regex1.55.0 libboost-system1.55.0 libboost-thread1.55.0 
> libgnutlsxx28 libgoogle-perftools4 libicu52 libipset3 libjs-extjs 
> libjson-c3 liblttng-ust-ctl2 liblttng-ust0
>    libnet1 libnetfilter-log1 libprotobuf-c1 libprotobuf10 
> libpve-access-control libpve-apiclient-perl libpve-guest-common-perl 
> libpve-http-server-perl libpve-storage-perl
>    librados2-perl libtcmalloc-minimal4 libtemplate-perl libunwind8 
> liburcu4 libuuid-perl lxc-pve lxcfs novnc-pve proxmox-widget-toolkit 
> pve-cluster pve-container pve-docs
>    pve-edk2-firmware pve-firewall pve-ha-manager pve-i18n pve-manager 
> pve-xtermjs python-ipaddr python-protobuf qemu-server spiceterm uidmap
> Use 'apt autoremove' to remove them.
> The following packages will be REMOVED:
>    grub-common grub-pc grub-pc-bin grub2-common libnvpair1 libzfs2 
> proxmox-ve pve-kernel-4.15 pve-kernel-4.15.17-2-pve 
> pve-kernel-4.15.17-3-pve pve-kernel-4.15.18-4-pve
>    pve-kernel-4.15.18-5-pve
> The following NEW packages will be installed:
>    libboost-program-options1.62.0 libboost-random1.62.0 
> libboost-regex1.62.0 libfdt1 libjson-c3 libopus0
> The following packages will be upgraded:
>    ceph-common libcephfs1 libnvpair1linux libpve-common-perl 
> libpve-storage-perl librados2 libradosstriper1 librbd1 librgw2 
> libzfs2linux libzpool2linux pve-container
>    pve-libspice-server1 pve-manager pve-qemu-kvm python-cephfs 
> python-rados python-rbd qemu-server zfs-initramfs zfs-zed
> zfsutils-linux
> 
> 
> I've done a plain apt-get update + upgrade and rebooted.
> 
> Current versions:
> 
> pveversion -v
> proxmox-ve: 5.3-1 (running kernel: 4.15.18-5-pve)
> pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
> pve-kernel-4.15: 5.2-8
> pve-kernel-4.15.18-5-pve: 4.15.18-24
> pve-kernel-4.15.18-4-pve: 4.15.18-23
> pve-kernel-4.15.17-3-pve: 4.15.17-14
> pve-kernel-4.15.17-2-pve: 4.15.17-10
> corosync: 2.4.4-pve1
> criu: 2.11.1-1~bpo90
> glusterfs-client: 3.10.5-1
> ksm-control-daemon: 1.2-2
> libjs-extjs: 6.0.1-2
> libpve-access-control: 5.1-3
> libpve-apiclient-perl: 2.0-5
> libpve-common-perl: 5.0-40
> libpve-guest-common-perl: 2.0-18
> libpve-http-server-perl: 2.0-11
> libpve-storage-perl: 5.0-29
> libqb0: 1.0.3-1~bpo9
> lvm2: 2.02.168-pve6
> lxc-pve: 3.0.2+pve1-5
> lxcfs: 3.0.2-2
> novnc-pve: 1.0.0-2
> openvswitch-switch: 2.7.0-3
> proxmox-widget-toolkit: 1.0-22
> pve-cluster: 5.0-31
> pve-container: 2.0-27
> pve-docs: 5.3-1
> pve-firewall: 3.0-16
> pve-firmware: 2.0-6
> pve-ha-manager: 2.0-5
> pve-i18n: 1.0-9
> pve-libspice-server1: 0.12.8-3
> pve-qemu-kvm: 2.11.2-1
> pve-sheepdog: 1.0.2-1
> pve-xtermjs: 1.0-5
> qemu-server: 5.0-36
> smartmontools: 6.5+svn4324-1
> spiceterm: 3.0-5
> vncterm: 1.5-3
> zfsutils-linux: 0.7.11-pve1~bpo1
> 
> 
> 
> This is probably my oldest server, started off as Proxmox 3.x
> 
> On 4/12/2018 8:24 pm, Martin Maurer wrote:
> > Hi all!
> >
> > We are very excited to announce the general availability of Proxmox
> > VE 5.3!
> >
> > Proxmox VE now integrates CephFS, a distributed, POSIX-compliant
> > file system which serves as an interface to the Ceph storage (like
> > the RBD). You can store backupfiles, ISO images, and container
> > templates. CephFS can be created and configured easily with its
> > Metadata server (MDS) in the GUI.
> >
> > We improved disk management and you can now add ZFS raid volumes,
> > LVM, and LVMthin pools as well as additional disks with a
> > traditional file system. The existing ZFS over iSCSI storage
> > plug-in can now access LIO target in the Linux kernel. Other new
> > features are nesting for LXC containers so you can use LXC and LXD
> > inside containers or access NFS or CIFS. If you are adventurous,
> > you can configure PCI passthrough and vGPUs via the GUI.
> >
> > Countless bugfixes and more smaller improvements are listed in the 
> > release notes.
> >
> > Release notes
> > https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_5.3
> >
> > Video tutorial
> > Watch our short introduction video What's new in Proxmox VE 5.3?
> > https://www.proxmox.com/en/training/video-tutorials
> >
> > Download
> > https://www.proxmox.com/en/downloads
> > Alternate ISO download:
> > http://download.proxmox.com/iso/
> >
> > Source Code
> > https://git.proxmox.com
> >
> > Bugtracker
> > https://bugzilla.proxmox.com
> >
> > FAQ
> > Q: Can I install Proxmox VE 5.3 on top of Debian Stretch?
> > A: Yes, see 
> > https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch
> >
> > Q: Can I upgrade Proxmox VE 5.x to 5.3 with apt?
> > A: Yes, just via GUI or via CLI with apt update && apt dist-upgrade
> >
> > Q: Can I upgrade Proxmox VE 4.x to 5.3 with apt dist-upgrade?
> > A: Yes, see https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0.
> > If you Ceph on V4.x please also check 
> > https://pve.proxmox.com/wiki/Ceph_Jewel_to_Luminous. Please note, 
> > Proxmox VE 4.x is already end of support since June 2018, see
> > Proxmox VE Support Lifecycle 
> > https://forum.proxmox.com/threads/proxmox-ve-support-lifecycle.35755/
> >
> > Many THANKS to our active community for all your feedback, testing, 
> > bug reporting and patch submitting!
> >  
> 




More information about the pve-user mailing list