yahoo-eng-team team mailing list archive

[Jason Hobbs <jason.hobbs@xxxxxxxxxxxxx>]

Public bug reported:

Description
===========
Using python-novaclient, I call nova.servers.create() and then poll with nova.servers.get() until my new instance has a private IP assigned. Occasionally the client raises an error instead:

ConnectionError: ('Connection aborted.', BadStatusLine("''",))

I don't see any indication in the nova cloud controller logs as to what
the failure may be.


Steps to reproduce
==================
* I used nova.servers.create() to create a server
* I used nova.servers.get() to check if the new server was ready to use.
* nova.servers.get() failed with an error:
ConnectionError: ('Connection aborted.', BadStatusLine("''",))

Expected result
===============
I expected the server to come up in ACTIVE state and have a private IP assigned.

Actual result
=============
The nova client throw a connection error.

Environment
===========
I'm running nova on newton:

ii  nova-api-os-compute              2:14.0.1-0ubuntu1~cloud0           all          OpenStack Compute - OpenStack Compute API frontend
ii  nova-cert                        2:14.0.1-0ubuntu1~cloud0           all          OpenStack Compute - certificate management
ii  nova-common                      2:14.0.1-0ubuntu1~cloud0           all          OpenStack Compute - common files
ii  nova-conductor                   2:14.0.1-0ubuntu1~cloud0           all          OpenStack Compute - conductor service
ii  nova-scheduler                   2:14.0.1-0ubuntu1~cloud0           all          OpenStack Compute - virtual machine scheduler
ii  python-nova                      2:14.0.1-0ubuntu1~cloud0           all          OpenStack Compute Python libraries

2. Which hypervisor did you use?
libvirt + kvm
ii  libvirt-bin                          1.3.1-1ubuntu10.6                   amd64        programs for the libvirt library
ii  libvirt0:amd64                       1.3.1-1ubuntu10.6                   amd64        library for interfacing with different virtualization systems
ii  nova-compute-libvirt                 2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node libvirt support
ii  python-libvirt                       1.3.1-1ubuntu1                      amd64        libvirt Python bindings


2. Which storage type did you use?
ceph, but with no attached volumes - not really using it here.

3. Which networking type did you use?
neutron with openvswitch

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: oil oil-guestos-fail

** Attachment added: "sosreport-juju-e54bcf-1-lxd-1-20170131160047.tar.xz"
   https://bugs.launchpad.net/bugs/1660670/+attachment/4811425/+files/sosreport-juju-e54bcf-1-lxd-1-20170131160047.tar.xz

-- 
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/1660670

Title:
  ConnectionError: ('Connection aborted.', BadStatusLine("''",))

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  Using python-novaclient, I call nova.servers.create() and then poll with nova.servers.get() until my new instance has a private IP assigned. Occasionally the client raises an error instead:

  ConnectionError: ('Connection aborted.', BadStatusLine("''",))

  I don't see any indication in the nova cloud controller logs as to
  what the failure may be.


  Steps to reproduce
  ==================
  * I used nova.servers.create() to create a server
  * I used nova.servers.get() to check if the new server was ready to use.
  * nova.servers.get() failed with an error:
  ConnectionError: ('Connection aborted.', BadStatusLine("''",))

  Expected result
  ===============
  I expected the server to come up in ACTIVE state and have a private IP assigned.

  Actual result
  =============
  The nova client throw a connection error.

  Environment
  ===========
  I'm running nova on newton:

  ii  nova-api-os-compute              2:14.0.1-0ubuntu1~cloud0           all          OpenStack Compute - OpenStack Compute API frontend
  ii  nova-cert                        2:14.0.1-0ubuntu1~cloud0           all          OpenStack Compute - certificate management
  ii  nova-common                      2:14.0.1-0ubuntu1~cloud0           all          OpenStack Compute - common files
  ii  nova-conductor                   2:14.0.1-0ubuntu1~cloud0           all          OpenStack Compute - conductor service
  ii  nova-scheduler                   2:14.0.1-0ubuntu1~cloud0           all          OpenStack Compute - virtual machine scheduler
  ii  python-nova                      2:14.0.1-0ubuntu1~cloud0           all          OpenStack Compute Python libraries

  2. Which hypervisor did you use?
  libvirt + kvm
  ii  libvirt-bin                          1.3.1-1ubuntu10.6                   amd64        programs for the libvirt library
  ii  libvirt0:amd64                       1.3.1-1ubuntu10.6                   amd64        library for interfacing with different virtualization systems
  ii  nova-compute-libvirt                 2:14.0.1-0ubuntu1~cloud0            all          OpenStack Compute - compute node libvirt support
  ii  python-libvirt                       1.3.1-1ubuntu1                      amd64        libvirt Python bindings

  
  2. Which storage type did you use?
  ceph, but with no attached volumes - not really using it here.

  3. Which networking type did you use?
  neutron with openvswitch

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