vmbuilder team mailing list archive

[Robert Riches <963352@xxxxxxxxxxxxxxxxxx>]

Private bug reported:

Chassis build 35208 with manzanita-20120321-1, cluster appears to
silently ignore attempts to temporarily migrate two of the VMs.

The original condition was VMs rmr211, rmr212, and rmr213 running on
blade 1; VMs rmr221, rmr222, and rmr223 running on blade 2.  I temp-
migrated all three VMs from blade 2 to blade 1, and that was successful.
Then, I attempted to temp-migrate rmr211, then rmr212, then rmr213 from
blade 1 to blade 2.  The UI reported that all three migrations had been
successfully started.  However, only the last one, rmr213, migrated.
DevLog shows the CRM resource migrate ... command issued for all three
VMs.  EventLog shows RA_... events from the cluster for rmr213 but
nothing for rmr211 and rmr212.  Diags were captured after the first
attempt to migrate each VM once.

Each VM has 0.6 (reported as 0.56) GB of memory.  There is enough memory
on blade 2 to run three, as evidenced by the original state with three
VMs running on it.

Subsequent attempts to temp-migrate rmr211 and rmr212 via the UI and
then via the HV shell appear to have been silently ignored.

** Affects: manzanita
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of
VMBuilder, which is subscribed to The Manzanita Project.
https://bugs.launchpad.net/bugs/963352

Title:
  cluster silently ignores VM temp migration attempt

Status in The Manzanita Project:
  New

Bug description:
  Chassis build 35208 with manzanita-20120321-1, cluster appears to
  silently ignore attempts to temporarily migrate two of the VMs.

  The original condition was VMs rmr211, rmr212, and rmr213 running on
  blade 1; VMs rmr221, rmr222, and rmr223 running on blade 2.  I temp-
  migrated all three VMs from blade 2 to blade 1, and that was
  successful.  Then, I attempted to temp-migrate rmr211, then rmr212,
  then rmr213 from blade 1 to blade 2.  The UI reported that all three
  migrations had been successfully started.  However, only the last one,
  rmr213, migrated.  DevLog shows the CRM resource migrate ... command
  issued for all three VMs.  EventLog shows RA_... events from the
  cluster for rmr213 but nothing for rmr211 and rmr212.  Diags were
  captured after the first attempt to migrate each VM once.

  Each VM has 0.6 (reported as 0.56) GB of memory.  There is enough
  memory on blade 2 to run three, as evidenced by the original state
  with three VMs running on it.

  Subsequent attempts to temp-migrate rmr211 and rmr212 via the UI and
  then via the HV shell appear to have been silently ignored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/manzanita/+bug/963352/+subscriptions