Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Wed, May 20, 2015 at 05:38:43PM +0200, Dietmar Maurer wrote: > >So adding a node node X to cluster A, that was > > previously in cluster B and contains resources from the old cluster B. > > Right? If it would not have been part of some kind of cluster B, it > > would not have a control volume. "add-node" is synonymous for > > "new-node". And "new-node" means that this node becomes part of the new > > cluster and its old information is not required anymore. > > Something is very confusing here. It happens when the new node > already contains a (empty) control volume. (I do many test here, > so I often reset/delete my test nodes with 'drbdmanage init'). For a clean node state after testing you can use "drbdmanage uninit" which removes the control volume from the node. > The documentation states you need to execute add-node on a existing > cluster node. If you do that, you get the information that this will > destroy your existing control volume. > > I guess this is because it automatically open ssh to the new node, so this > output is from the new node, but printed one the console of the old node. > Can you see the problem? Yes. That might be confusing if you are not one of the drbdmanage devs ;-). I will add a big fat "***THIS IS THE IN/OUTPUT OF NODE bla***" kind of thing. In short: What you did was fine, you could have used "uninit", the (correct) noise was from your new node, displayed on your old/existing node... Regards, rck