yahoo-eng-team team mailing list archive

[Pawel Koniszewski <pawel.koniszewski@xxxxxxxxx>]

So it is packstack related issue - please refer to
https://bugzilla.redhat.com/show_bug.cgi?id=968310

** Bug watch added: Red Hat Bugzilla #968310
   https://bugzilla.redhat.com/show_bug.cgi?id=968310

** Changed in: nova
       Status: Confirmed => Invalid

** Changed in: nova
     Assignee: lvmxh (shaohef) => (unassigned)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1428553

Title:
  migration and live migration fails with images_type=rbd

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description of problem:
  The migration and live migration of instances fail when Nova is set to work with RBD as a back end for the instances disks. 
  When attempting to migrate an instance from one host to another an error prompt:

  Error: Failed to launch instance "osp5": Please try again later
  [Error: Unexpected error while running command. Command: ssh <host
  address> mkdir -p /var/lib/nova/instances/98cc014a-0d6d-48bc-
  9d76-4fe361b67f3b Exit code: 1 Stdout: u'This account is currently not
  available.\n' Stderr: u''].

  The log show: http://pastebin.test.redhat.com/267337

  when attempting to run live migration this is the output:
  http://pastebin.test.redhat.com/267340

  There's a work around, to change the nova user settings on all the
  compute nodes, on the /etc/passwd file from sbin/nologin to bin/bash
  and run the command. I wouldn't recommend it, it creates a security
  breach IMO.

  Version-Release number of selected component (if applicable):
  openstack-nova-api-2014.2.2-2.el7ost.noarch
  python-nova-2014.2.2-2.el7ost.noarch
  openstack-nova-compute-2014.2.2-2.el7ost.noarch
  openstack-nova-common-2014.2.2-2.el7ost.noarch
  openstack-nova-scheduler-2014.2.2-2.el7ost.noarch
  python-novaclient-2.20.0-1.el7ost.noarch
  openstack-nova-conductor-2014.2.2-2.el7ost.noarch

  How reproducible:
  100%

  Steps to Reproduce:
  1. Set the nova to work with RBD as the back end of the instances disks, according to the Ceph documentation
  2. Launch an instance
  3. migrate the instance to a different host 

  Actual results:
  The migration fails and the instance status moves to error.

  Expected results:
  the instance migrates to the other host

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