[pve-devel] [PVE-User] About openvswitch daemon started in S03 and not S01 ?

[alex.lu]

Hi, 
i see this from mailing list:
>>I need to test that again - I thought it works here (why is 'auto' not working?) 

This is strange, if I do after boot: 

#ifup vmbr10 

I have 
ifup: interface bond1 already configured 

(but I can't see any bond1 anywhere) 

then 

#ifdown vmbr10 
#ifup vmbr10 

and now it's ok ... 

>> Ok, I found the problem, my openvswitch daemon started in S03 and not S01.
>> (Don't have checked that updating the packages don't have updated the start
>> order).
>> 
>> So, all is working fine now !

I still get strange ovs error when I shut down my host. Can you confirm this?

I Have same this error , How can I fix it?
 
# ls -l /etc/rc2.d/S01openvswitch-switch 
lrwxrwxrwx 1 root root 28 Feb  7 09:31 /etc/rc2.d/S01openvswitch-switch -> ../init.d/openvswitch-switch

# pveversion -v
proxmox-ve-2.6.32: 3.1-121 (running kernel: 3.10.0-1-pve)
pve-manager: 3.1-45 (running version: 3.1-45/b282dec2)
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-3.10.0-1-pve: 3.10.0-5
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-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-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-4
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20140304/62ecfe4f/attachment.htm>