Zentyal/zentyal — pull request #1347 by figarocorso (2014-06-03 13:41:21+00:00)
Title: Mjulian/service replication exception

When the webadmin port was changed in one of the HA nodes, that port changed also at the rest of the nodes. That behaviour shouldn't happen. So that setting is added as a exception to the HA replication:

Zentyal High Availability
InstallNonProfilePackages: OK
InstallNonProfilePackages2: OK
InitClusterConf: OK
EnableFireallModule: OK
EnableModule: OK
SetDHCPRange: OK
GetClusterSecret: OK
JoinCluster: OK
EnableFirewallModule2: OK
EnableModule2: OK
SetFloatingIP: OK
SaveChanges: OK
CheckFloatingIP: OK
EnableDHCPModule: OK
EnableDHCPModule2: OK
CheckIPCollisions: OK
CheckHAStatus: OK
CheckIPResourceRunning: OK
CheckDHCPResourceRunning: OK
ResourcesAtServer: OK
TestDHCPRunning: OK
TestDHCPNotRunning: OK
PromoteHAServer: OK
CheckHAStatus2: OK
CheckIPResourceRunning2: OK
CheckDHCPResourceRunning2: OK
ResourcesAtServer2: OK
TestDHCPRunning2: OK
TestDHCPNotRunning2: OK
DemoteHAServer: OK
CheckHAStatus3: OK
CheckIPResourceRunning3: OK
CheckDHCPResourceRunning3: OK
ResourcesAtServer3: OK
TestDHCPRunning3: OK
TestDHCPNotRunning3: OK
ChangeAdminPort: OK
SaveChangesAdminPort: OK
CheckNodePortChange: OK
TestDeleteDefaultAccessRule: OK
TestCreateProfile: OK
TestProfileReplicated: OK
TestCreateProfile2: OK
TestProfileReplicated2: OK
check-zentyal-log: OK
check-syslog-apparmor: OK
check-zentyal-log: OK
check-syslog-apparmor: OK