[Yahoo-eng-team] [Bug 1660596] Re: ValueError: Expecting property name enclosed in double quotes

2017-01-31 Thread A.Ojea
Fixed, was a problem with the policy.json Once I replaced the modified with the original one it started to work. https://raw.githubusercontent.com/openstack/keystone/stable/mitaka/etc/policy.json The error should be handled better, it tooks me a lot of hours to pinpoint the problem. **

[Yahoo-eng-team] [Bug 1660596] [NEW] ValueError: Expecting property name enclosed in double quotes

2017-01-31 Thread A.Ojea
Public bug reported: After creating some users with an script, keystone stopped to work because of the following error 2017-01-31 20:29:11.111462 2017-01-31 20:29:11.110 39594 DEBUG keystone.middleware.auth [req-5ea06271-928b-4f50-a5d6-aa60ab642852 ebaefe56b50f40e4a884e0ac713cfdc2

[Yahoo-eng-team] [Bug 1649527] Re: nova creates an invalid ethernet/bridge interface definition in virsh xml

2017-01-12 Thread A.Ojea
** Also affects: centos Importance: Undecided Status: New ** No longer affects: centos -- 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/1649527 Title: nova

[Yahoo-eng-team] [Bug 1616066] [NEW] neutron error when trying to update a bgp peer

2016-08-23 Thread A.Ojea
Public bug reported: Trying to update a bgp peer in Mitaka with midonet-plugin installed neutron throws an error. root@controller:~# neutron bgp-peer-update --name BGP-Peer22 46b91ae4-990c-4d23-9dab-905eae0ec364; tail -f /var/log/neutron/neutron-server.log Request Failed: internal server error

[Yahoo-eng-team] [Bug 1596869] Re: APIv3 compatibility broken in Mitaka and Liberty

2016-06-29 Thread A.Ojea
I see my fault now, I was supposing that "default" in liberty was the Name field and it's the ID, and in Mitaka following the docs the "default" domain is the name but the ID is an uuid randomly generated. Apologize for any inconvenience and appreciate your help @stevemar and @guang-yee. **

[Yahoo-eng-team] [Bug 1596869] [NEW] APIv3 compatibility broken in Mitaka and Liberty

2016-06-28 Thread A.Ojea
Public bug reported: Current API documentation [1] uses the fields "domain": { "id": "default" }, to select a domain. This call works in Liberty as you can see in the following snippet: curl -i -H "Content-Type: application/json" -d ' { "auth": { "identity": { "methods":