yahoo-eng-team team mailing list archive

[Kim-Norman Sahm <1682423@xxxxxxxxxxxxxxxxxx>]

I've tried Bernards workaround and it's working.

--- api.py	2017-10-10 14:40:14.384511170 +0200
+++ api.py.patched	2017-10-10 14:40:46.192451521 +0200
@@ -83,6 +83,7 @@
 from nova import utils
 from nova.virt import hardware
 from nova.volume import cinder
+from time import sleep
 
 LOG = logging.getLogger(__name__)
 
@@ -2354,6 +2355,7 @@
         expected_attrs.extend(['metadata', 'system_metadata',
                                'security_groups', 'info_cache'])
         # NOTE(ameade): we still need to support integer ids for ec2
+        sleep(1.0)
         try:
             if uuidutils.is_uuid_like(instance_id):
                 LOG.debug("Fetching instance by UUID",


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

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

Title:
  create instance with dashbaord / 404 returned

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Description
  ===========
  When launching an instance over  dashboard, a 404 code is returned (  Instance XX-XX-XX could not be found ).
  Same issue occurs when you make it through nova client, but it has no effect.
  In both tasks the instance is created.
  You can see a "HTTP exception thrown:" in the nova-api logfile.

  
  Steps to reproduce
  ==================
  A chronological list of steps which will bring off the
  issue you noticed:
  * upgraded all nodes to CentoS 7.3
  * no issues
  * upgraded from newton to ocata (RDO) 
  * 404 issue

  
  * launching an instance through dashboard.
  The instance has been added but a 404 returned.
  So an error is displayed in dashboard interface (see create_instance_error.png)

  For testing purposes i used curl.
  see output.txt

  
  * launching an instance using nova client
  Same error occurs but it has no effect.

  see output.txt

  
  Expected result
  ===============
  A new instance launched and the wizard should be closed.

  Actual result
  =============
  I get an 404 Code and the "instance wizard" is still open although the instances was created and is running.

  Environment
  ===========
  openstack-nova-console-15.0.0-1.el7
  python-nova-15.0.0-1.el7
  openstack-nova-placement-api-15.0.0-1.el7
  python2-novaclient-7.1.0-1.el7
  openstack-nova-scheduler-15.0.0-1.el7
  openstack-nova-conductor-15.0.0-1.el7
  openstack-nova-novncproxy-15.0.0-1.el7
  openstack-nova-api-15.0.0-1.el7
  openstack-nova-common-15.0.0-1.el7
  openstack-nova-cert-15.0.0-1.el7
  openstack-dashboard-11.0.0-1.el7
  python-networking-bgpvpn-dashboard-6.0.0-0.1.681a5e7git.el7

  
  Logs & Configs
  ==============
  see nova-api-logs.txt

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