Broken openvswitch init dependency

[sacculus]

Hi
I saw some errors about inaccessible unix socket when PVE was booting.
When I investigated boot sequence I found that openvswitch may start before local fs's were mounted. When "/run" is mounting it overlays on created openvswitch socket and pid files.
So when I added dependency on $local_fs in init Required-Start section, those errors were gone.

 

[cesarpk]

Hi sacculus

Did you installed PVE of his own ISO installer, or of a debian for after update it?

Best regards
Cesar

 

[sacculus]

Hi

Hi sacculus

Did you installed PVE of his own ISO installer, or of a debian for after update it?

I didn't set up this system personally.
I only know that it was installed from one of previous releases of PVE ISO and then it was upgraded to 3.2 in a few steps.

 

[cesarpk]

So when I added dependency on $local_fs in init Required-Start section, those errors were gone.

In any way, you did a good work, and will be good that you make a report of this error in https://bugzilla.proxmox.com/

Only for know how you apply the solution, can you post here the content of the file(s) that you modified

Best regards
Cesar

 

[sacculus]

Hi cesarpk

In any way, you did a good work, and will be good that you make a report of this error in https://bugzilla.proxmox.com/

Only for know how you apply the solution, can you post here the content of the file(s) that you modified

Best regards
Cesar

I tried, but "Component" field on bug registration page doesn't have any option related to openvswitch. What option should I select?

This is my change to openvswitch init script (/etc/init.d/openvswitch-switch), it is very simple:

--- openvswitch-switch.ORIG    2014-01-07 10:49:47.000000000 +0200
+++ openvswitch-switch    2014-06-09 23:38:47.000000000 +0300
@@ -16,7 +16,7 @@
 #
 ### BEGIN INIT INFO
 # Provides:          openvswitch-switch
-# Required-Start:    pvenetcommit
+# Required-Start:    pvenetcommit $local_fs
 # Required-Stop:     $local_fs
 # X-Start-Before:    networking
 # X-Stop-After:      networking

 

[cesarpk]

Thanks for the answer

And about of make a report of this error in https://bugzilla.proxmox.com/ , if you don't have a field that correspond with the error, try it with the option nearest, may be "pve-manager" or "pve-kernel".

I particularly am not registered in bugzilla, so i am not enabled for answer with property, but believe that "pve-manager" (the GUI of PVE) or "pve-kernel" will be the more nearest

Best regards
Cesar

 

[sacculus]

Hi

In any way, you did a good work, and will be good that you make a report of this error in https://bugzilla.proxmox.com/

Only for know how you apply the solution, can you post here the content of the file(s) that you modified

Best regards
Cesar

Done
https://bugzilla.proxmox.com/show_bug.cgi?id=528