[BUG Found] unable to remove LXC container

B

brosky

Well-Known Member
Oct 13, 2015
55
4
48
Hi,

System: fresh proxmox 4 install, local storage is 400g SSD and secondary /storage is 12TB HDD

I create a LXC container using the provided ubuntu14 template:

Code: 
[COLOR=#000000][FONT=tahoma]Formatting '/storage/images/102/vm-102-disk-1.raw', fmt=raw size=1099511627776[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]mke2fs 1.42.12 (29-Aug-2014)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Discarding device blocks:      4096/268435456                   done                            [/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Creating filesystem with 268435456 4k blocks and 67108864 inodes[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Filesystem UUID: 64c8a8ae-68b1-407a-92a7-ae3f1a0ae043[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Superblock backups stored on blocks: [/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, [/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]    4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, [/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]    102400000, 214990848[/FONT][/COLOR]

[COLOR=#000000][FONT=tahoma]Allocating group tables:    0/8192         done                            [/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Writing inode tables:    0/8192         done                            [/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Creating journal (32768 blocks): done[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Multiple mount protection is enabled with update interval 5 seconds.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Writing superblocks and filesystem accounting information:    0/8192         done[/FONT][/COLOR]

[COLOR=#000000][FONT=tahoma]Use of uninitialized value $path in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1969.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Use of uninitialized value $path in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1969.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]extracting archive '/storage/template/cache/ubuntu-14.04-standard_14.04-1_amd64.tar.gz'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Total bytes read: 437422080 (418MiB, 141MiB/s)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Detected container architecture: amd64[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Creating SSH host key 'ssh_host_ecdsa_key' - this may take some time ...[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Creating SSH host key 'ssh_host_dsa_key' - this may take some time ...[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Creating SSH host key 'ssh_host_key' - this may take some time ...[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Creating SSH host key 'ssh_host_ed25519_key' - this may take some time ...[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Creating SSH host key 'ssh_host_rsa_key' - this may take some time ...[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Use of uninitialized value $path in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1969.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Use of uninitialized value $path in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1969.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Use of uninitialized value $path in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1969.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK OK[/FONT][/COLOR]

and I can't start it:

Code: 
[COLOR=#000000][FONT=tahoma]Use of uninitialized value $path in concatenation (.) or string at /usr/share/perl5/PVE/LXC.pm line 1110.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]lxc-start: lxc_start.c: main: 344 The container failed to start.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK OK[/FONT][/COLOR]

and I can't remove it:

Code: 
[COLOR=#000000][FONT=tahoma]Use of uninitialized value $path in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1969.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Use of uninitialized value $volume in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1404.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Use of uninitialized value $volid in pattern match (m//) at /usr/share/perl5/PVE/Storage/Plugin.pm line 188.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Use of uninitialized value $volid in concatenation (.) or string at /usr/share/perl5/PVE/Storage/Plugin.pm line 192.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK ERROR: unable to parse volume ID ''[/FONT][/COLOR]

- same situation with CentOS template.
- no issues with VM (the VM is created properly and I can manage the resources)

I've tested in various disk size configurations and only if I specify "1024" as the size it crashes. (1025 or 1000 is fine)
Also, 2048 fails while 2049 works.

As now I have a couple of un-removable LXC containers, please advise to to remove them :)
 
Hi,
can you please post the output of
pveversion -v
 
i have the same problem
when i want to start lxc got:
Use of uninitialized value $path in concatenation (.) or string at /usr/share/perl5/PVE/LXC.pm line 1110.
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
TASK OK
Click to expand...

when i want to remove them:
Use of uninitialized value $path in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1969.
Use of uninitialized value $volume in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1404.
Use of uninitialized value $volid in pattern match (m//) at /usr/share/perl5/PVE/Storage/Plugin.pm line 188.
Use of uninitialized value $volid in concatenation (.) or string at /usr/share/perl5/PVE/Storage/Plugin.pm line 192.
TASK ERROR: unable to parse volume ID ''
Click to expand...


proxmox-ve: 4.0-16 (running kernel: 4.2.2-1-pve)
pve-manager: 4.0-48 (running version: 4.0-48/0d8559d0)
pve-kernel-4.2.2-1-pve: 4.2.2-16
lvm2: 2.02.116-pve1
corosync-pve: 2.3.5-1
libqb0: 0.17.2-1
pve-cluster: 4.0-22
qemu-server: 4.0-30
pve-firmware: 1.1-7
libpve-common-perl: 4.0-29
libpve-access-control: 4.0-9
libpve-storage-perl: 4.0-25
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.4-9
pve-container: 1.0-6
pve-firewall: 2.0-12
pve-ha-manager: 1.0-9
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.3-1
lxcfs: 0.9-pve2
cgmanager: 0.37-pve2
criu: 1.6.0-1
zfsutils: 0.6.5-pve4~jessie
Click to expand...
 
here:
arch: amd64
cpulimit: 1
cpuunits: 1024
hostname: something.mydomain.com
memory: 1024
net0: bridge=vmbr1,gw=XX.XX.XX.XX,hwaddr=XX:XX:XX:XX:XX:XX,ip=XX.XX.XX.XX/24,name=eth0,type=veth
ostype: debian
rootfs: local:101/vm-101-disk-1.raw,size=2T
swap: 1024
Click to expand...
 
I made a bugfix, will be available in pve-container greater 1.0-8.
current work around make only container with max 1023 G rootfs size.
 
wolfgang said:
I made a bugfix, will be available in pve-container greater 1.0-8.
current work around make only container with max 1023 G rootfs size.
Click to expand...


Ок,

is it ok to delete this lxc with.
rm /etc/pve/lxc/101.conf
and
rm -rf /var/lib/vz/images/101/

?????
 
yes this is correct.
 
You must log in or register to reply here.
Top Bottom