[Yahoo-eng-team] [Bug 1278677] Re: VMware driver should cache morefs
Hi, This has already been implemented. Please see - https://review.openstack.org/#/c/60259/ Thanks Gary ** Changed in: nova 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/1278677 Title: VMware driver should cache morefs Status in OpenStack Compute (Nova): Invalid Bug description: The VMware needs to cache morefs as much as possible throughout the codebase. This will avoid extra VC queries. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1278677/+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 1283718] [NEW] file ./etc/nova/cells.json is invalid JSON
Public bug reported: The file etc/nova/cells.json in the nova repository is invalid JSON: $ python -mjson.tool ./etc/nova/cells.json Expecting property name: line 9 column 5 (char 240) ** Affects: nova Importance: Undecided Assignee: shihanzhang (shihanzhang) Status: New -- 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/1283718 Title: file ./etc/nova/cells.json is invalid JSON Status in OpenStack Compute (Nova): New Bug description: The file etc/nova/cells.json in the nova repository is invalid JSON: $ python -mjson.tool ./etc/nova/cells.json Expecting property name: line 9 column 5 (char 240) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1283718/+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 1211338] Re: Direct vs. direct in impl_qpid
Merged to Havana stable, Grizzly stable, master.
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
Status: New = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1211338
Title:
Direct vs. direct in impl_qpid
Status in Cinder:
Fix Released
Status in OpenStack Neutron (virtual network service):
Fix Released
Status in OpenStack Compute (Nova):
Fix Released
Status in OpenStack Compute (nova) grizzly series:
New
Status in Oslo - a Library of Common OpenStack Code:
Fix Released
Bug description:
impl_qpid.py has {type: Direct} (with a capital D) in one place.
direct (lowercase) in others. It appears that qpid is case-
sensitive about exchange types, so the version with the capital D is
invalid. This ends up causing qpid to throw an error like:
/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py,
line 567, in _ewait\nself.check_error()\n', ' File
/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py,
line 556, in check_error\nraise self.error\n', 'NotFound:
not-found: Exchange type not implemented: Direct
(qpid/broker/SessionAdapter.cpp:117)(404)\n']
It should be a one-character fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1211338/+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 1269407] Re: Instance Termination delays in updating port list
** No longer affects: tempest
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1269407
Title:
Instance Termination delays in updating port list
Status in OpenStack Neutron (virtual network service):
New
Status in OpenStack Compute (Nova):
New
Bug description:
When deleting an instance, the port list is not updated immediately.
As a result - deleting net/subnet fails with error:
409-{u'NeutronError': {u'message': u'Unable to complete operation on
subnet UUID. One or more ports have an IP allocation from this
subnet.', u'type': u'SubnetInUse', u'detail': u''}}
(*) Happens only on automated scripts, since manual input isn't quick
enough to catch this.
(**) Happens only when Floating IP is attached - error doesn't happen when
Floating IP isn't used.
my guess: Nova delays in deleting the VM while checking with neutron DB that
Floating IP was deleted.
(***) nova delete command returns BEFORE instance is deleted:
nova delete $instance_id ; nova show $instance_id
will return the instance without failure
(*) might also affect Tempest during tearDown execution
Version:
openstack-nova-api-2014.1-0.5.b1.el6.noarch
openstack-nova-compute-2014.1-0.5.b1.el6.noarch
openstack-nova-scheduler-2014.1-0.5.b1.el6.noarch
openstack-nova-console-2014.1-0.5.b1.el6.noarch
openstack-nova-conductor-2014.1-0.5.b1.el6.noarch
openstack-nova-cert-2014.1-0.5.b1.el6.noarch
python-neutron-2014.1-0.1.b1.el6.noarch
openstack-neutron-2014.1-0.1.b1.el6.noarch
openstack-neutron-openvswitch-2014.1-0.1.b1.el6.noarch
How to reproduce:
script attached
assumes:
1. external network exists with floating ip range available (public)
2. image exists
Setup:
1 create network private
2. create subnet
3. create router:
3.1 set router gateway to public
3.2 set router interface to private
4. create VM
5. assign Floating IP to VM
TearDown
1. Delete / Disassociate Floating IP
2. Delete VM
3. detach router interface from subnet (router-interface-delete)
4. Delete subnet/net
Expected Result:
subnet/net should be successfully deleted.
Actual Results:
Unable to complete operation on subnet UUID. One or more ports have an IP
allocation from this subnet
409-{u'NeutronError': {u'message': u'Unable to complete operation on
subnet UUID. One or more ports have an IP allocation from this
subnet.', u'type': u'SubnetInUse', u'detail': u''}}
script log:
line 101 - VM port still in port list even though VM was deleted
line 105 - subnet fails to delete
line 117 - network successfully deleted after enough time passed for port
list to update
1 + EXT_NET_NAME=public
2 + NET_NAME=my_net
3 + SUBNET_NAME=my_subnet
4 + ROUTER_NAME=my_router
5 + SERVER_NAME=my_server
6 + IMAGE_NAME='cirros-0.3.1-x86_64-uec '
7 + MASK=54.0.0
8 + SERVER_IP=54.0.0.6
9 ++ neutron net-list
10 ++ grep public
11 ++ awk '{print $2;}'
12 + EXT_NET_ID=200a91cf-5376-4095-8722-2f247ddb01c9
13 ++ nova image-list
14 ++ grep -w ' cirros-0.3.1-x86_64-uec '
15 ++ awk '{print $2;}'
16 + IMAGE_ID=1f16b297-aeaa-4fa9-9640-269695b6eb48
17 ++ grep -w id
18 ++ neutron net-create my_net
19 ++ awk '{print $4;}'
20 + NET_ID=6ec5ef65-5279-4bbd-919a-b45a27bb31cd
21 ++ neutron subnet-create --name my_subnet
6ec5ef65-5279-4bbd-919a-b45a27bb31cd 54.0.0.0/24
22 ++ grep -w id
23 ++ awk '{print $4;}'
24 + SUBNET_ID=76abfa0f-938a-4be1-abd5-804af306fa2d
25 ++ neutron router-create my_router
26 ++ awk '{print $4;}'
27 ++ grep -w id
28 + ROUTER_ID=df211133-0513-44fc-bec5-38f9bca74025
29 + neutron router-gateway-set df211133-0513-44fc-bec5-38f9bca74025
200a91cf-5376-4095-8722-2f247ddb01c9
30 Set gateway for router df211133-0513-44fc-bec5-38f9bca74025
31 + neutron router-interface-add df211133-0513-44fc-bec5-38f9bca74025
76abfa0f-938a-4be1-abd5-804af306fa2d
32 Added interface cafd4161-f840-4c87-a80b-71b0ef374b9e to router
df211133-0513-44fc-bec5-38f9bca74025.
33 + nova boot --flavor 2 --image 1f16b297-aeaa-4fa9-9640-269695b6eb48
my_server --nic net-id=6ec5ef65-5279-4bbd-919a-b45a27bb31cd,v4-fixed-ip=54.0.0.6
34
+--+--+
35 | Property | Value
|
36
+--+--+
37 | OS-DCF:diskConfig| MANUAL
|
38 | OS-EXT-AZ:availability_zone | nova
|
39 | OS-EXT-STS:power_state | 0
|
40 | OS-EXT-STS:task_state| scheduling
|
41 | OS-EXT-STS:vm_state | building
[Yahoo-eng-team] [Bug 1282266] Re: enabled attribute missing from GET /v3/endpoints
** Also affects: tempest
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1282266
Title:
enabled attribute missing from GET /v3/endpoints
Status in OpenStack Identity (Keystone):
Triaged
Status in Tempest:
New
Bug description:
response from current master:
RESP BODY: {endpoints: [{links: {self:
http://localhost:5000/v3/endpoints/7237fc3ba1ec460595e8de463a5c7132},
url: http://localhost:35357/v3;, region: regionOne,
interface: admin, service_id:
0c8a9efdeada49d689c4d3ef29ecb3d7, id:
7237fc3ba1ec460595e8de463a5c7132}], links: {self:
http://localhost:5000/v3/endpoints;, previous: null, next: null}}
response from stable/havana (this is correct):
RESP BODY: {endpoints: [{links: {self:
http://localhost:5000/v3/endpoints/6e1b54c3423347f1bafb20030dabb412},
url: http://127.0.0.1:35357/;, region: null, enabled: true,
interface: admin, service_id:
f43f1d5cb2e04edda9316077421062c8, id:
6e1b54c3423347f1bafb20030dabb412}], links: {self:
http://localhost:5000/v3/endpoints;, previous: null, next: null}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1282266/+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 1283872] [NEW] webob.exc.HTTPForbidden can't show correct message
Public bug reported: In nova/api/ec2/__init__.py there are codes like: 154 def __call__(self, req): 155 access_key = str(req.params['AWSAccessKeyId']) 156 failures_key = authfailures-%s % access_key 157 failures = int(self.mc.get(failures_key) or 0) 158 if failures = CONF.lockout_attempts: 159 detail = _(Too many failed authentications.) 160 raise webob.exc.HTTPForbidden(detail=detail) But webob.exc.HTTPForbidden should use the 'explanation' parameter to show the error message. The source can be referred to https://github.com/Pylons/webob/blob/master/webob/exc.py#L666 ** Affects: nova Importance: Undecided Assignee: Haiwei Xu (xu-haiwei) Status: In Progress ** Changed in: nova Assignee: (unassigned) = Haiwei Xu (xu-haiwei) ** Changed in: nova Status: New = In Progress -- 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/1283872 Title: webob.exc.HTTPForbidden can't show correct message Status in OpenStack Compute (Nova): In Progress Bug description: In nova/api/ec2/__init__.py there are codes like: 154 def __call__(self, req): 155 access_key = str(req.params['AWSAccessKeyId']) 156 failures_key = authfailures-%s % access_key 157 failures = int(self.mc.get(failures_key) or 0) 158 if failures = CONF.lockout_attempts: 159 detail = _(Too many failed authentications.) 160 raise webob.exc.HTTPForbidden(detail=detail) But webob.exc.HTTPForbidden should use the 'explanation' parameter to show the error message. The source can be referred to https://github.com/Pylons/webob/blob/master/webob/exc.py#L666 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1283872/+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 1275615] Re: keystone-manage db_sync fails in a dual-stacked environment
Not a worry! Happy to work on debugging this. Going to mark this as invalid. Thanks for the report and 2x checking in on it. ** Changed in: keystone Status: Incomplete = Invalid ** Changed in: keystone Milestone: icehouse-3 = None -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1275615 Title: keystone-manage db_sync fails in a dual-stacked environment Status in OpenStack Identity (Keystone): Invalid Bug description: Hello Stackers! I'm trying to install IceHouse-2 in a dual-stacked environment (Ubuntu 14.04) but, keystone-manage db_sync doesn't work if db connection points to a IPv6 address, like this: My /etc/network/interfaces contains: --- # The loopback network interface auto lo iface lo inet loopback iface lo inet6 loopback auto eth0 # IPv6 iface eth0 inet6 static address 2001:1291::fffa:: netmask 64 gateway 2001:1291::fffa::1 # dns-* options are implemented by the resolvconf package, if installed dns-search domain.com dns-nameservers 2001:4860:4860::8844 # IPv4 iface eth0 inet static address 192.168.XX.100 netmask 24 gateway 192.168.XX.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 8.8.4.4 8.8.8.8 dns-search domain.com --- My /etc/hosts contains: --- 2001:1291::fffa::controller-1.domain.com controller-1 192.168.XX.100 controller-1.domain.com controller-1 --- MySQL binds on both IPv4 and IPv6, my.cnf have this: --- bind-address = :: --- My /etc/keystone/keystone.conf contains: --- connection = mysql://keystoneUser:keystonep...@controller-1.domain.com/keystone --- But, this way, keystone-manage db_sync does not work and, if I replace keystone.conf connection line into this: --- connection = mysql://keystoneUser:keystonep...@192.168.xx.100/keystone --- Then, keystone-manage db_sync works! So, after db_sync finishes, I return it back to the FQDN, where it resolves to IPv6 address and it works fine (keystone user-list, etc, via IPv6)... I tried it 3 times, always re-installing Ubuntu 14.04 from scratch, same result... keystone-make db_sync doesn't start its operations... I'll try again tomorrow, to see if it is just me, or not... =) Best! Thiago To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1275615/+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 1283876] [NEW] webob.exc.HTTPUnprocessableEntity can't return correct messages
Public bug reported:
In nova/api/openstack/compute/contrib/services.py there are codes like:
190 if id == disable-log-reason:
191 reason = body['disabled_reason']
192 if not self._is_valid_as_reason(reason):
193 msg = _('The string containing the reason for disabling
'
194 'the service contains invalid characters or is '
195 'too long.')
196 raise webob.exc.HTTPUnprocessableEntity(detail=msg)
But HTTPUnprocessableEntity should use 'explanation' parameter to return
the error message.
The source can be referred here:
https://github.com/Pylons/webob/blob/master/webob/exc.py#L885
** Affects: nova
Importance: Undecided
Assignee: Haiwei Xu (xu-haiwei)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) = Haiwei Xu (xu-haiwei)
** Changed in: nova
Status: New = In Progress
--
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/1283876
Title:
webob.exc.HTTPUnprocessableEntity can't return correct messages
Status in OpenStack Compute (Nova):
In Progress
Bug description:
In nova/api/openstack/compute/contrib/services.py there are codes
like:
190 if id == disable-log-reason:
191 reason = body['disabled_reason']
192 if not self._is_valid_as_reason(reason):
193 msg = _('The string containing the reason for
disabling '
194 'the service contains invalid characters or
is '
195 'too long.')
196 raise webob.exc.HTTPUnprocessableEntity(detail=msg)
But HTTPUnprocessableEntity should use 'explanation' parameter to
return the error message.
The source can be referred here:
https://github.com/Pylons/webob/blob/master/webob/exc.py#L885
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1283876/+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 1283872] Re: webob.exc.HTTPForbidden can't show correct message
** Also affects: keystone Importance: Undecided Status: New ** Changed in: keystone Assignee: (unassigned) = Haiwei Xu (xu-haiwei) ** Changed in: keystone Status: New = In Progress -- 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/1283872 Title: webob.exc.HTTPForbidden can't show correct message Status in OpenStack Identity (Keystone): In Progress Status in OpenStack Compute (Nova): In Progress Bug description: In nova/api/ec2/__init__.py there are codes like: 154 def __call__(self, req): 155 access_key = str(req.params['AWSAccessKeyId']) 156 failures_key = authfailures-%s % access_key 157 failures = int(self.mc.get(failures_key) or 0) 158 if failures = CONF.lockout_attempts: 159 detail = _(Too many failed authentications.) 160 raise webob.exc.HTTPForbidden(detail=detail) But webob.exc.HTTPForbidden should use the 'explanation' parameter to show the error message. The source can be referred to https://github.com/Pylons/webob/blob/master/webob/exc.py#L666 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1283872/+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 1283872] Re: webob.exc.HTTPForbidden can't show correct message
** Also affects: cinder Importance: Undecided Status: New ** Changed in: cinder Assignee: (unassigned) = Haiwei Xu (xu-haiwei) -- 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/1283872 Title: webob.exc.HTTPForbidden can't show correct message Status in Cinder: In Progress Status in OpenStack Identity (Keystone): In Progress Status in OpenStack Compute (Nova): In Progress Bug description: In nova/api/ec2/__init__.py there are codes like: 154 def __call__(self, req): 155 access_key = str(req.params['AWSAccessKeyId']) 156 failures_key = authfailures-%s % access_key 157 failures = int(self.mc.get(failures_key) or 0) 158 if failures = CONF.lockout_attempts: 159 detail = _(Too many failed authentications.) 160 raise webob.exc.HTTPForbidden(detail=detail) But webob.exc.HTTPForbidden should use the 'explanation' parameter to show the error message. The source can be referred to https://github.com/Pylons/webob/blob/master/webob/exc.py#L666 To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1283872/+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 1281916] Re: OpenStack cannot assign IPv6 address to instance via dnsmasq dhcpserver
** Project changed: nova = neutron ** Changed in: neutron Status: New = In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1281916 Title: OpenStack cannot assign IPv6 address to instance via dnsmasq dhcpserver Status in OpenStack Neutron (virtual network service): In Progress Bug description: Use dnsmasq as dhcp server, OpenStack deploy one instance, we found the deployed instance cannot get the targeted IPv6 address, but it can get the targeted IPv4 address. At the earlier time, I found this issue when use Vmware vcenter driver, today I also found this issue is Linux env. I use dnsmasq as dhcpv6 server, use 'tcpdump -i tap' to monitor the network data, and in deployed instance, and run dhclient -6, the result of tcpdump as below: 22:02:54.354287 IP6 fe80::f816:3eff:fe34:a80e.dhcpv6-client ff02::1:2.dhcpv6-server: dhcp6 solicit 22:02:54.354689 IP6 fe80::184d:82ff:fec4:d268.dhcpv6-server fe80::f816:3eff:fe34:a80e.dhcpv6-client: dhcp6 advertise 22:02:55.434954 IP6 fe80::f816:3eff:fe34:a80e.dhcpv6-client ff02::1:2.dhcpv6-server: dhcp6 solicit 22:02:55.435283 IP6 fe80::184d:82ff:fec4:d268.dhcpv6-server fe80::f816:3eff:fe34:a80e.dhcpv6-client: dhcp6 advertise 22:02:57.587164 IP6 fe80::f816:3eff:fe34:a80e.dhcpv6-client ff02::1:2.dhcpv6-server: dhcp6 solicit 22:02:57.587456 IP6 fe80::184d:82ff:fec4:d268.dhcpv6-server fe80::f816:3eff:fe34:a80e.dhcpv6-client: dhcp6 advertise 22:02:59.354082 IP6 fe80::184d:82ff:fec4:d268 fe80::f816:3eff:fe34:a80e: ICMP6, neighbor solicitation, who has fe80::f816:3eff:fe34:a80e, length 32 22:02:59.354922 IP6 fe80::f816:3eff:fe34:a80e fe80::184d:82ff:fec4:d268: ICMP6, neighbor advertisement, tgt is fe80::f816:3eff:fe34:a80e, length 24 from dnsmasq log, I got no address available error. The root cause is dnsmasq need to read host file, and distinguish MAC addresses from IPv6 addresses. the current host file as below: fa:16:3e:25:f4:31,host-2001-2011-0-f104--3.openstacklocal, 2001:2011:0:f104::3 We need to wrap the ipv6 address with '[]' to let dnsmasq can distinguish MAC addresses from IPv6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1281916/+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 1283909] [NEW] Internal errors happen if passing malformed body to attach_interface API
Public bug reported: Attach an interface to an instance v2 API does not validate whether necessary attribute is specified or not. The lack causes internal errors now. ** Affects: nova Importance: Undecided Assignee: Ken'ichi Ohmichi (oomichi) Status: New ** Changed in: nova Assignee: (unassigned) = Ken'ichi Ohmichi (oomichi) -- 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/1283909 Title: Internal errors happen if passing malformed body to attach_interface API Status in OpenStack Compute (Nova): New Bug description: Attach an interface to an instance v2 API does not validate whether necessary attribute is specified or not. The lack causes internal errors now. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1283909/+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 1283872] Re: webob.exc.HTTPForbidden can't show correct message
** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Assignee: (unassigned) = Haiwei Xu (xu-haiwei) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1283872 Title: webob.exc.HTTPForbidden can't show correct message Status in Cinder: In Progress Status in OpenStack Identity (Keystone): In Progress Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): In Progress Bug description: In nova/api/ec2/__init__.py there are codes like: 154 def __call__(self, req): 155 access_key = str(req.params['AWSAccessKeyId']) 156 failures_key = authfailures-%s % access_key 157 failures = int(self.mc.get(failures_key) or 0) 158 if failures = CONF.lockout_attempts: 159 detail = _(Too many failed authentications.) 160 raise webob.exc.HTTPForbidden(detail=detail) But webob.exc.HTTPForbidden should use the 'explanation' parameter to show the error message. The source can be referred to https://github.com/Pylons/webob/blob/master/webob/exc.py#L666 To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1283872/+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 1269066] Re: Call to dns related APIs are not implemented when using neutron
So rather than multiple bug reports documenting bits missing in the proxying of neutron information in Nova I think instead we should do this as a single blueprint which covers all of the different areas where we need better neutron support. Though note that the long term goal is to remove proxying of neutron information in Nova. ** Changed in: nova 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/1269066 Title: Call to dns related APIs are not implemented when using neutron Status in OpenStack Compute (Nova): Invalid Bug description: The following methods in nova.network.neutron.v2.api are not implemented (well, they throw NotImplemented exceptions) - create_private_dns_domains - create_public_dns_domains - get_dns_entries_by_address - get_dns_entries_by_name - get_dns_domains - add_dns_entry - modify_dns_entry - delete_dns_entry - delete_dns_domain To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1269066/+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 1269065] Re: Calls for basic network operations are not implemented when using neutron
So rather than multiple bug reports documenting bits missing in the proxying of neutron information in Nova I think instead we should do this as a single blueprint which covers all of the different areas where we need better neutron support. Though note that the long term goal is to remove proxying of neutron information in Nova. ** Changed in: nova 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/1269065 Title: Calls for basic network operations are not implemented when using neutron Status in OpenStack Compute (Nova): Invalid Bug description: Certain methods that are related to network lifecycle and association with projects/tenants are not implemented when using neutron. - add_project_to_network - delete - disassociate It may be unreasonable to implement these in the nova.network.neutronv2.api module, but it does have an impact on dropping in neutron as a nova-network replacement. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1269065/+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 1283943] [NEW] Update keystone docs for IceHouse release
Public bug reported: I noticed a few spots in the docs that are out of date, I'm going to list them all here, some might not be necessary. 1) Mention that ADMIN_TOKEN does not carry any authorization (we say this in sample.conf) http://docs.openstack.org/developer/keystone/configuringservices.html #admin-token 2) Tenant is used: http://docs.openstack.org/developer/keystone/configuringservices.html #setting-up-tenants-users-and-roles 3) Tenant again: http://docs.openstack.org/developer/keystone/configuringservices.html #creating-service-users 4) Should we mention #openstack-keystone: http://docs- draft.openstack.org/00/73900/4/check/gate-keystone- docs/98c168c/doc/build/html/community.html#openstack-on-freenode-irc- network 5) This seems like a good spot to mention extensions, since they are not really mentioned anywhere (except developing extensions): http://docs.openstack.org/developer/keystone/architecture.html 6) Can we condense Service API Examples Using Curl and Admin API Examples Using Curl, as they go to the same url: http://docs.openstack.org/developer/keystone/#developers-documentation 7) This contains a lot of V2 specific content: http://docs.openstack.org/developer/keystone/api_curl_examples.html (tenant is used, /tokens instead of /auth/tokens, token response contains 'access'. Not sure if we should keep two copies, or update it all to v3. 8) No mention of disable events in: http://docs.openstack.org/developer/keystone/event_notifications.html ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1283943 Title: Update keystone docs for IceHouse release Status in OpenStack Identity (Keystone): New Bug description: I noticed a few spots in the docs that are out of date, I'm going to list them all here, some might not be necessary. 1) Mention that ADMIN_TOKEN does not carry any authorization (we say this in sample.conf) http://docs.openstack.org/developer/keystone/configuringservices.html #admin-token 2) Tenant is used: http://docs.openstack.org/developer/keystone/configuringservices.html #setting-up-tenants-users-and-roles 3) Tenant again: http://docs.openstack.org/developer/keystone/configuringservices.html #creating-service-users 4) Should we mention #openstack-keystone: http://docs- draft.openstack.org/00/73900/4/check/gate-keystone- docs/98c168c/doc/build/html/community.html#openstack-on-freenode-irc- network 5) This seems like a good spot to mention extensions, since they are not really mentioned anywhere (except developing extensions): http://docs.openstack.org/developer/keystone/architecture.html 6) Can we condense Service API Examples Using Curl and Admin API Examples Using Curl, as they go to the same url: http://docs.openstack.org/developer/keystone/#developers-documentation 7) This contains a lot of V2 specific content: http://docs.openstack.org/developer/keystone/api_curl_examples.html (tenant is used, /tokens instead of /auth/tokens, token response contains 'access'. Not sure if we should keep two copies, or update it all to v3. 8) No mention of disable events in: http://docs.openstack.org/developer/keystone/event_notifications.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1283943/+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
