yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #46192
[Bug 1542486] Re: nova-compute stack traces with BadRequest: Specifying 'tenant_id' other than authenticated tenant in request requires admin privileges
looks like middlware related, not keystone server, changing project
** Also affects: keystonemiddleware
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => 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/1542486
Title:
nova-compute stack traces with BadRequest: Specifying 'tenant_id'
other than authenticated tenant in request requires admin privileges
Status in OpenStack Identity (keystone):
Invalid
Status in keystonemiddleware:
New
Status in OpenStack Compute (nova):
Incomplete
Status in puppet-nova:
New
Bug description:
The puppet-openstack-integration tests (rebased on
https://review.openstack.org/#/c/276773/ ) currently fail on the
latest version of RDO Mitaka (delorean current) due to what seems to
be a problem with the neutron configuration.
Everything installs fine but tempest fails:
http://logs.openstack.org/92/276492/6/check/gate-puppet-openstack-integration-scenario001-tempest-dsvm-centos7/78b9c32/console.html#_2016-02-05_20_26_35_569
And there are stack traces in nova-compute.log:
http://logs.openstack.org/92/276492/6/check/gate-puppet-openstack-integration-scenario001-tempest-dsvm-centos7/78b9c32/logs/nova/nova-compute.txt.gz#_2016-02-05_20_22_16_151
I talked with #openstack-nova and they pointed out a difference between what devstack yields as a [neutron] configuration versus what puppet-nova configures:
####
# puppet-nova via puppet-openstack-integration
####
[neutron]
service_metadata_proxy=True
metadata_proxy_shared_secret =a_big_secret
url=http://127.0.0.1:9696
region_name=RegionOne
ovs_bridge=br-int
extension_sync_interval=600
auth_url=http://127.0.0.1:35357
password=a_big_secret
tenant_name=services
timeout=30
username=neutron
auth_plugin=password
default_tenant_id=default
####
# Well, it worked in devstack™
####
[neutron]
service_metadata_proxy = True
url = http://127.0.0.1:9696
region_name = RegionOne
auth_url = http://127.0.0.1:35357/v3
password = secretservice
auth_strategy = keystone
project_domain_name = Default
project_name = service
user_domain_name = Default
username = neutron
auth_plugin = v3password
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1542486/+subscriptions