[Bug 1439645] Re: nova can't schedule instance with libvirt-xen driver

[Launchpad Bug Tracker]

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439645

Title:
  nova can't schedule instance  with libvirt-xen driver

Status in OpenStack Compute (nova):
  Expired
Status in nova package in Ubuntu:
  Expired

Bug description:
  This issue is closely related to bug
  https://bugs.launchpad.net/nova/+bug/1425115.

  Applying patch 
  $ git fetch https://review.openstack.org/openstack/nova refs/changes/06/159106/5 && git checkout FETCH_HEAD
  in /opt/stack/nova

  I was able to shutdown and restart system via ./rejoin-stack.sh with
  nova-compute up and running

  ubuntu at ubuntu-wks:~/devstack$ nova service-list
  +----+------------------+------------+----------+---------+-------+----------------------------+-----------------+
  | Id | Binary           | Host       | Zone     | Status  | State | Updated_at                 | Disabled Reason |
  +----+------------------+------------+----------+---------+-------+----------------------------+-----------------+-------------------------
  | 1  | nova-conductor    | ubuntu-wks | internal | enabled | up    | 2015-04-02T11:06:02.000000 | -               |
  | 2  | nova-cert               | ubuntu-wks | internal | enabled | up    | 2015-04-02T11:06:02.000000 | -               |
  | 3  | nova-scheduler     | ubuntu-wks | internal | enabled | up    | 2015-04-02T11:06:02.000000 | -               |
  | 4  | nova-consoleauth | ubuntu-wks | internal | enabled | up    | 2015-04-02T11:06:02.000000 | -               |
  | 5  | nova-compute       | ubuntu-wks | nova     | enabled | up    | 2015-04-02T11:06:02.000000 | -               |
  +----+------------------+------------+----------+---------+-------+----------------------------+----------------------------------------------

  However, attempt to launch instance fails, n-sch.log reports :-

  2015-04-02 06:16:51.248 ^[[00;36mINFO nova.filters
  [^[[00;36m-^[[00;36m] ^[[01;35m^[[00;36mFilter RetryFilter returned 0
  hosts^[[00m^M

  My local.conf

  [[local|localrc]]
  HOST_IP=192.168.1.50
  ADMIN_PASSWORD=secret
  DATABASE_PASSWORD=$ADMIN_PASSWORD
  RABBIT_PASSWORD=$ADMIN_PASSWORD
  SERVICE_PASSWORD=$ADMIN_PASSWORD
  SERVICE_TOKEN=a682f596-76f3-11e3-b3b2-e716f9080d50

  FLOATING_RANGE=192.168.10.0/24
  FLAT_INTERFACE=eth0
  Q_FLOATING_ALLOCATION_POOL=start=192.168.10.150,end=192.168.10.254
  PUBLIC_NETWORK_GATEWAY=192.168.10.15

  # Useful logging options for debugging:
  DEST=/opt/stack
  LOGFILE=$DEST/logs/stack.sh.log
  SCREEN_LOGDIR=$DEST/logs/screen

  # The default fixed range (10.0.0.0/24) conflicted with an address
  # range I was using locally.
  FIXED_RANGE=10.254.1.0/24
  NETWORK_GATEWAY=10.254.1.1

  # Services
  disable_service n-net
  enable_service q-svc
  enable_service q-agt
  enable_service q-dhcp
  enable_service q-l3
  enable_service q-meta
  enable_service horizon
  disable_service tempest

  # This is a Xen Project host:
  LIBVIRT_TYPE=xen

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