Comment #3 on issue 270 by [email protected]: drbd sync fails on readded
node
http://code.google.com/p/ganeti/issues/detail?id=270
--ignore-consistency is not valid for replace-disks. -a fails for
I am suffering from exactly the same problem on a production 2 node cluster
I'm in the middle of upgrading. In my test environment (and in prod) we
have 2 Debian 6 squeeze with Ganeti 2.1, which we in turn upgraded to
Debian 7 and Ganeti 2.9 from wheezy-backports.
Due to hardware changes on the platform, we have to rebuild each node in
turn. This works perfectly in our test environment (virtualized), with the
node A (master) running a dist-upgraded 7.3, Ganeti 2.9.2, and node B
(slave) is running a freshly installed 7.3, Ganeti 2.9.2. KVM was also
upgraded from 1.1.2 to 1.7 on the A node to match KVM version on node B.
DRBD is version 8.3.13 on A, 8.14 on B.
I simulated the entire rebuild with the above configuration yesterday, and
now we are stuck as replace-disks fails in the manner described above.
On the test setup, replace-disks -s just worked.
On the prod setup, it failed:
OpExecError: Can't find disk/0 on node B: disk not found
Disks seem to be not properly activated. Try running activate-disks on the
instance before using replace-disks.
So I did, it returned:
nodeA:disk/0:/dev/drbd3
Tried replace-disks again with -s:
Wed Jan 29 18:03:17 2014 STEP 2/6 Check peer consistency
Wed Jan 29 18:03:17 2014 - INFO: Checking disk/0 consistency on node A
Failure: command execution error:
Node A has degraded storage, unsafe to replace disks for instance
instancename
Per the report above I tried with '-a':
Wed Jan 29 18:02:43 2014 - INFO: Checking disk/0 on B
Wed Jan 29 18:02:43 2014 - INFO: Checking disk/0 on A
Wed Jan 29 18:02:44 2014 No disks need replacement for
instance 'instancename'
But clearly the disks are NOT in sync.
Any suggestions at this point ?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
