TASK ERROR: unsupported Ubuntu version '18.04'

[arnolem]

Hello,

I have update the templates list with :

pveam update

I have create a container with the new Ubuntu-18.04-standard template but I have this error :

TASK ERROR: unsupported Ubuntu version '18.04'

​

I have update my Proxmox with :

aptitude update
aptitude upgrade

​

This is my ve version

pveversion -v

proxmox-ve: 4.4-109 (running kernel: 4.4.67-1-pve)
pve-manager: 4.4-22 (running version: 4.4-22/2728f613)
pve-kernel-4.4.117-1-pve: 4.4.117-109
pve-kernel-4.2.8-1-pve: 4.2.8-41
pve-kernel-4.4.67-1-pve: 4.4.67-92
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+2
libqb0: 1.0.1-1
pve-cluster: 4.0-54
qemu-server: 4.0-115
pve-firmware: 1.1-11
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.9.1-9~pve4
pve-container: 1.0-105
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80

What does it mean (Why 4.4-109 but 4.4.67 is running? how to change this?):

proxmox-ve: 4.4-109 (running kernel: 4.4.67-1-pve)

Thanks

 

[haxxa]

It was fixed today:

Try these commands again:

pveam update
apt update
apt full-upgrade

Then try create the container and it should work

If not reboot and it should then be running the latest kernel.

 

[arnolem]

Thanks for your reply.
I have try this but I a the same error

extracting archive '/var/lib/vz/template/cache/ubuntu-18.04-standard_18.04-1_amd64.tar.gz'
Total bytes read: 623677440 (595MiB, 157MiB/s)
Detected container architecture: amd64
Logical volume "vm-100-disk-1" successfully removed
TASK ERROR: unsupported Ubuntu version '18.04'

 

[arnolem]

I have the problem only on Proxmox Virtual Environment 4.4-22

 

[dietmar]

This only works with latest 5.X version.

 

[arnolem]

This only works with latest 5.X version.

I have try to upgrade my server but i loose it. Debian is upgrade but all PVE tools are missed. I reinstall a new spare server

 

[fireon]

I have try to upgrade my server but i loose it. Debian is upgrade but all PVE tools are missed. I reinstall a new spare server

Have you followed the guide? Have upgraded about 50+ here, never had a problem with.

 

[arnolem]

Have you followed the guide? Have upgraded about 50+ here, never had a problem with.

Yes, I have followed this guide.
I had a problem doing the first upgrade (To the last proxmox 4.X) :

Resolving dependencies...
The following NEW packages will be installed:
pve-kernel-4.4.117-1-pve{a}
The following packages will be upgraded:
cpp-4.9
The following partially installed packages will be configured:
initramfs-tools proxmox-ve
1 packages upgraded, 1 newly installed, 0 to remove and 78 not upgraded.

Need to get 0 B/49.8 MB of archives. After unpacking 12.3 kB will be used.
Do you want to continue? [Y/n/?] y
Reading changelogs... Done
(Reading database ... 67426 files and directories currently installed.)
Preparing to unpack .../pve-kernel-4.4.117-1-pve_4.4.117-109_amd64.deb ...
Unpacking pve-kernel-4.4.117-1-pve (4.4.117-109) ...
Preparing to unpack .../cpp-4.9_4.9.2-10+deb8u1_amd64.deb ...
Unpacking cpp-4.9 (4.9.2-10+deb8u1) over (4.9.2-10) ...
Setting up initramfs-tools (0.120+deb8u3) ...
update-initramfs: deferring update (trigger activated)
Setting up pve-kernel-4.4.117-1-pve (4.4.117-109) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.117-1-pve /boot/vmlinuz-4.4.117-1-pve
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.117-1-pve /boot/vmlinuz-4.4.117-1-pve
update-initramfs: Generating /boot/initrd.img-4.4.117-1-pve
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.117-1-pve /boot/vmlinuz-4.4.117-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.117-1-pve
Found initrd image: /boot/initrd.img-4.4.117-1-pve
Found linux image: /boot/vmlinuz-4.4.67-1-pve
Found initrd image: /boot/initrd.img-4.4.67-1-pve
Found linux image: /boot/vmlinuz-4.4.40-1-pve
Found initrd image: /boot/initrd.img-4.4.40-1-pve
Found linux image: /boot/vmlinuz-4.4.35-2-pve
Found initrd image: /boot/initrd.img-4.4.35-2-pve
Found linux image: /boot/vmlinuz-4.4.19-1-pve
Found initrd image: /boot/initrd.img-4.4.19-1-pve
Found linux image: /boot/vmlinuz-4.2.8-1-pve
Found initrd image: /boot/initrd.img-4.2.8-1-pve
Found memtest86+ image: /memtest86+.bin
Found memtest86+ multiboot image: /memtest86+_multiboot.bin
done
Setting up proxmox-ve (4.4-109) ...
Setting up cpp-4.9 (4.9.2-10+deb8u1) ...
Processing triggers for initramfs-tools (0.120+deb8u3) ...
update-initramfs: Generating /boot/initrd.img-4.4.117-1-pve

gzip: stdout: No space left on device
E: mkinitramfs failure find 141 cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.4.117-1-pve with 1.
dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package. Trying to recover:
Setting up initramfs-tools (0.120+deb8u3) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.120+deb8u3) ...
update-initramfs: Generating /boot/initrd.img-4.4.117-1-pve

