On 04/07/2013, at 8:37 PM, Leon Fauster <leonfaus...@googlemail.com> wrote:
> Am 04.07.2013 um 12:02 schrieb andreas graeper <agrae...@googlemail.com>: >> >> i tried to change the IPaddr2 parameter ip >> >> 1) crm resource edit <rsc> >> >> 2) pcs resource update <rsc> <attr>=<value> >> >> in both cases the cib is modified (`crm configure show` shows) >> but old ip only is pingable and all depending resources are stopped >> >> crm resource stop p_clusterip # does not stop that resource ?! >> crm resource start p_clusterip >> >> after >> crn resource cleanup p_clusterip >> i can ping both (new and old) ip >> >> `ip addr show` >> inet 172.27.10.91/16 brd 172.27.255.255 scope global eth0 >> inet 172.27.10.199/16 brd 172.27.255.255 scope global secondary eth0 >> inet 172.27.10.90/16 brd 172.27.255.255 scope global secondary eth0 >> maybe ip_stop() / delete_address() did not succeed ? >> >> how this is done correctly ? > > > stop resource > change resource > start resource Shouldn't be necessary. The cluster /should/ detect the change and perform a stop (with the old values) and a start (with the new). _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
