[Yahoo-eng-team] [Bug 1642419] Re: GPU Passthrough isn't working
** Changed in: kolla-ansible Status: Confirmed => Invalid -- 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/1642419 Title: GPU Passthrough isn't working Status in kolla-ansible: Invalid Status in OpenStack Compute (nova): New Bug description: Hi, I cannot get IOMMU working on my Openstack cloud. Everytime I launch an instance with one gpu I get this error complaining that host doesn't have the requested feature. Message Exceeded maximum number of retries. Exceeded max scheduling attempts 10 for instance 769a2108-9a53-4cf5-9055-82411ce5cafd. Last exception: internal error: process exited while connecting to monitor: warning: host doesn't support requested feature: CPUID.0 Code 500 Details File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/conductor/manager.py", line 480, in build_instances filter_properties, instances[0].uuid) File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/nova/scheduler/utils.py", line 184, in populate_retry raise exception.MaxRetriesExceeded(reason=msg) Here is the log from nova-compute: http://paste.openstack.org/show/589527/ And here is a log from nova-scheduler: http://paste.openstack.org/show/589528/ I'm running Openstack Kolla v3.0.1 on an i7 4790k. My GPU is Nvidia GTX 970 (that I want to passthrough) and my motherboard is Maximus VI Extreme. IOMMU has worked on this setup in the past on Arch Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/kolla-ansible/+bug/1642419/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1563029] Re: Nova instance fail to launch: "Unexpected API Error."
** Changed in: kolla Status: Won't Fix => Incomplete ** No longer affects: kolla/mitaka -- 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/1563029 Title: Nova instance fail to launch: "Unexpected API Error." Status in kolla: Incomplete Status in OpenStack Compute (nova): Invalid Bug description: This is a Kolla installation of openstack. The docker images build well and some services work great; e.g cinder, glance and neutron. Nova seems to have a problem that is prevent provisioning instances. The manila-api logs below says: "Returning 500 to user: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. __call__ /usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py:1070" 1. The GIT commit level is: lsorrillo@ptest:~/git/kolla$ git log -1 commit 90321d0497f14bda370908610cfc44296a940523 Merge: 328a7e8 a789346 Author: JenkinsDate: Sun Mar 27 23:42:47 2016 + Merge "Fix gate to use world writeable docker socket" lsorrillo@ptest:~/git/kolla$ RPM version: lsorrillo@ptest:~$ lsorrillo@ptest:~$ docker exec -ti nova_api bash bash-4.2$ bash-4.2$ bash-4.2$ bash-4.2$ rpm -qa | grep nova python-novaclient-3.3.1-0.20160303082753.d63800d.el7.centos.noarch openstack-nova-common-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch python-nova-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch openstack-nova-api-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch bash-4.2$ 2. The following error is seen in the nova-api.log: 2016-03-28 19:53:40.086 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connecting to AMQP server on 192.168.0.121:5672 __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:535 2016-03-28 19:53:40.132 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connected to AMQP server on 192.168.0.121:5672 via [amqp] client __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:562 2016-03-28 19:53:40.148 29 DEBUG oslo.messaging._drivers.pool [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Pool creating new connection create /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/pool.py:109 2016-03-28 19:53:40.151 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connecting to AMQP server on 192.168.0.121:5672 __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:535 2016-03-28 19:53:40.205 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connected to AMQP server on 192.168.0.121:5672 via [amqp] client __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:562 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Unexpected exception in API method 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 478, in wrapped 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return f(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in wrapper 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in wrapper 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in wrapper 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 630, in create 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions **create_kwargs) 2016-03-28
[Yahoo-eng-team] [Bug 1568202] Re: linux bridge agent gets out of sync with plugin
** No longer affects: kolla/mitaka ** No longer affects: kolla/liberty -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1568202 Title: linux bridge agent gets out of sync with plugin Status in kolla: Triaged Status in neutron: Invalid Bug description: I am using ml2 plugin with linux bridge which 3 control 3 network and 51 compute nodes. while spinning 500 to 1000 vms sometimes the success rate of getting vms active is 60% 2 out of 6 time 500 or 1000 vms were getting active when being spun. logs here http://paste.openstack.org/show/493553/ To manage notifications about this bug go to: https://bugs.launchpad.net/kolla/+bug/1568202/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1568202] Re: linux bridge agent gets out of sync with plugin
** Also affects: kolla/liberty Importance: Undecided Status: New ** Changed in: kolla/liberty Status: New => Triaged ** Changed in: kolla/liberty Milestone: None => 1.1.2 ** Changed in: kolla/mitaka Milestone: 2.0.1 => 2.0.2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1568202 Title: linux bridge agent gets out of sync with plugin Status in kolla: Triaged Status in kolla liberty series: Triaged Status in kolla mitaka series: Triaged Status in neutron: Invalid Bug description: I am using ml2 plugin with linux bridge which 3 control 3 network and 51 compute nodes. while spinning 500 to 1000 vms sometimes the success rate of getting vms active is 60% 2 out of 6 time 500 or 1000 vms were getting active when being spun. logs here http://paste.openstack.org/show/493553/ To manage notifications about this bug go to: https://bugs.launchpad.net/kolla/+bug/1568202/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1568202] Re: linux bridge agent gets out of sync with plugin
** This bug is no longer a duplicate of bug 1567406 neutron linux bridge agent is buggy and can not boot instance ** Changed in: kolla Milestone: None => newton-1 ** Also affects: kolla/mitaka Importance: Undecided Status: New ** Changed in: kolla Status: New => Triaged ** Changed in: kolla/mitaka Status: New => Triaged ** Changed in: kolla Importance: Undecided => Critical ** Changed in: kolla/mitaka Importance: Undecided => Critical ** Changed in: kolla/mitaka Milestone: None => 2.0.0 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1568202 Title: linux bridge agent gets out of sync with plugin Status in kolla: Triaged Status in kolla mitaka series: Triaged Status in neutron: New Bug description: I am using ml2 plugin with linux bridge which 3 control 3 network and 51 compute nodes. while spinning 500 to 1000 vms sometimes the success rate of getting vms active is 60% 2 out of 6 time 500 or 1000 vms were getting active when being spun. logs here http://paste.openstack.org/show/493553/ To manage notifications about this bug go to: https://bugs.launchpad.net/kolla/+bug/1568202/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1563029] Re: Nova instance fail to launch: "Unexpected API Error."
The nova issue here is the conductor retries of 3 is too small for medium scale (64 node) clusters. While I realize its configurable, my expectation is OpenStack services work out of the box at 100 node scale under overload conditions. ** Changed in: kolla/mitaka Milestone: mitaka-rc3 => 2.0.0 ** Changed in: nova Status: Invalid => Confirmed ** Changed in: kolla Status: Triaged => Confirmed ** Changed in: kolla/mitaka Status: Triaged => 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/1563029 Title: Nova instance fail to launch: "Unexpected API Error." Status in kolla: Confirmed Status in kolla mitaka series: Confirmed Status in OpenStack Compute (nova): Incomplete Bug description: This is a Kolla installation of openstack. The docker images build well and some services work great; e.g cinder, glance and neutron. Nova seems to have a problem that is prevent provisioning instances. The manila-api logs below says: "Returning 500 to user: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. __call__ /usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py:1070" 1. The GIT commit level is: lsorrillo@ptest:~/git/kolla$ git log -1 commit 90321d0497f14bda370908610cfc44296a940523 Merge: 328a7e8 a789346 Author: JenkinsDate: Sun Mar 27 23:42:47 2016 + Merge "Fix gate to use world writeable docker socket" lsorrillo@ptest:~/git/kolla$ RPM version: lsorrillo@ptest:~$ lsorrillo@ptest:~$ docker exec -ti nova_api bash bash-4.2$ bash-4.2$ bash-4.2$ bash-4.2$ rpm -qa | grep nova python-novaclient-3.3.1-0.20160303082753.d63800d.el7.centos.noarch openstack-nova-common-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch python-nova-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch openstack-nova-api-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch bash-4.2$ 2. The following error is seen in the nova-api.log: 2016-03-28 19:53:40.086 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connecting to AMQP server on 192.168.0.121:5672 __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:535 2016-03-28 19:53:40.132 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connected to AMQP server on 192.168.0.121:5672 via [amqp] client __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:562 2016-03-28 19:53:40.148 29 DEBUG oslo.messaging._drivers.pool [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Pool creating new connection create /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/pool.py:109 2016-03-28 19:53:40.151 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connecting to AMQP server on 192.168.0.121:5672 __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:535 2016-03-28 19:53:40.205 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connected to AMQP server on 192.168.0.121:5672 via [amqp] client __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:562 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Unexpected exception in API method 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 478, in wrapped 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return f(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in wrapper 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in wrapper 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File
[Yahoo-eng-team] [Bug 1563029] Re: Nova instance fail to launch: "Unexpected API Error."
nm comment #4, i was thinking of a different bug. ** Changed in: nova Status: Confirmed => Invalid ** Changed in: nova Status: Invalid => Incomplete -- 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/1563029 Title: Nova instance fail to launch: "Unexpected API Error." Status in kolla: Confirmed Status in kolla mitaka series: Confirmed Status in OpenStack Compute (nova): Incomplete Bug description: This is a Kolla installation of openstack. The docker images build well and some services work great; e.g cinder, glance and neutron. Nova seems to have a problem that is prevent provisioning instances. The manila-api logs below says: "Returning 500 to user: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. __call__ /usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py:1070" 1. The GIT commit level is: lsorrillo@ptest:~/git/kolla$ git log -1 commit 90321d0497f14bda370908610cfc44296a940523 Merge: 328a7e8 a789346 Author: JenkinsDate: Sun Mar 27 23:42:47 2016 + Merge "Fix gate to use world writeable docker socket" lsorrillo@ptest:~/git/kolla$ RPM version: lsorrillo@ptest:~$ lsorrillo@ptest:~$ docker exec -ti nova_api bash bash-4.2$ bash-4.2$ bash-4.2$ bash-4.2$ rpm -qa | grep nova python-novaclient-3.3.1-0.20160303082753.d63800d.el7.centos.noarch openstack-nova-common-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch python-nova-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch openstack-nova-api-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch bash-4.2$ 2. The following error is seen in the nova-api.log: 2016-03-28 19:53:40.086 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connecting to AMQP server on 192.168.0.121:5672 __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:535 2016-03-28 19:53:40.132 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connected to AMQP server on 192.168.0.121:5672 via [amqp] client __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:562 2016-03-28 19:53:40.148 29 DEBUG oslo.messaging._drivers.pool [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Pool creating new connection create /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/pool.py:109 2016-03-28 19:53:40.151 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connecting to AMQP server on 192.168.0.121:5672 __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:535 2016-03-28 19:53:40.205 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connected to AMQP server on 192.168.0.121:5672 via [amqp] client __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:562 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Unexpected exception in API method 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 478, in wrapped 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return f(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in wrapper 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in wrapper 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in wrapper 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line
[Yahoo-eng-team] [Bug 1565105] Re: while spining vms on large scale some vms get multiple ips and multiple ports get created
TimeoutError: QueuePool limit of size 5 overflow 50 reached Perhaps we should try raising the queue pool limit or the amqp pool timeouts for all services for large scale deployments. can you try that? ** Changed in: kolla Importance: Undecided => Critical ** Changed in: kolla Status: New => Incomplete ** Changed in: kolla Milestone: None => newton-1 ** Also affects: kolla/mitaka Importance: Undecided Status: New ** Changed in: kolla/mitaka Milestone: None => 2.0.0 ** Changed in: kolla/mitaka Importance: Undecided => Critical ** Changed in: kolla/mitaka Status: New => Incomplete ** Changed in: kolla Status: Incomplete => Confirmed ** Changed in: kolla/mitaka Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1565105 Title: while spining vms on large scale some vms get multiple ips and multiple ports get created Status in kolla: Confirmed Status in kolla mitaka series: Confirmed Status in neutron: Confirmed Bug description: attached logs from neutron_server not getting any error logs in rabbit mq http://paste.openstack.org/show/492785/ To manage notifications about this bug go to: https://bugs.launchpad.net/kolla/+bug/1565105/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1563029] Re: Nova instance fail to launch: "Unexpected API Error."
** Changed in: kolla Importance: Undecided => High ** Changed in: kolla Status: New => Triaged ** Changed in: kolla Milestone: None => 2.0.0 ** Changed in: kolla Milestone: 2.0.0 => newton-1 ** Also affects: kolla/mitaka Importance: Undecided Status: New ** Changed in: kolla/mitaka Milestone: None => mitaka-rc3 ** Changed in: kolla/mitaka Importance: Undecided => High ** Changed in: kolla/mitaka Status: New => Triaged -- 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/1563029 Title: Nova instance fail to launch: "Unexpected API Error." Status in kolla: Triaged Status in kolla mitaka series: Triaged Status in OpenStack Compute (nova): Invalid Bug description: This is a Kolla installation of openstack. The docker images build well and some services work great; e.g cinder, glance and neutron. Nova seems to have a problem that is prevent provisioning instances. The manila-api logs below says: "Returning 500 to user: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. __call__ /usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py:1070" 1. The GIT commit level is: lsorrillo@ptest:~/git/kolla$ git log -1 commit 90321d0497f14bda370908610cfc44296a940523 Merge: 328a7e8 a789346 Author: JenkinsDate: Sun Mar 27 23:42:47 2016 + Merge "Fix gate to use world writeable docker socket" lsorrillo@ptest:~/git/kolla$ RPM version: lsorrillo@ptest:~$ lsorrillo@ptest:~$ docker exec -ti nova_api bash bash-4.2$ bash-4.2$ bash-4.2$ bash-4.2$ rpm -qa | grep nova python-novaclient-3.3.1-0.20160303082753.d63800d.el7.centos.noarch openstack-nova-common-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch python-nova-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch openstack-nova-api-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch bash-4.2$ 2. The following error is seen in the nova-api.log: 2016-03-28 19:53:40.086 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connecting to AMQP server on 192.168.0.121:5672 __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:535 2016-03-28 19:53:40.132 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connected to AMQP server on 192.168.0.121:5672 via [amqp] client __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:562 2016-03-28 19:53:40.148 29 DEBUG oslo.messaging._drivers.pool [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Pool creating new connection create /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/pool.py:109 2016-03-28 19:53:40.151 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connecting to AMQP server on 192.168.0.121:5672 __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:535 2016-03-28 19:53:40.205 29 DEBUG oslo.messaging._drivers.impl_rabbit [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Connected to AMQP server on 192.168.0.121:5672 via [amqp] client __init__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:562 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions [req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 9e4b40d958e741599adc497b0a9d955a - - -] Unexpected exception in API method 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 478, in wrapped 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return f(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in wrapper 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in wrapper 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions File