[Yahoo-eng-team] [Bug 1486407] Re: devstack install failed, error in keystone requirement.
[Expired for OpenStack Identity (keystone) because there has been no
activity for 60 days.]
** Changed in: keystone
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1486407
Title:
devstack install failed, error in keystone requirement.
Status in OpenStack Identity (keystone):
Expired
Bug description:
download the lastest devstack, and use './stack.sh' to install the OpenStack.
Error happens as follow:
2015-08-19 06:03:51.039 | + is_service_enabled ldap
2015-08-19 06:03:51.050 | + return 1
2015-08-19 06:03:51.050 | + recreate_database keystone
2015-08-19 06:03:51.050 | + local db=keystone
2015-08-19 06:03:51.051 | + recreate_database_mysql keystone
2015-08-19 06:03:51.051 | + local db=keystone
2015-08-19 06:03:51.051 | + mysql -uroot -pstackdb -h127.0.0.1 -e 'DROP
DATABASE IF EXISTS keystone;'
2015-08-19 06:03:51.060 | + mysql -uroot -pstackdb -h127.0.0.1 -e 'CREATE
DATABASE keystone CHARACTER SET utf8;'
2015-08-19 06:03:51.069 | + /usr/local/bin/keystone-manage db_sync
2015-08-19 06:03:51.513 | Traceback (most recent call last):
2015-08-19 06:03:51.513 | File "/usr/local/bin/keystone-manage", line 4, in
2015-08-19 06:03:51.514 |
__import__('pkg_resources').require('keystone==2015.2.0.dev43')
2015-08-19 06:03:51.514 | File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3084,
in
2015-08-19 06:03:51.535 | @_call_aside
2015-08-19 06:03:51.536 | File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3070,
in _call_aside
2015-08-19 06:03:51.537 | f(*args, **kwargs)
2015-08-19 06:03:51.537 | File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3097,
in _initialize_master_working_set
2015-08-19 06:03:51.537 | working_set = WorkingSet._build_master()
2015-08-19 06:03:51.538 | File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 653,
in _build_master
2015-08-19 06:03:51.538 | return
cls._build_from_requirements(__requires__)
2015-08-19 06:03:51.538 | File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 666,
in _build_from_requirements
2015-08-19 06:03:51.539 | dists = ws.resolve(reqs, Environment())
2015-08-19 06:03:51.539 | File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 839,
in resolve
2015-08-19 06:03:51.539 | raise DistributionNotFound(req, requirers)
2015-08-19 06:03:51.540 | pkg_resources.DistributionNotFound: The
'oslo.utils<1.5.0,>=1.4.0' distribution was not found and is required by
keystone
2015-08-19 06:03:51.546 | + exit_trap
2015-08-19 06:03:51.546 | + local r=1
2015-08-19 06:03:51.547 | ++ jobs -p
2015-08-19 06:03:51.548 | + jobs=
2015-08-19 06:03:51.549 | + [[ -n '' ]]
2015-08-19 06:03:51.549 | + kill_spinner
2015-08-19 06:03:51.549 | + '[' '!' -z '' ']'
2015-08-19 06:03:51.549 | + [[ 1 -ne 0 ]]
2015-08-19 06:03:51.550 | + echo 'Error on exit'
2015-08-19 06:03:51.550 | Error on exit
2015-08-19 06:03:51.550 | + [[ -z /opt/stack/logs ]]
2015-08-19 06:03:51.550 | + /opt/stack/devstack/tools/worlddump.py -d
/opt/stack/logs
2015-08-19 06:03:51.950 | + exit 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1486407/+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 1484836] Re: apache failed to restart with keystone wsgi app
[Expired for OpenStack Identity (keystone) because there has been no activity for 60 days.] ** Changed in: keystone Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1484836 Title: apache failed to restart with keystone wsgi app Status in OpenStack Identity (keystone): Expired Bug description: From time to time apache failed to restart with init script when keystone wsgi application is running. There is steps how to reproduce it: launch apache start/stop in cycle while :; do service apache2 stop; service apache2 start; done after sime time apache failed to start, because it can't bind to opened socket: * Starting web server apache2 * * Stopping web server apache2 * * Starting web server apache2 * * Stopping web server apache2 * * Starting web server apache2 (98)Address already in use: AH00072: make_sock: could not bind to address [::]:35357 (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:35357 no listening sockets available, shutting down AH00015: Unable to open logs Action 'start' failed. The Apache error log may have more information. * * The apache2 instance did not start within 20 seconds. Please read the log files to discover problems * Stopping web server apache2 * * Starting web server apache2 * * Stopping web server apache2 Without keystone wsgi application, I can't reproduce error in 12 hours. horizon and radosgw wsgi were enabled. It look like root cause is in keystone wsgi application itself. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1484836/+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 1198813] Re: Duplicated glance image service
Closing stale bug. If this is still an issue please reopen. ** Changed in: cinder Status: Incomplete => 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/1198813 Title: Duplicated glance image service Status in Cinder: Invalid Status in Ironic: Expired Status in OpenStack Compute (nova): Invalid Status in python-glanceclient: Incomplete Bug description: This code is duplicated in nova, cinder and ironic. Should be removed and use the common version on python-glanceclient once the code lands. https://review.openstack.org/#/c/33327/ To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1198813/+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 1185828] Re: Default routes mappings for format, edit and new are present
Closing stale bug. If this is still an issue please reopen. ** Changed in: cinder Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1185828 Title: Default routes mappings for format, edit and new are present Status in Cinder: Invalid Status in Glance: Fix Released Bug description: This invalid call: $ curl -H "x-auth-token: `cat ~/token`" http://localhost:9292/v1/images/detail.xxx Returns 200 (rather than 404) and also creates a file in the cache area: $ ls -l /opt/stack/data/glance/cache/detail.xxx -rw-r- 1 ubuntu ubuntu 1513 May 30 14:00 /opt/stack/data/glance/cache/detail.xxx To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1185828/+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 1511982] [NEW] Unable to upgrade the DB from kilo to liberty with VPNaaS
Public bug reported: i'm trying to upgrade neutron from Kilo to Liberty with VPNaaS enabled. While neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade liberty I get this error. Traceback (most recent call last): File "/usr/bin/neutron-db-manage", line 10, in sys.exit(main()) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 554, in main CONF.command.func(config, CONF.command.name) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 188, in do_upgrade run_sanity_checks(config, revision) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 541, in run_sanity_checks script_dir.run_env() File "/usr/lib/python2.7/dist-packages/alembic/script/base.py", line 397, in run_env util.load_python_file(self.dir, 'env.py') File "/usr/lib/python2.7/dist-packages/alembic/util/pyfiles.py", line 81, in load_python_file module = load_module_py(module_id, path) File "/usr/lib/python2.7/dist-packages/alembic/util/compat.py", line 79, in load_module_py mod = imp.load_source(module_id, path, fp) File "/usr/lib/python2.7/dist-packages/neutron_vpnaas/db/migration/alembic_migrations/env.py", line 87, in run_migrations_online() File "/usr/lib/python2.7/dist-packages/neutron_vpnaas/db/migration/alembic_migrations/env.py", line 78, in run_migrations_online context.run_migrations() File "", line 8, in run_migrations File "/usr/lib/python2.7/dist-packages/alembic/runtime/environment.py", line 797, in run_migrations self.get_context().run_migrations(**kw) File "/usr/lib/python2.7/dist-packages/alembic/runtime/migration.py", line 303, in run_migrations for step in self._migrations_fn(heads, self): File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 532, in check_sanity revision, rev, implicit_base=True): File "/usr/lib/python2.7/dist-packages/alembic/script/revision.py", line 664, in _iterate_revisions raise RangeNotAncestorError(lower, upper) alembic.script.revision.RangeNotAncestorError: Revision (u'2c82e782d734',) is not an ancestor of revision 24f28869838b ** Affects: neutron 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/1511982 Title: Unable to upgrade the DB from kilo to liberty with VPNaaS Status in neutron: New Bug description: i'm trying to upgrade neutron from Kilo to Liberty with VPNaaS enabled. While neutron-db-manage --config-file /etc/neutron/neutron.conf --config- file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade liberty I get this error. Traceback (most recent call last): File "/usr/bin/neutron-db-manage", line 10, in sys.exit(main()) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 554, in main CONF.command.func(config, CONF.command.name) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 188, in do_upgrade run_sanity_checks(config, revision) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 541, in run_sanity_checks script_dir.run_env() File "/usr/lib/python2.7/dist-packages/alembic/script/base.py", line 397, in run_env util.load_python_file(self.dir, 'env.py') File "/usr/lib/python2.7/dist-packages/alembic/util/pyfiles.py", line 81, in load_python_file module = load_module_py(module_id, path) File "/usr/lib/python2.7/dist-packages/alembic/util/compat.py", line 79, in load_module_py mod = imp.load_source(module_id, path, fp) File "/usr/lib/python2.7/dist-packages/neutron_vpnaas/db/migration/alembic_migrations/env.py", line 87, in run_migrations_online() File "/usr/lib/python2.7/dist-packages/neutron_vpnaas/db/migration/alembic_migrations/env.py", line 78, in run_migrations_online context.run_migrations() File "", line 8, in run_migrations File "/usr/lib/python2.7/dist-packages/alembic/runtime/environment.py", line 797, in run_migrations self.get_context().run_migrations(**kw) File "/usr/lib/python2.7/dist-packages/alembic/runtime/migration.py", line 303, in run_migrations for step in self._migrations_fn(heads, self): File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 532, in check_sanity revision, rev, implicit_base=True): File "/usr/lib/python2.7/dist-packages/alembic/script/revision.py", line 664, in _iterate_revisions raise RangeNotAncestorError(lower, upper) alembic.script.revision.RangeNotAncestorError: Revision (u'2c82e782d734',) is not an ancestor of revision 24f28869838b To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1511982/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team P
[Yahoo-eng-team] [Bug 1471959] Re: Dhcp error in network with two subnet when one is disabled
*** This bug is a duplicate of bug 1417379 ***
https://bugs.launchpad.net/bugs/1417379
just now noticed, this is duplicate to bug
https://bugs.launchpad.net/neutron/+bug/1417379
** This bug has been marked a duplicate of bug 1417379
KeyError returned when subnet-update enable_dhcp to False
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1471959
Title:
Dhcp error in network with two subnet when one is disabled
Status in neutron:
New
Bug description:
Trace:
ERROR neutron.agent.dhcp_agent [-] Unable to enable dhcp for
125c7403-1ef1-489c-bc0c-cf6a0f83e742.
Traceback (most recent call last):
File "/opt/stack/neutron/neutron/agent/dhcp_agent.py", line 128, in
call_driver
getattr(driver, action)(**action_kwargs)
File "/opt/stack/neutron/neutron/agent/linux/dhcp.py", line 207, in enable
self.spawn_process()
File "/opt/stack/neutron/neutron/agent/linux/dhcp.py", line 376, in
spawn_process
'--dhcp-optsfile=%s' % self._output_opts_file(),
File "/opt/stack/neutron/neutron/agent/linux/dhcp.py", line 646, in
_output_opts_file
isolated_subnets = self.get_isolated_subnets(self.network)
File "/opt/stack/neutron/neutron/agent/linux/dhcp.py", line 812, in
get_isolated_subnets
if subnets[alloc.subnet_id].gateway_ip == alloc.ip_address:
KeyError: u'f1ff257b-ddb8-4069-bf9f-8a60bd704097'
TRACE neutron.agent.dhcp_agent KeyError:
u'f1ff257b-ddb8-4069-bf9f-8a60bd704097'
TRACE neutron.agent.dhcp_agent
Steps to reproduce:
NET_NAME=test-key
I=11
neutron net-create ${NET_NAME}
neutron port-create ${NET_NAME}
neutron subnet-create --name "${NET_NAME}-sub001" ${NET_NAME}
192.168.${I}.1/24
neutron subnet-create --name "${NET_NAME}-sub002" ${NET_NAME}
192.168.${I}1.1/24
while [ "$(neutron port-list | grep "192.168.${I}" | wc -l)" != 2 ]; do
echo "waiting for dhcp port on both subnet"
done
neutron subnet-update --disable-dhcp "${NET_NAME}-sub002"
sleep 10
if [ "$(neutron port-list | grep "192.168.${I}" | wc -l)" != 2 ]; then
echo "failed"
fi
Impact:
cause logs to grow more than necessary
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1471959/+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 1511925] [NEW] Update subnet allocation-pool failed
Public bug reported: this bug happens on master branch, reproduce steps: 1. create a subnet with no-gateway, etc, neutron subnet-create --no-gateway test 30.30.30.0/24 2. update this subnet allocation-pool, etc, neutron subnet-update --allocation-pool start=30.30.30.5,end=30.30.30.6 bb956363-cf67-4689-a3a7-08d179a9ea3e I get a error as bellow: failed to detect a valid IP address from None ** Affects: neutron Importance: Undecided Assignee: shihanzhang (shihanzhang) Status: New ** Changed in: neutron Assignee: (unassigned) => shihanzhang (shihanzhang) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1511925 Title: Update subnet allocation-pool failed Status in neutron: New Bug description: this bug happens on master branch, reproduce steps: 1. create a subnet with no-gateway, etc, neutron subnet-create --no-gateway test 30.30.30.0/24 2. update this subnet allocation-pool, etc, neutron subnet-update --allocation-pool start=30.30.30.5,end=30.30.30.6 bb956363-cf67-4689-a3a7-08d179a9ea3e I get a error as bellow: failed to detect a valid IP address from None To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1511925/+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 1493026] Re: location-add return error when add new location to 'queued' image
** Description changed: Reproduce: 1. create a new image: glance image-create --disk-format qcow2 --container-format bare --name test suppose the image'id is 1 2.add location to the image: glance location-add 1 --url Result : the client raise an error:'The administrator has disabled API access to image locations'. - But when use REST API to reproduce the step 2, it runs well and the image's status will be changed into 'active'. - According to the code: https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L735-L750 - I think we should add check in glance like client does. + 3.set show_multiple_locations = True in glance-api.conf. Then take step + 1,2. It works now. + + But when use REST API to reproduce it, No matter show_multiple_locations + is False or True, it runs both well and the image's status will be + changed into 'active'. + + So there are one thing to discuess: Is it need to check the location in + glance-client(show_multiple_locations)? Or Is it need to add the check + like glance-client does in Glance server on the contrary? ** Also affects: python-glanceclient Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1493026 Title: location-add return error when add new location to 'queued' image Status in Glance: Opinion Status in python-glanceclient: New Bug description: Reproduce: 1. create a new image: glance image-create --disk-format qcow2 --container-format bare --name test suppose the image'id is 1 2.add location to the image: glance location-add 1 --url Result : the client raise an error:'The administrator has disabled API access to image locations'. 3.set show_multiple_locations = True in glance-api.conf. Then take step 1,2. It works now. But when use REST API to reproduce it, No matter show_multiple_locations is False or True, it runs both well and the image's status will be changed into 'active'. So there are one thing to discuess: Is it need to check the location in glance-client(show_multiple_locations)? Or Is it need to add the check like glance-client does in Glance server on the contrary? To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1493026/+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
