[ https://issues.apache.org/jira/browse/CLOUDSTACK-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wei Zhou closed CLOUDSTACK-1211. -------------------------------- > Network operations are Blocked for the Read-only file system of Virtual Router > ------------------------------------------------------------------------------ > > Key: CLOUDSTACK-1211 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1211 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Affects Versions: 4.0.0 > Reporter: Wei Zhou > Assignee: Wei Zhou > Fix For: 4.0.2 > > > Sometimes the virtual router VM has read-only file system for some reasons, > such as the Abnormal shutdown of the Host. This is not that we expected, but > really happens. > When this happens, the network operations will receive error messages and > fail. But indeed it is not. For example, > (1) Acquire IP. always in "Allocating" state. > (2) EnableStaticNat, the result is success(it is incorrect). > (3) DisableStaticNat. This is correct. > (4) Add Firewalls. always in "Adding" state. > Furthermore, The AgentManager report statistics every 60 minutes(normally it > should be router.stats.interval=5 minutes). > The agent.log show this after restart cloud-mnagement: > 2013-02-08 08:02:12,612 WARN [kvm.resource.LibvirtComputingResource] > (Script-6:null) Interrupting script. > 2013-02-08 08:02:12,614 WARN [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-4:null) Timed out: > /usr/lib/cloud/common/scripts/network/domr/router_proxy.sh netusage.sh > 169.254.0.151 -g . Output is: /root/func.sh: line 44: > /tmp/biglock-31028.lock: Permission deniedls: cannot access > /tmp/biglock-*.lock: No such file or directory/root/func.sh: line 49: [: -ef: > unary operator expectedls: cannot access /tmp/biglock-*.lock: No such file or > directory/root/func.sh: line 49: [: -ef: unary operator expected > ...... > 2013-02-08 10:44:18,925 INFO [cloud.agent.Agent] (Agent-Handler-3:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-02-08 10:44:18,926 INFO [cloud.agent.Agent] (Agent-Handler-3:null) > Cannot connect because we still have 3 commands in progress. > To reproduce > (1) log in the virtual router from console, or ssh from host. > (2) to generate errors, use "chattr =i -R /tmp" > (3) to remove errors, use "chattr -i -R /tmp" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira