Container CentOS missing nic after restart

[Kage]

Hello,

today i first time restart one of container that works for me as pacemaker cluster ,

container working with 3 NIC eth0 eth1 eth3, after reboot of container i see only eth0.

if i change one number in mac or anything in eth1 and eth3 and save, this appear in Container.

any clue how to avoid this?

Br,

Kage

 

[dietmar]

What OS do you run inside the container? Please can you also port the container config file /etc/pve/lxc/<CTID>.conf?

 

[Kage]

Hello,

use centos-7-default_20160205_amd64.tar.xz


arch: amd64
cpulimit: 1
cpuunits: 1024
hostname: apache2
memory: 512
net0: bridge=vmbr0,gw=192.168.14.254,hwaddr=3A:63:36:32:39:31,ip=192.168.14.244/24,name=eth0,type=veth
net1: bridge=vmbr0,hwaddr=62:61:66:63:32:62,ip=192.168.102.102/24,name=eth1,type=veth
net2: bridge=vmbr0,hwaddr=66:34:36:61:39:63,name=eth3,type=veth
onboot: 1
ostype: centos
rootfs: Container:100/vm-100-disk-1.raw,size=20G
swap: 512


Br,

Kage

 

[fabian]

I cannot reproduce this here - could you post the output of "pveversion -v" and if not uptodate, test this with a current 4.2 installation?

 

[Kage]

Hello,

my OS is up to date.

problem still exist. after contener reboot additionals NIC is missing.

root@hutivu:/home/psobota# pveversion -v
proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
pve-manager: 4.2-2 (running version: 4.2-2/725d76f0)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.2.8-1-pve: 4.2.8-41
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-39
qemu-server: 4.0-72
pve-firmware: 1.1-8
libpve-common-perl: 4.0-59
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-14
pve-container: 1.0-62
pve-firewall: 2.0-25
pve-ha-manager: 1.0-28
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie
fence-agents-pve: 4.0.20-1
pve-sheepdog: not correctly installed


Br,

Kage

 

[fabian]

Could you start the container in question in foreground/debugging mode and collect both the lxt startup log and the system log?

1. shutdown the container if running
2. "lxc-start -n ID -F -lDEBUG -o /tmp/lxc-debug.log"
3. wait until boot completes (lxc-start will not return to the shell, since it was started in foreground mode)
4. shutdown the container using "pct shutdown ID" in a second shell
5. post output of "journalctl -b" (or "journalctl --since -1h"), output of lxc-start from above and content of /tmp/lxc-debug.log