gzip: stdout: No space left on device
cpio: write error: Broken pipe
find: `standard output': Broken pipe
find: write error
E: mkinitramfs failure find 1 cpio 1 gzip 1
update-initramfs: failed for /boot/initrd.img-4.4.117-1-pve with 1.
dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
initramfs-tools

I have clean my /boot/ deleting 2 old linux image and I have follow the guide to upgrade to 5.X.

So, I bought a new physical machine and I migrate all my server for 14 hours ;-)

 

[Borut]

This only works with latest 5.X version.

What works only with latest 5.X version? I have PVE version 5.1-41 and tried to create my first CT:

root@starspot:~# pveam available --section system
system alpine-3.4-default_20161206_amd64.tar.xz
system alpine-3.5-default_20170504_amd64.tar.xz
system alpine-3.6-default_20171211_amd64.tar.xz
system alpine-3.7-default_20171211_amd64.tar.xz
system archlinux-base_20171214-1_amd64.tar.gz
system centos-6-default_20161207_amd64.tar.xz
system centos-7-default_20171212_amd64.tar.xz
system debian-6.0-standard_6.0-7_amd64.tar.gz
system debian-7.0-standard_7.11-1_amd64.tar.gz
system debian-8.0-standard_8.7-1_amd64.tar.gz
system debian-9.0-standard_9.3-1_amd64.tar.gz
system fedora-26-default_20171212_amd64.tar.xz
system fedora-27-default_20171212_amd64.tar.xz
system gentoo-current-default_20171211_amd64.tar.xz
system opensuse-42.3-default_20171214_amd64.tar.xz
system ubuntu-12.04-standard_12.04-1_amd64.tar.gz
system ubuntu-14.04-standard_14.04-1_amd64.tar.gz
system ubuntu-16.04-standard_16.04-1_amd64.tar.gz
system ubuntu-16.10-standard_16.10-1_amd64.tar.gz
system ubuntu-17.04-standard_17.04-1_amd64.tar.gz
system ubuntu-17.10-standard_17.10-1_amd64.tar.gz
system ubuntu-18.04-standard_18.04-1_amd64.tar.gz

root@starspot:~# pveam list local
NAME SIZE

root@starspot:~# pveam download local ubuntu-18.04-standard_18.04-1_amd64.tar.gz
starting template download from: http://download.proxmox.com/images/system/ubuntu-18.04-standard_18.04-1_amd64.tar.gz
target file: /var/lib/vz/template/cache/ubuntu-18.04-standard_18.04-1_amd64.tar.gz
--2018-05-23 13:51:37-- http://download.proxmox.com/images/system/ubuntu-18.04-standard_18.04-1_amd64.tar.gz
Resolving download.proxmox.com (download.proxmox.com)... 212.224.123.70, 2a01:7e0:0:424::249
Connecting to download.proxmox.com (download.proxmox.com)|212.224.123.70|:80... connected.
HTTP request sent, awaiting response... 200 OK
...

Creating CT failed:

extracting archive '/var/lib/vz/template/cache/ubuntu-18.04-standard_18.04-1_amd64.tar.gz'
Total bytes read: 623677440 (595MiB, 105MiB/s)
Detected container architecture: amd64
TASK ERROR: unsupported Ubuntu version '18.04'

What am I doing wrong?

 

[fireon]

TASK ERROR: unsupported Ubuntu version '18.04'

Your system does not support 18.04, this was updated quite recently. So update your system. After it will work for you.

 

[Borut]

Exist a command to list supported "--section system" for installed version `uname -r`? This should be as default and not that user is trying as long as find supported one...

I installed "centos-7-default_20171212_amd64.tar.xz" which is supported.I was able, at least to, install it, bu not start:
● pve-container@103.service - PVE LXC Container: 103
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-05-24 11:42:57 CEST; 31min ago
Docs: man:lxc-start
man:lxc
manct
Process: 111184 ExecStart=/usr/bin/lxc-start -n 103 (code=exited, status=1/FAILURE)

May 24 11:42:57 starspot systemd[1]: Starting PVE LXC Container: 103...
May 24 11:42:57 starspot lxc-start[111184]: lxc-start: 103: lxccontainer.c: wait_on_daemonized_start: 751 No such file or directory - Failed to receive the container state
May 24 11:42:57 starspot lxc-start[111184]: lxc-start: 103: tools/lxc_start.c: main: 371 The container failed to start.
May 24 11:42:57 starspot lxc-start[111184]: lxc-start: 103: tools/lxc_start.c: main: 373 To get more details, run the container in foreground mode.
May 24 11:42:57 starspot lxc-start[111184]: lxc-start: 103: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --logpriority options.
May 24 11:42:57 starspot systemd[1]: pve-container@103.service: Control process exited, code=exited status=1
May 24 11:42:57 starspot systemd[1]: pve-container@103.service: Killing process 111187 (lxc-start) with signal SIGKILL.
May 24 11:42:57 starspot systemd[1]: Failed to start PVE LXC Container: 103.
May 24 11:42:57 starspot systemd[1]: pve-container@103.service: Unit entered failed state.
May 24 11:42:57 starspot systemd[1]: pve-container@103.service: Failed with result 'exit-code'.

Looks like there are many bugs in PVE...

 

[tom]

...
Looks like there are many bugs in PVE...

This thread is about ubuntu 18.04, so if you have any other issue please open a new thread. If you find a bug, report it to our bugtracker.

 

[Andres Vargas Duarte]

Hello everyone,

Edit:
/usr/share/perl5/PVE/LXC/Setup/Debian.pm or file.pm

die "unsupported debian version '$version'\n"
- if !($version >= 4 && $version <= 9);

for

if !($version >= 4 && $version <= 9.9);
or
if !($version >= 4 && $version <= 11);

You always forget to mention that you must restart the PROXMOX server, to make it work, otherwise it is useless to modify this file and the line. Greetings.