[jira] [Updated] (CLOUDSTACK-2772) Redundant router: When redundant router recover happened, rebooted BACKUP doesn't have rules programmed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Yang updated CLOUDSTACK-2772: --- Description: When redundant router recover happened due to BACKUP's priority is not equal to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. Command to block eth0 traffic on VR: Block: iptables -I INPUT -j DROP iptables -I OUTPUT -j DROP Unblock: iptables -D INPUT -j DROP iptables -D OUTPUT -j DROP How to test: 1. Start RvR. 2. After two routers are both up, add some firewall rules. 3. Run bumpup_priority.sh in both router's root directory. One of the router would be rebooted by mgmt server soon. After reboot, check if it contained firewall rules. Also check if firewall rule commands are sent after start up commands. was: When redundant router recover happened due to BACKUP's priority is not equal to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. Command to block eth0 traffic on VR: Block: iptables -I INPUT -j DROP iptables -I OUTPUT -j DROP Unblock: iptables -D INPUT -j DROP iptables -D OUTPUT -j DROP How to test: 1. Start RvR. 2. After two routers are both up, add some firewall rules. 3. Run bumpup_priority.sh in both router's root directory. One of the router would be rebooted by mgmt server soon. After reboot, check if it contained firewall rules. > Redundant router: When redundant router recover happened, rebooted BACKUP > doesn't have rules programmed > --- > > Key: CLOUDSTACK-2772 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2772 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.0 >Reporter: Sheng Yang >Assignee: Sheng Yang >Priority: Critical > Fix For: 4.0.2, 4.1.0, 4.2.0 > > > When redundant router recover happened due to BACKUP's priority is not equal > to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. > Command to block eth0 traffic on VR: > Block: > iptables -I INPUT -j DROP > iptables -I OUTPUT -j DROP > Unblock: > iptables -D INPUT -j DROP > iptables -D OUTPUT -j DROP > How to test: > 1. Start RvR. > 2. After two routers are both up, add some firewall rules. > 3. Run bumpup_priority.sh in both router's root directory. > One of the router would be rebooted by mgmt server soon. After reboot, check > if it contained firewall rules. Also check if firewall rule commands are sent > after start up commands. -- 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
[jira] [Updated] (CLOUDSTACK-2772) Redundant router: When redundant router recover happened, rebooted BACKUP doesn't have rules programmed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Yang updated CLOUDSTACK-2772: --- Description: When redundant router recover happened due to BACKUP's priority is not equal to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. Command to block eth0 traffic on VR: Block: iptables -I INPUT -j DROP iptables -I OUTPUT -j DROP Unblock: iptables -D INPUT -j DROP iptables -D OUTPUT -j DROP How to test: 1. Start RvR. 2. After two routers are both up, add some firewall rules. 3. Run bumpup_priority.sh in MASTER router's root directory. BACKUP router would be rebooted by mgmt server soon. After reboot, check if it contained firewall rules. Also check if firewall rule commands are sent after start up commands. was: When redundant router recover happened due to BACKUP's priority is not equal to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. Command to block eth0 traffic on VR: Block: iptables -I INPUT -j DROP iptables -I OUTPUT -j DROP Unblock: iptables -D INPUT -j DROP iptables -D OUTPUT -j DROP How to test: 1. Start RvR. 2. After two routers are both up, add some firewall rules. 3. Run bumpup_priority.sh in both router's root directory. One of the router would be rebooted by mgmt server soon. After reboot, check if it contained firewall rules. Also check if firewall rule commands are sent after start up commands. > Redundant router: When redundant router recover happened, rebooted BACKUP > doesn't have rules programmed > --- > > Key: CLOUDSTACK-2772 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2772 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.0 >Reporter: Sheng Yang >Assignee: Sheng Yang >Priority: Critical > Fix For: 4.0.2, 4.1.0, 4.2.0 > > > When redundant router recover happened due to BACKUP's priority is not equal > to MASTER's priority - 1, rebooted BACKUP doesn't have rules programmed. > Command to block eth0 traffic on VR: > Block: > iptables -I INPUT -j DROP > iptables -I OUTPUT -j DROP > Unblock: > iptables -D INPUT -j DROP > iptables -D OUTPUT -j DROP > How to test: > 1. Start RvR. > 2. After two routers are both up, add some firewall rules. > 3. Run bumpup_priority.sh in MASTER router's root directory. > BACKUP router would be rebooted by mgmt server soon. After reboot, check if > it contained firewall rules. Also check if firewall rule commands are sent > after start up commands. -- 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
