[Yahoo-eng-team] [Bug 1403921] Re: allow_automatic_l3agent_failover fails if neutron-server goes down as well
[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1403921 Title: allow_automatic_l3agent_failover fails if neutron-server goes down as well Status in OpenStack Neutron (virtual network service): Expired Bug description: when working with a topology with multiple, balanced, neutron-server nodes, the neutron l3 agent failover facility (allow_automatic_l3agent_failover) works as expected if the cluster is stable (aka, the agent dies but server remains stable) it does not instead when the entire node is brought down and the server it was connected to initially becomes unavailable, the remaining server nodes will recognize agent is died, but relocation of routers never happens To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1403921/+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 1424277] [NEW] Running without arguments results in Exception on Python 3
Public bug reported: I'm trying to run the current trunk on Python 3. When I run cloud-init with no arguments, I get the following exception. $ python3 bin/cloud-init Traceback (most recent call last): File "bin/cloud-init", line 623, in sys.exit(main()) File "bin/cloud-init", line 614, in main (name, functor) = args.action AttributeError: 'Namespace' object has no attribute 'action' This is caused by a change of behavior of argparse on Python 3 when using subparsers. Can be workarounded by adding try-catch similar to this one: try: (name, functor) = args.action except AttributeError: parser.print_help() return 0 (Consider it public domain, as it is so simple) ** Affects: cloud-init Importance: Undecided Status: New ** Description changed: I'm trying to run the current trunk on Python 3. When I run cloud-init with no arguments, I get the following exception. - $ python3 bin/cloud-init - Traceback (most recent call last): - File "bin/cloud-init", line 623, in - sys.exit(main()) - File "bin/cloud-init", line 614, in main - (name, functor) = args.action - AttributeError: 'Namespace' object has no attribute 'action' + $ python3 bin/cloud-init + Traceback (most recent call last): + File "bin/cloud-init", line 623, in + sys.exit(main()) + File "bin/cloud-init", line 614, in main + (name, functor) = args.action + AttributeError: 'Namespace' object has no attribute 'action' This is caused by a chenge of behavior of argparse on Python 3 when using subparsers. - Can we workarounded by adding try-catch similar to this one: + Can be workarounded by adding try-catch similar to this one: - try: - (name, functor) = args.action - except AttributeError: - parser.print_help() - return 0 + try: + (name, functor) = args.action + except AttributeError: + parser.print_help() + return 0 (Consider it public domain, as it is so simple) ** Description changed: I'm trying to run the current trunk on Python 3. When I run cloud-init with no arguments, I get the following exception. $ python3 bin/cloud-init Traceback (most recent call last): File "bin/cloud-init", line 623, in sys.exit(main()) File "bin/cloud-init", line 614, in main (name, functor) = args.action AttributeError: 'Namespace' object has no attribute 'action' - This is caused by a chenge of behavior of argparse on Python 3 when + This is caused by a change of behavior of argparse on Python 3 when using subparsers. Can be workarounded by adding try-catch similar to this one: try: (name, functor) = args.action except AttributeError: parser.print_help() return 0 (Consider it public domain, as it is so simple) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1424277 Title: Running without arguments results in Exception on Python 3 Status in Init scripts for use on cloud images: New Bug description: I'm trying to run the current trunk on Python 3. When I run cloud-init with no arguments, I get the following exception. $ python3 bin/cloud-init Traceback (most recent call last): File "bin/cloud-init", line 623, in sys.exit(main()) File "bin/cloud-init", line 614, in main (name, functor) = args.action AttributeError: 'Namespace' object has no attribute 'action' This is caused by a change of behavior of argparse on Python 3 when using subparsers. Can be workarounded by adding try-catch similar to this one: try: (name, functor) = args.action except AttributeError: parser.print_help() return 0 (Consider it public domain, as it is so simple) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1424277/+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 1424269] [NEW] No [database] section on nova.conf
Public bug reported: While following the http://docs.openstack.org/juno/install- guide/install/yum/content/ch_nova.html documentation, on the step to populate the Database I've faced an error with DB access. After verifying again, I've realized that the following area didn't even exist on nova.conf file (even commented out): "[database] ... connection = mysql://nova:NOVA_DBPASS@controller/nova" This is strange, because on "To install and configure Compute controller components" section / item 2, they say to edit the '[database]' section, but this section doesn't exist on nova.conf file. So, what's wrong? The documentation that should say to 'add' a section called 'database' on nova.conf file, or the 'nova.conf' file that does not contain this section with the example config directives? Thanks ** Affects: nova Importance: Undecided Status: New ** Tags: centos7 nova yum -- 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/1424269 Title: No [database] section on nova.conf Status in OpenStack Compute (Nova): New Bug description: While following the http://docs.openstack.org/juno/install- guide/install/yum/content/ch_nova.html documentation, on the step to populate the Database I've faced an error with DB access. After verifying again, I've realized that the following area didn't even exist on nova.conf file (even commented out): "[database] ... connection = mysql://nova:NOVA_DBPASS@controller/nova" This is strange, because on "To install and configure Compute controller components" section / item 2, they say to edit the '[database]' section, but this section doesn't exist on nova.conf file. So, what's wrong? The documentation that should say to 'add' a section called 'database' on nova.conf file, or the 'nova.conf' file that does not contain this section with the example config directives? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1424269/+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 1424244] [NEW] Go button of the instance log page becomes disable
Public bug reported: Steps to reproduce. 1. Spin up an instance. 2. Once the instance is up, click the View Log action. 3. On the view log page, enter some valid value on the Log Length text box. 4. Click "Go" button 5. Once the page is refreshed, you will notice that the Go button become disable forever. Test it on Chrome broswer. ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Changed in: horizon Assignee: (unassigned) => Kahou Lei (kahou82) ** Description changed: Steps to reproduce. 1. Spin up an instance. 2. Once the instance is up, click the View Log action. 3. On the view log page, enter some valid value on the Log Length text box. 4. Click "Go" button 5. Once the page is refreshed, you will notice that the Go button become disable forever. + + Test it on Chrome broswer. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1424244 Title: Go button of the instance log page becomes disable Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce. 1. Spin up an instance. 2. Once the instance is up, click the View Log action. 3. On the view log page, enter some valid value on the Log Length text box. 4. Click "Go" button 5. Once the page is refreshed, you will notice that the Go button become disable forever. Test it on Chrome broswer. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1424244/+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 1415336] Re: type: parameter should be replaced by healthmonitor_type in loadbalancer
The page you've linked to in this bug report is no longer updated. Can you review https://review.openstack.org/#/c/148687/ to see if this has been addressed in the updated documentation? ** Also affects: openstack-api-site Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1415336 Title: type: parameter should be replaced by healthmonitor_type in loadbalancer Status in OpenStack Neutron (virtual network service): New Status in OpenStack API documentation site: New Status in Python client library for Neutron: New Bug description: As per V2 API specification load balancer healthmonitor has a parameter "type" which can not be parsed by JSON parser. So, it must be replaced by "healthmonitor_type" as per the OpenDayLight Bug- ( https://bugs.opendaylight.org/show_bug.cgi?id=1674 ) Further information related to lbaas healthmonitor can be found here: http://docs.openstack.org/api/openstack-network/2.0/content/POST_createHealthMonitor__v2.0_healthmonitors_lbaas_ext_ops_health_monitor.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1415336/+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 1423250] Re: Terminating neutron-server leads to waitall() inside a GreenPool's greenthread
This confirms it's happening in the community code for keystone and
neutron, but apparently it's not fatal:
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiIEFzc2VydGlvbkVycm9yOiBDYWxsaW5nIHdhaXRhbGwoKSBmcm9tIHdpdGhpbiBvbmUgb2YgdGhlIEdyZWVuUG9vbCdzIGdyZWVudGhyZWFkcyB3aWxsIG5ldmVyIHRlcm1pbmF0ZS5cIiBBTkQgdGFnczpcImNvbnNvbGVcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQyNDUzMzY5NDMzMCwibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIifQ==
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => 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/1423250
Title:
Terminating neutron-server leads to waitall() inside a GreenPool's
greenthread
Status in OpenStack Identity (Keystone):
Confirmed
Status in OpenStack Neutron (virtual network service):
In Progress
Bug description:
Sending a termination signal (e.g. SIGHUP or SIGTERM) to neutron
server with more that one api/rpc worker leads to the following
traceback:
2015-02-18 16:05:18.411 CRITICAL neutron [-] AssertionError: Calling
waitall() from within one of the GreenPool's greenthreads will never
terminate.
2015-02-18 16:05:18.411 TRACE neutron Traceback (most recent call last):
2015-02-18 16:05:18.411 TRACE neutron File "/usr/local/bin/neutron-server",
line 9, in
2015-02-18 16:05:18.411 TRACE neutron
load_entry_point('neutron==2015.1.dev117', 'console_scripts',
'neutron-server')()
2015-02-18 16:05:18.411 TRACE neutron File
"/opt/stack/neutron/neutron/server/__init__.py", line 46, in main
2015-02-18 16:05:18.411 TRACE neutron neutron_api =
service.serve_wsgi(service.NeutronApiService)
2015-02-18 16:05:18.411 TRACE neutron File
"/opt/stack/neutron/neutron/service.py", line 106, in serve_wsgi
2015-02-18 16:05:18.411 TRACE neutron LOG.exception(_LE('Unrecoverable
error: please check log '
2015-02-18 16:05:18.411 TRACE neutron File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 82, in
__exit__
2015-02-18 16:05:18.411 TRACE neutron six.reraise(self.type_, self.value,
self.tb)
2015-02-18 16:05:18.411 TRACE neutron File
"/opt/stack/neutron/neutron/service.py", line 103, in serve_wsgi
2015-02-18 16:05:18.411 TRACE neutron service.start()
2015-02-18 16:05:18.411 TRACE neutron File
"/opt/stack/neutron/neutron/service.py", line 74, in start
2015-02-18 16:05:18.411 TRACE neutron self.wsgi_app =
_run_wsgi(self.app_name)
2015-02-18 16:05:18.411 TRACE neutron File
"/opt/stack/neutron/neutron/service.py", line 175, in _run_wsgi
2015-02-18 16:05:18.411 TRACE neutron workers=cfg.CONF.api_workers)
2015-02-18 16:05:18.411 TRACE neutron File
"/opt/stack/neutron/neutron/wsgi.py", line 224, in start
2015-02-18 16:05:18.411 TRACE neutron self._launch(application, workers)
2015-02-18 16:05:18.411 TRACE neutron File
"/opt/stack/neutron/neutron/wsgi.py", line 238, in _launch
2015-02-18 16:05:18.411 TRACE neutron
self._server.launch_service(service, workers=workers)
2015-02-18 16:05:18.411 TRACE neutron File
"/opt/stack/neutron/neutron/openstack/common/service.py", line 333, in
launch_service
2015-02-18 16:05:18.411 TRACE neutron self._start_child(wrap)
2015-02-18 16:05:18.411 TRACE neutron File
"/opt/stack/neutron/neutron/openstack/common/service.py", line 314, in
_start_child
2015-02-18 16:05:18.411 TRACE neutron status, signo =
self._child_wait_for_exit_or_signal(launcher)
2015-02-18 16:05:18.411 TRACE neutron File
"/opt/stack/neutron/neutron/openstack/common/service.py", line 272, in
_child_wait_for_exit_or_signal
2015-02-18 16:05:18.411 TRACE neutron launcher.stop()
2015-02-18 16:05:18.411 TRACE neutron File
"/opt/stack/neutron/neutron/openstack/common/service.py", line 126, in stop
2015-02-18 16:05:18.411 TRACE neutron self.services.stop()
2015-02-18 16:05:18.411 TRACE neutron File
"/opt/stack/neutron/neutron/openstack/common/service.py", line 462, in stop
2015-02-18 16:05:18.411 TRACE neutron service.stop()
2015-02-18 16:05:18.411 TRACE neutron File
"/opt/stack/neutron/neutron/wsgi.py", line 117, in stop
2015-02-18 16:05:18.411 TRACE neutron self._server.kill()
2015-02-18 16:05:18.411 TRACE neutron File
"/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 240, in
kill
2015-02-18 16:05:18.411 TRACE neutron return kill(self, *throw_args)
2015-02-18 16:05:18.411 TRACE neutron File
"/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 294, in
kill
2015-02-18 16:05:18.411 TRACE neutron g.throw(*throw_args)
2015-02-18 16:05:18.411 TRACE neutron File
"/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 214, in
main
2015
