[Yahoo-eng-team] [Bug 1608378] [NEW] Creating metering-label-rule with non-existent UUID of metering_label_id raised 500 Internal Server Error
Public bug reported:
1. When I was trying to create metering-label-rule by inserting non-
existent UUID of metering_label_id then it raised 500 Internal Server
Error, and according to the traceback of logs itself which explained
that "foreign key constraint". However this perhaps should be 404 Not
Found since I was inserting non-existent UUID of metering_label_id.
Here I attached all of request which was sent to API and traceback log.
---
Request parameters
curl -g -i -X POST
http://192.168.122.139:9696/v2.0/metering/metering-label-rules -H
"X-Auth-Token: $TOKEN" -d
'{"metering_label_rule":{"remote_ip_prefix":"10.0.1.0/24", "direction":
"ingress", "metering_label_id":"0fd2758c-0754-4773-997f-44d3db288a75"}}'
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 150
X-Openstack-Request-Id: req-f4e2ae59-4d4b-491f-96be-58d9ce6ebc39
Date: Fri, 29 Jul 2016 01:35:24 GMT
{"NeutronError": {"message": "Request Failed: internal server error
while processing your request.", "type": "HTTPInternalServerError",
"detail": ""}}
Log
2016-07-29 10:35:24.047 1448 DEBUG neutron.wsgi [-] (1448) accepted
('192.168.122.139', 6574) server
/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py:868
2016-07-29 10:35:24.149 1448 DEBUG neutron.api.v2.base
[req-f4e2ae59-4d4b-491f-96be-58d9ce6ebc39 e01bc3eadeb045edb02fc6b2af4b5d49
867929bfedca4a719e17a7f3293845de - - -] Request body: {u'metering_label_rule':
{u'remote_ip_prefix': u'10.0.1.0/24', u'direction': u'ingress',
u'metering_label_id': u'0fd2758c-0754-4773-997f-44d3db288a75'}}
prepare_request_body /opt/stack/neutron/neutron/api/v2/base.py:649
2016-07-29 10:35:24.152 1448 DEBUG neutron.api.v2.base
[req-f4e2ae59-4d4b-491f-96be-58d9ce6ebc39 e01bc3eadeb045edb02fc6b2af4b5d49
867929bfedca4a719e17a7f3293845de - - -] Unknown quota resources
['metering_label_rule']. _create /opt/stack/neutron/neutron/api/v2/base.py:445
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource
[req-f4e2ae59-4d4b-491f-96be-58d9ce6ebc39 e01bc3eadeb045edb02fc6b2af4b5d49
867929bfedca4a719e17a7f3293845de - - -] create failed: No details.
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource Traceback (most
recent call last):
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource File
"/opt/stack/neutron/neutron/api/v2/resource.py", line 79, in resource
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource result =
method(request=request, **args)
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource File
"/opt/stack/neutron/neutron/api/v2/base.py", line 397, in create
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource return
self._create(request, body, **kwargs)
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 148, in wrapper
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource ectxt.value =
e.inner_exc
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in
__exit__
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource
self.force_reraise()
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in
force_reraise
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource
six.reraise(self.type_, self.value, self.tb)
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 138, in wrapper
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource return f(*args,
**kwargs)
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource File
"/opt/stack/neutron/neutron/api/v2/base.py", line 510, in _create
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource obj =
do_create(body)
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource File
"/opt/stack/neutron/neutron/api/v2/base.py", line 492, in do_create
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource request.context,
reservation.reservation_id)
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in
__exit__
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource
self.force_reraise()
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in
force_reraise
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource
six.reraise(self.type_, self.value, self.tb)
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource File
"/opt/stack/neutron/neutron/api/v2/base.py", line 485, in do_create
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource return
obj_creator(request.context, **kwargs)
2016-07-29 10:35:24.186 1448 ERROR neutron.api.v2.resource File
"/opt/stack/neutron/neu
[Yahoo-eng-team] [Bug 1608361] [NEW] After updating metadata any messages are not shown
Public bug reported: When I update metadata from somewhere like Admin -> Flavor, Admin -> Image, Project -> Instances and so on, after being updated there is no message on display. So a user could not understand whether this process succeeded or failed. ** Affects: horizon Importance: Undecided Assignee: Kenji Ishii (ken-ishii) Status: New ** Changed in: horizon Assignee: (unassigned) => Kenji Ishii (ken-ishii) -- 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/1608361 Title: After updating metadata any messages are not shown Status in OpenStack Dashboard (Horizon): New Bug description: When I update metadata from somewhere like Admin -> Flavor, Admin -> Image, Project -> Instances and so on, after being updated there is no message on display. So a user could not understand whether this process succeeded or failed. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1608361/+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 1608353] [NEW] QoS Spec Creation for Volumes doesn't validate blank spaces
Public bug reported: Volume Type QoS Spec Creation doesn't validate blank spaces as Name Values on horizon. ** Affects: horizon Importance: Undecided Assignee: sandeep nandal (nandal) Status: New -- 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/1608353 Title: QoS Spec Creation for Volumes doesn't validate blank spaces Status in OpenStack Dashboard (Horizon): New Bug description: Volume Type QoS Spec Creation doesn't validate blank spaces as Name Values on horizon. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1608353/+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 1608351] [NEW] Volume Type Extra Spec key-value creation doesn't validate blank spaces
Public bug reported: Volume Type Extra Spec key-value creation doesn't validate blank spaces. Blank spaces should not be allowed as key-value pairs values. There must be a validation to prompt use for entering a invalid values. ** Affects: cinder Importance: Undecided Status: New ** Affects: horizon Importance: Undecided Status: New ** Also affects: horizon Importance: Undecided Status: New -- 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/1608351 Title: Volume Type Extra Spec key-value creation doesn't validate blank spaces Status in Cinder: New Status in OpenStack Dashboard (Horizon): New Bug description: Volume Type Extra Spec key-value creation doesn't validate blank spaces. Blank spaces should not be allowed as key-value pairs values. There must be a validation to prompt use for entering a invalid values. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1608351/+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 1608347] [NEW] Neutron-server can't clean obsolete tunnel info
Public bug reported: Now for tunnel network like vxlan or gre in neutron, if we change a compute node tunnel IP, the obsolete tunnel info was still saved in neutron-server, and other compute nodes still established tunnel with the obsolete IP, I think we should provide a approach to clean the obsolete tunnel info, like ovs_cleanup.py. ** Affects: neutron Importance: Undecided Assignee: shihanzhang (shihanzhang) Status: New ** Description changed: - Now for tunnel network like vxlan or gre in neutron, if we change a compute node tunnel IP, the obsolete tunnel info was - still saved in neutron-server, and other compute nodes still established tunnel with the obsolete IP, I think we should provide a approach to clean the obsolete tunnel info, like ovs_cleanup.py. + Now for tunnel network like vxlan or gre in neutron, if we change a + compute node tunnel IP, the obsolete tunnel info was still saved in + neutron-server, and other compute nodes still established tunnel with + the obsolete IP, I think we should provide a approach to clean the + obsolete tunnel info, like ovs_cleanup.py. ** 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/1608347 Title: Neutron-server can't clean obsolete tunnel info Status in neutron: New Bug description: Now for tunnel network like vxlan or gre in neutron, if we change a compute node tunnel IP, the obsolete tunnel info was still saved in neutron-server, and other compute nodes still established tunnel with the obsolete IP, I think we should provide a approach to clean the obsolete tunnel info, like ovs_cleanup.py. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1608347/+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 1608346] [NEW] test breakage due to config refactoring
Public bug reported: core_opts is referenced by at least fwaas and vpnaas tests. they got broken by the recently merged code refactoring. [1] [1] Ib5fa294906549237630f87b9c848eebe0644088c ** Affects: neutron Importance: Undecided Assignee: YAMAMOTO Takashi (yamamoto) Status: In Progress ** Tags: gate-failure ** Tags added: gate-failure ** Description changed: - core_opts are referenced by at least fwaas and vpnaas tests. + core_opts is referenced by at least fwaas and vpnaas tests. they got broken by the recently merged code refactoring. [1] [1] Ib5fa294906549237630f87b9c848eebe0644088c -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1608346 Title: test breakage due to config refactoring Status in neutron: In Progress Bug description: core_opts is referenced by at least fwaas and vpnaas tests. they got broken by the recently merged code refactoring. [1] [1] Ib5fa294906549237630f87b9c848eebe0644088c To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1608346/+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 1505298] Re: No JSONSchema validation on some of federation API calls
This was completed by https://blueprints.launchpad.net/keystone/+spec /schema-validation-extent ** Changed in: keystone Assignee: Aswad Rangnekar (aswad-r) => (unassigned) ** Changed in: keystone Status: In Progress => Fix Released -- 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/1505298 Title: No JSONSchema validation on some of federation API calls Status in OpenStack Identity (keystone): Fix Released Bug description: Identity providers, Mapping and Protocols CRUD requests should be validated with JSONSchema. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1505298/+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 1291157] Re: idp deletion should trigger token revocation
unassigning due to inactivity ** Changed in: keystone Assignee: Sean Perry (sean-perry-a) => (unassigned) ** Changed in: keystone Status: In Progress => Confirmed ** No longer affects: python-keystoneclient -- 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/1291157 Title: idp deletion should trigger token revocation Status in OpenStack Identity (keystone): Confirmed Bug description: When a federation IdP is deleted, the tokens that were issued (and still active) and associated with the IdP should be deleted. To prevent unwarranted access. The fix should delete any tokens that are associated with the idp, upon deletion (and possibly update, too). To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1291157/+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 1471289] Re: Fernet tokens and Federated Identities result in token scope failures
** No longer affects: keystone/kilo
--
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/1471289
Title:
Fernet tokens and Federated Identities result in token scope failures
Status in OpenStack Identity (keystone):
Fix Released
Bug description:
When keystone is configured to use fernet tokens and also configured
to be a SP for an external IDP then the token data received by nova
and other services appear to not contain the right information,
resulting in errors from nova-api-os-compute such as:
Returning 400 to user: Malformed request URL: URL's project_id
'69f5cff441e04554b285d7772630dec1' doesn't match Context's project_id
'None'
When keystone is switched to use uuid tokens, then everything works as
expected.
Further debugging of the request to the nova api shows:
'HTTP_X_USER_DOMAIN_NAME': None,
'HTTP_X_DOMAIN_ID': None,
'HTTP_X_PROJECT_DOMAIN_ID': None,
'HTTP_X_ROLES': '',
'HTTP_X_TENANT_ID': None,
'HTTP_X_PROJECT_DOMAIN_NAME': None,
'HTTP_X_TENANT': None,
'HTTP_X_USER': u'S-1-5-21-2917001131-1385516553-613696311-1108',
'HTTP_X_USER_DOMAIN_ID': None,
'HTTP_X_AUTH_PROJECT_ID': '69f5cff441e04554b285d7772630dec1',
'HTTP_X_DOMAIN_NAME': None,
'HTTP_X_PROJECT_NAME': None,
'HTTP_X_PROJECT_ID': None,
'HTTP_X_USER_NAME': u'S-1-5-21-2917001131-1385516553-613696311-1108'
Comparing the interaction of nova-api-os-compute with keystone for the
token validation between an internal user and a federated user, the
following is seen:
### federated user ###
2015-07-03 14:43:05.229 8103 DEBUG keystoneclient.session [-] REQ: curl -g -i
--insecure -X GET https://sp.testenvironment.local:5000/v3/auth/tokens -H
"X-Subject-Token: {SHA1}acff9b5962270fec270e693eacb4c987c335f5c5" -H
"User-Agent: python-keystoneclient" -H "Accept: application/json" -H
"X-Auth-Token: {SHA1}a6a8a70ae39c533379eccd51b6d253f264d59f14"
_http_log_request
/usr/local/lib/python2.7/dist-packages/keystoneclient/session.py:193
2015-07-03 14:43:05.265 8103 DEBUG keystoneclient.session [-] RESP: [200]
content-length: 402 x-subject-token:
{SHA1}acff9b5962270fec270e693eacb4c987c335f5c5 vary: X-Auth-Token keep-alive:
timeout=5, max=100 server: Apache/2.4.7 (Ubuntu) connection: Keep-Alive date:
Fri, 03 Jul 2015 14:43:05 GMT content-type: application/json
x-openstack-request-id: req-df3dce71-3174-4753-b883-11eb31a67d7c
RESP BODY: {"token": {"methods": ["token"], "expires_at":
"2015-07-04T02:43:04.00Z", "extras": {}, "user": {"OS-FEDERATION":
{"identity_provider": {"id": "adfs-idp"}, "protocol": {"id": "saml2"},
"groups": []}, "id": "S-1-5-21-2917001131-1385516553-613696311-1108", "name":
"S-1-5-21-2917001131-1385516553-613696311-1108"}, "audit_ids":
["_a6BbQ6mSoGAY2u9NN0tFA"], "issued_at": "2015-07-03T14:43:04.00Z"}}
### internal user ###
2015-07-03 14:28:31.875 8103 DEBUG keystoneclient.session [-] REQ: curl -g -i
--insecure -X GET https://sp.testenvironment.local:5000/v3/auth/tokens -H
"X-Subject-Token: {SHA1}b9c6748d65a0492faa9862fabf0a56fd5fdd255d" -H
"User-Agent: python-keystoneclient" -H "Accept: application/json" -H
"X-Auth-Token: {SHA1}a6a8a70ae39c533379eccd51b6d253f264d59f14"
_http_log_request
/usr/local/lib/python2.7/dist-packages/keystoneclient/session.py:193
2015-07-03 14:28:31.949 8103 DEBUG keystoneclient.session [-] RESP: [200]
content-length: 6691 x-subject-token:
{SHA1}b9c6748d65a0492faa9862fabf0a56fd5fdd255d vary: X-Auth-Token keep-alive:
timeout=5, max=100 server: Apache/2.4.7 (Ubuntu) connection: Keep-Alive date:
Fri, 03 Jul 2015 14:28:31 GMT content-type: application/json
x-openstack-request-id: req-6e0ed9f4-46c3-4c79-b444-f72963fc9503
RESP BODY: {"token": {"methods": ["password"], "roles": [{"id":
"9fe2ff9ee4384b1894a90878d3e92bab", "name": "_member_"}], "expires_at":
"2015-07-04T02:28:31.00Z", "project": {"domain": {"id": "default", "name":
"Default"}, "id": "0f491c8551c04cdc804a479af0bf13ec", "name": "demo"},
"catalog": "", "extras": {}, "user": {"domain": {"id": "default",
"name": "Default"}, "id": "76c8c3017c954d88a6ad69ee4cb656d6", "name": "test"},
"audit_ids": ["aAN_V0c6SLSI0Rm1hoScCg"], "issued_at":
"2015-07-03T14:28:31.00Z"}}
The data structures that come back from keystone are clearly quite
different.
### configuration environment ###
Ubuntu 14.04 OS
nova==12.0.0.0a1.dev51 # commit a4f4be370be06cfc9aa3ed30d2445277e832376f from
master branch
keystone==8.0.0.0a1.dev12 # commit a7ca13b687dd284f0980d768b11a3d1b52b4106e
from master branch
python-keystoneclient==1.6.1.dev19 # commit
d238cc9af4927d1092de207db978536d712af129 from master branch
python-openstackclient==1.5.1.dev11# commit
2d6bc8f4c38dbf997e3e71119f13f0328b4a8669 from master branch
python-novaclient==2.26.1.dev25 # commit
3c2ff0faad8c84777ffe7d9946a1bc4486116084 from master branch
keystonemiddl
[Yahoo-eng-team] [Bug 1608332] [NEW] create pool api parameter issue
Public bug reported:
There is a bug in the documentation for lbaas v2 pool create parameters.
http://developer.openstack.org/api-ref/networking/v2-ext/index.html?expanded=create-a-load-balancer-pool-detail,create-pool-detail.
The request parameter mentioned are
{
"pool": {
"admin_state_up": true,
"description": "simple pool",
"lb_algorithm": "ROUND_ROBIN",
"name": "my-pool",
"protocol": "HTTP",
"subnet_id": "e301aed0-d9e7-498a-977c-1bbfaf14ed5d"
}
}
create pool needs listener ID and not subnet Id
** 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/1608332
Title:
create pool api parameter issue
Status in neutron:
New
Bug description:
There is a bug in the documentation for lbaas v2 pool create parameters.
http://developer.openstack.org/api-ref/networking/v2-ext/index.html?expanded=create-a-load-balancer-pool-detail,create-pool-detail.
The request parameter mentioned are
{
"pool": {
"admin_state_up": true,
"description": "simple pool",
"lb_algorithm": "ROUND_ROBIN",
"name": "my-pool",
"protocol": "HTTP",
"subnet_id": "e301aed0-d9e7-498a-977c-1bbfaf14ed5d"
}
}
create pool needs listener ID and not subnet Id
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1608332/+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 1608314] Re: vpn ut failure
** Also affects: neutron
Importance: Undecided
Status: New
** Tags added: vpnaas
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1608314
Title:
vpn failure with neutron-lib 0.3.0
Status in networking-midonet:
In Progress
Status in neutron:
In Progress
Bug description:
http://logs.openstack.org/16/349016/1/check/gate-networking-midonet-
python27-ubuntu-xenial/102bea5/testr_results.html.gz
ft18.5:
midonet.neutron.tests.unit.test_extension_vpnaas.VPNTestCase.test_update_ipsec_site_connection_error_StringException:
Empty attachments:
stdout
pythonlogging:'': {{{
WARNING [stevedore.named] Could not load
midonet.neutron.plugin_v2.MidonetPluginV2
WARNING [stevedore.named] Could not load
neutron_vpnaas.services.vpn.plugin.VPNDriverPlugin
WARNING [stevedore.named] Could not load
midonet.neutron.services.vpn.service_drivers.midonet_ipsec.MidonetIPsecVPNDriver
WARNING [neutron.api.extensions] Extension address-scope not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension auto-allocated-topology not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension availability_zone not supported
by any of loaded plugins
WARNING [neutron.api.extensions] Extension default-subnetpools not supported
by any of loaded plugins
WARNING [neutron.api.extensions] Extension dns-integration not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension dvr not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension flavors not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension ip_allocation not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension l3-ha not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension l3-flavors not supported by any
of loaded plugins
WARNING [neutron.api.extensions] Extension l3_agent_scheduler not supported
by any of loaded plugins
WARNING [neutron.api.extensions] Extension metering not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension multi-provider not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension net-mtu not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension network_availability_zone not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension network-ip-availability not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension qos not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension revisions not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension router_availability_zone not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension router-service-type not supported
by any of loaded plugins
WARNING [neutron.api.extensions] Extension segment not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension tag not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension timestamp_core not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension trunk not supported by any of
loaded plugins
WARNING [neutron.api.extensions] Extension trunk-details not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension vlan-transparent not supported by
any of loaded plugins
ERROR [neutron.api.extensions] Extension path
'neutron/tests/unit/extensions' doesn't exist!
WARNING [neutron.api.extensions] Extension bgp-speaker-router-insertion not
supported by any of loaded plugins
WARNING [neutron.api.extensions] Extension gateway-device not supported by
any of loaded plugins
WARNING [neutron.api.extensions] Extension logging-resource not supported by
any of loaded plugins
WARNING [neutron.quota.resource_registry] network is already registered
WARNING [neutron.quota.resource_registry] subnetpool is already registered
WARNING [neutron.quota.resource_registry] port is already registered
WARNING [neutron.quota.resource_registry] subnet is already registered
WARNING [neutron.quota.resource_registry] router is already registered
WARNING [neutron.quota.resource_registry] floatingip is already registered
WARNING [neutron.scheduler.dhcp_agent_scheduler] No more DHCP agents
WARNING [neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api] Unable to
schedule network 1d884b17-a640-4392-9e83-ca704a8338fb: no agents available;
will retry on subsequent port and subnet creation events.
WARNING [neutron.scheduler.dhcp_agent_scheduler] No more DHCP agents
WARNING [neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api] Unable to
schedule network ce5d24a2-ab47-4c49-bff0-2e980e009b79: no agents available;
will retry on
[Yahoo-eng-team] [Bug 1607107] Re: Unauthorized exception causes missing exception kwargs (programmer error)
Not sure why this wasn't updated,
https://review.openstack.org/#/c/348086/ closed it out.
** Changed in: keystone
Status: In Progress => Fix Released
--
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/1607107
Title:
Unauthorized exception causes missing exception kwargs (programmer
error)
Status in OpenStack Identity (keystone):
Fix Released
Bug description:
I created the following class in keystone/exception.py:
class AccountLocked(Unauthorized):
message_format = _("The account is locked for user: %(user_id)s")
And would raise the exception if a user account was locked:
raise exception.AccountLocked(user_id=user_id)
However when doing so, the following error would get logged:
missing exception kwargs (programmer error)
This seems to be a product of:
https://github.com/openstack/keystone/blob/master/keystone/exception.py#L61-L67
A few of us spent time on this in IRC. For more content you can view that
conversation here:
http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2016-07-27.log.html#t2016-07-27T14:49:24
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1607107/+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 1606426] Re: user list is much slower in mitaka and newton
** Changed in: keystone/mitaka Status: Fix Committed => Fix Released -- 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/1606426 Title: user list is much slower in mitaka and newton Status in OpenStack Identity (keystone): Invalid Status in OpenStack Identity (keystone) mitaka series: Fix Released Bug description: With Kilo doing a user-list on V2 or V3 would take approx. 2-4 seconds In Mitaka it takes 19-22 seconds. This is a significant slow down. We have ~9,000 users We also changed from going under eventlet to moving to apache wsgi We have ~10,000 project and this api (project-list) hasn't slowed down so I think this is something specific to the user-list api To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1606426/+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 1595819] Re: cannot create (or set) a user with no password
** Changed in: heat
Assignee: Ron De Rose (ronald-de-rose) => (unassigned)
** Changed in: heat
Status: New => Invalid
--
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/1595819
Title:
cannot create (or set) a user with no password
Status in heat:
Invalid
Status in OpenStack Identity (keystone):
Fix Released
Bug description:
It seems the gate is broken with AutoScalingSignaltest faling.
I suspect this is due to the recent keystone change
https://review.openstack.org/#/c/314284/
keystone error traceback:
2016-06-24 03:34:02.273 8966 ERROR oslo_db.sqlalchemy.exc_filters
[req-99ad876c-6f1f-4742-8dcf-52d461fa0c9f
16a1dbfadccd44a3813a0e097a61ac25 - a08006a9c7c84f5ca7afaed59ac8e7a5
a08006a9c7c84f5ca7afaed59ac8e7a5 -] DBAPIError exception wrapped from
(pymysql.err.IntegrityError) (1048, u"Column 'password' cannot be
null") [SQL: u'INSERT INTO password (local_user_id, password,
created_at, expires_at) VALUES (%(local_user_id)s, %(password)s,
%(created_at)s, %(expires_at)s)'] [parameters: {'local_user_id': 36,
'password': None, 'created_at': datetime.datetime(2016, 6, 24, 3, 34,
2, 269022), 'expires_at': None}]
heat engine traceback:
http://logs.openstack.org/76/333676/1/check/gate-heat-dsvm-functional-
orig-mysql-
lbaasv2/516afaa/logs/screen-h-eng.txt.gz#_2016-06-24_03_34_02_280
b2c8-e27e2a774982]
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource Traceback (most
recent call last):
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/opt/stack/new/heat/heat/engine/resource.py", line 716, in _action_recorder
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource yield
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/opt/stack/new/heat/heat/engine/resource.py", line 796, in _do_action
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource yield
self.action_handler_task(action, args=handler_args)
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/opt/stack/new/heat/heat/engine/scheduler.py", line 312, in wrapper
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource step =
next(subtask)
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/opt/stack/new/heat/heat/engine/resource.py", line 759, in action_handler_task
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource handler_data =
handler(*args)
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/opt/stack/new/heat/heat/engine/resources/stack_user.py", line 110, in
handle_suspend
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource user_id=user_id,
project_id=self.stack.stack_user_project_id)
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/opt/stack/new/heat/heat/engine/clients/os/keystone/heat_keystoneclient.py",
line 528, in disable_stack_domain_user
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource
self.domain_admin_client.users.update(user=user_id, enabled=False)
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/usr/local/lib/python2.7/dist-packages/debtcollector/renames.py", line 43, in
decorator
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource return
wrapped(*args, **kwargs)
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/usr/local/lib/python2.7/dist-packages/positional/__init__.py", line 101, in
inner
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource return
wrapped(*args, **kwargs)
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/usr/local/lib/python2.7/dist-packages/keystoneclient/v3/users.py", line 209,
in update
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource log=False)
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/usr/local/lib/python2.7/dist-packages/keystoneclient/base.py", line 227, in
_update
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource **kwargs)
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/usr/local/lib/python2.7/dist-packages/keystoneauth1/adapter.py", line 190, in
patch
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource return
self.request(url, 'PATCH', **kwargs)
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/usr/local/lib/python2.7/dist-packages/keystoneauth1/adapter.py", line 335, in
request
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource resp =
super(LegacyJsonAdapter, self).request(*args, **kwargs)
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/usr/local/lib/python2.7/dist-packages/keystoneauth1/adapter.py", line 103, in
request
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource return
self.session.request(url, method, **kwargs)
2016-06-24 03:34:02.280 4863 ERROR heat.engine.resource File
"/usr/local/lib/python2.7/dist-packages/positional/_
[Yahoo-eng-team] [Bug 1608258] [NEW] test_neutronv2 unit tests fail with python-neutronclient 5.0.0
Public bug reported:
Seen in a g-r change here:
https://review.openstack.org/#/c/347652/
http://logs.openstack.org/52/347652/5/check/gate-cross-nova-python27-db-
ubuntu-xenial/97c6a0d/console.html#_2016-07-30_17_59_01_389311
2016-07-30 17:59:01.388984 | Captured traceback:
2016-07-30 17:59:01.389033 | ~~~
2016-07-30 17:59:01.389058 | Traceback (most recent call last):
2016-07-30 17:59:01.389095 | File
"nova/tests/unit/network/test_neutronv2.py", line 1678, in
test_validate_networks
2016-07-30 17:59:01.389120 | tenant_id=uuids.my_tenant).AndReturn(
2016-07-30 17:59:01.389175 | File
"/home/jenkins/workspace/gate-cross-nova-python27-db-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/mox3/mox.py",
line 1109, in __call__
2016-07-30 17:59:01.389200 | self._checker.Check(params, named_params)
2016-07-30 17:59:01.389253 | File
"/home/jenkins/workspace/gate-cross-nova-python27-db-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/mox3/mox.py",
line 1031, in Check
2016-07-30 17:59:01.389280 | % (' '.join(sorted(still_needed
2016-07-30 17:59:01.389311 | AttributeError: No values given for arguments:
project_id
It's because of this change: https://review.openstack.org/#/c/320090/
And these unit tests are creating a mox'ed mock of the neutronclient
Client class, which doesn't get that these methods are decorated with a
rename from debtcollector:
http://git.openstack.org/cgit/openstack/debtcollector/tree/debtcollector/renames.py#n25
We currently require neutronclient>=4.2 which doesn't have these kwargs,
so I can't start passing project_name/project_id until
neutronclient>=5.0 in g-r, and I can't pass tenant_id/name until that
point.
We might have to change the tests to use mock instead of mox which is
less strict.
** Affects: nova
Importance: High
Status: Triaged
** Tags: neutron testing
--
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/1608258
Title:
test_neutronv2 unit tests fail with python-neutronclient 5.0.0
Status in OpenStack Compute (nova):
Triaged
Bug description:
Seen in a g-r change here:
https://review.openstack.org/#/c/347652/
http://logs.openstack.org/52/347652/5/check/gate-cross-nova-python27
-db-ubuntu-xenial/97c6a0d/console.html#_2016-07-30_17_59_01_389311
2016-07-30 17:59:01.388984 | Captured traceback:
2016-07-30 17:59:01.389033 | ~~~
2016-07-30 17:59:01.389058 | Traceback (most recent call last):
2016-07-30 17:59:01.389095 | File
"nova/tests/unit/network/test_neutronv2.py", line 1678, in
test_validate_networks
2016-07-30 17:59:01.389120 | tenant_id=uuids.my_tenant).AndReturn(
2016-07-30 17:59:01.389175 | File
"/home/jenkins/workspace/gate-cross-nova-python27-db-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/mox3/mox.py",
line 1109, in __call__
2016-07-30 17:59:01.389200 | self._checker.Check(params, named_params)
2016-07-30 17:59:01.389253 | File
"/home/jenkins/workspace/gate-cross-nova-python27-db-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/mox3/mox.py",
line 1031, in Check
2016-07-30 17:59:01.389280 | % (' '.join(sorted(still_needed
2016-07-30 17:59:01.389311 | AttributeError: No values given for
arguments: project_id
It's because of this change: https://review.openstack.org/#/c/320090/
And these unit tests are creating a mox'ed mock of the neutronclient
Client class, which doesn't get that these methods are decorated with
a rename from debtcollector:
http://git.openstack.org/cgit/openstack/debtcollector/tree/debtcollector/renames.py#n25
We currently require neutronclient>=4.2 which doesn't have these
kwargs, so I can't start passing project_name/project_id until
neutronclient>=5.0 in g-r, and I can't pass tenant_id/name until that
point.
We might have to change the tests to use mock instead of mox which is
less strict.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1608258/+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 1608224] [NEW] neutron lib warnings in ipv6_util; s
Public bug reported: Captured stderr: /home/gkotton/networking-sfc/.tox/py27/src/neutron/neutron/common/ipv6_utils.py:70: DeprecationWarning: IPV6_SLAAC in version 'mitaka' and will be removed in version 'newton': moved to neutron_lib.constants modes = [constants.IPV6_SLAAC, constants.DHCPV6_STATELESS] /home/gkotton/networking-sfc/.tox/py27/src/neutron/neutron/common/ipv6_utils.py:70: DeprecationWarning: DHCPV6_STATELESS in version 'mitaka' and will be removed in version 'newton': moved to neutron_lib.constants modes = [constants.IPV6_SLAAC, constants.DHCPV6_STATELESS] ** Affects: neutron Importance: Undecided Assignee: Gary Kotton (garyk) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Gary Kotton (garyk) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1608224 Title: neutron lib warnings in ipv6_util;s Status in neutron: In Progress Bug description: Captured stderr: /home/gkotton/networking-sfc/.tox/py27/src/neutron/neutron/common/ipv6_utils.py:70: DeprecationWarning: IPV6_SLAAC in version 'mitaka' and will be removed in version 'newton': moved to neutron_lib.constants modes = [constants.IPV6_SLAAC, constants.DHCPV6_STATELESS] /home/gkotton/networking-sfc/.tox/py27/src/neutron/neutron/common/ipv6_utils.py:70: DeprecationWarning: DHCPV6_STATELESS in version 'mitaka' and will be removed in version 'newton': moved to neutron_lib.constants modes = [constants.IPV6_SLAAC, constants.DHCPV6_STATELESS] To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1608224/+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 1608209] [NEW] manage.py not found
Public bug reported:
I've followed all instruction from OpenStack.org to setup a "All In One" Linux
server with OpenStack.
I've used Ubuntu 16.04.1 (supported) with minimal installation, then I've run
stack.sh with success. Test.sh run with success too.
Opening Horizon it fails with a very common error found a lot in literature.
I've tried some fixes with no success.
But the real strange thing is that THERE'S NO MANAGE.PY file at all to
run...
You have offline compression enabled but key "71f1bb91aa1db46c691a399635d662c7"
is missing from offline manifest. You may need to run "python manage.py
compress".
1 {% load compress %}
2 {% load themes %}
3
4
5
{% compress css %}
6
7
8 {% endcompress %}
9
10
11
12 {% current_theme as current_theme %}
13 {% theme_dir as theme_dir %}
14
15 {% comment %}
** Affects: horizon
Importance: Undecided
Status: New
** Description changed:
I've followed all instruction from OpenStack.org to setup a "All In One"
Linux server with OpenStack.
- I've used Ubuntu 16.04.1 (supported) with minimal installation, then I've run
stack.sh with success.
+ I've used Ubuntu 16.04.1 (supported) with minimal installation, then I've run
stack.sh with success. Test.sh run with success too.
Opening Horizon it fails with a very common error found a lot in literature.
I've tried some fixes with no success.
But the real strange thing is that THERE'S NO MANAGE.PY file at all to
run...
-
You have offline compression enabled but key
"71f1bb91aa1db46c691a399635d662c7" is missing from offline manifest. You may
need to run "python manage.py compress".
1 {% load compress %}
2 {% load themes %}
- 3
- 4
- 5
-
- {% compress css %}
-
+ 3
+ 4
+ 5
-
+ {% compress css %}
+
6
7
8 {% endcompress %}
- 9
- 10
- 11
+ 9
+ 10
+ 11
12{% current_theme as current_theme %}
13{% theme_dir as theme_dir %}
- 14
+ 14
15{% comment %}
--
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/1608209
Title:
manage.py not found
Status in OpenStack Dashboard (Horizon):
New
Bug description:
I've followed all instruction from OpenStack.org to setup a "All In One"
Linux server with OpenStack.
I've used Ubuntu 16.04.1 (supported) with minimal installation, then I've run
stack.sh with success. Test.sh run with success too.
Opening Horizon it fails with a very common error found a lot in literature.
I've tried some fixes with no success.
But the real strange thing is that THERE'S NO MANAGE.PY file at all to
run...
You have offline compression enabled but key
"71f1bb91aa1db46c691a399635d662c7" is missing from offline manifest. You may
need to run "python manage.py compress".
1 {% load compress %}
2 {% load themes %}
3
4
5
{% compress css %}
6
7
8 {% endcompress %}
9
10
11
12{% current_theme as current_theme %}
13{% theme_dir as theme_dir %}
14
15{% comment %}
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1608209/+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
