[Yahoo-eng-team] [Bug 1373761] [NEW] Better error message for attach/detach interface failed
Public bug reported: Some time we can see attach/detach interface failed, but we didn't log the detail info, that's hard to debug. for example: http://logs.openstack.org/02/111802/1/gate/gate-tempest-dsvm-neutron/eff16a6/logs/screen-n-cpu.txt.gz?#_2014-09-24_07_54_12_206 ** Affects: nova Importance: Undecided Assignee: Alex Xu (xuhj) Status: New ** Changed in: nova Assignee: (unassigned) => Alex Xu (xuhj) -- 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/1373761 Title: Better error message for attach/detach interface failed Status in OpenStack Compute (Nova): New Bug description: Some time we can see attach/detach interface failed, but we didn't log the detail info, that's hard to debug. for example: http://logs.openstack.org/02/111802/1/gate/gate-tempest-dsvm-neutron/eff16a6/logs/screen-n-cpu.txt.gz?#_2014-09-24_07_54_12_206 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1373761/+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 1373756] [NEW] Unique check in allowed address pair's extension not work well
Public bug reported:
Test this case:
Assume a port's mac_address is 12:34:56:78:aa:bb
Then put these to allowed address pair:
[{"ip_address": "10.0.0.1"},
{"ip_address": "10.0.0.2",
"mac_address": "12:34:56:78:aa:bb"}]
This can pass in extension's validator, but will cause error in db, for
mac_address is None in extension, but conver to
port's real mac_address in db.
Unit test code:
def test_update_add_none_and_own_mac_address_pairs(self):
with self.network() as net:
res = self._create_port(self.fmt, net['network']['id'])
port = self.deserialize(self.fmt, res)
mac_address = port['port']['mac_address']
address_pairs = [{'ip_address': '10.0.0.1'},
{'mac_address': mac_address,
'ip_address': '10.0.0.1'}]
update_port = {'port': {addr_pair.ADDRESS_PAIRS:
address_pairs}}
req = self.new_update_request('ports', update_port,
port['port']['id'])
res = req.get_response(self.api)
self.assertEqual(res.status_int, 400)
self._delete('ports', port['port']['id'])
** Affects: neutron
Importance: Undecided
Assignee: Wei Wang (damon-devops)
Status: New
** Description changed:
Test this case:
Assume a port's mac_address is 12:34:56:78:aa:bb
+
Then put these to allowed address pair:
[{"ip_address": "10.0.0.1"},
- {"ip_address": "10.0.0.2",
-"mac_address": "12:34:56:78:aa:bb"}]
+ {"ip_address": "10.0.0.2",
+ "mac_address": "12:34:56:78:aa:bb"}]
This can pass in extension's validator, but will cause error in db, for
mac_address is None in extension, but conver to
port's real mac_address in db.
+
Unit test code:
- def test_update_add_none_and_own_mac_address_pairs(self):
- with self.network() as net:
- res = self._create_port(self.fmt, net['network']['id'])
- port = self.deserialize(self.fmt, res)
- mac_address = port['port']['mac_address']
- address_pairs = [{'ip_address': '10.0.0.1'},
- {'mac_address': mac_address,
- 'ip_address': '10.0.0.1'}]
- update_port = {'port': {addr_pair.ADDRESS_PAIRS:
- address_pairs}}
- req = self.new_update_request('ports', update_port,
- port['port']['id'])
- res = req.get_response(self.api)
- self.assertEqual(res.status_int, 400)
- self._delete('ports', port['port']['id'])
+ def test_update_add_none_and_own_mac_address_pairs(self):
+ with self.network() as net:
+ res = self._create_port(self.fmt, net['network']['id'])
+ port = self.deserialize(self.fmt, res)
+ mac_address = port['port']['mac_address']
+ address_pairs = [{'ip_address': '10.0.0.1'},
+ {'mac_address': mac_address,
+ 'ip_address': '10.0.0.1'}]
+ update_port = {'port': {addr_pair.ADDRESS_PAIRS:
+ address_pairs}}
+ req = self.new_update_request('ports', update_port,
+ port['port']['id'])
+ res = req.get_response(self.api)
+ self.assertEqual(res.status_int, 400)
+ self._delete('ports', port['port']['id'])
** Changed in: neutron
Assignee: (unassigned) => Wei Wang (damon-devops)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1373756
Title:
Unique check in allowed address pair's extension not work well
Status in OpenStack Neutron (virtual network service):
New
Bug description:
Test this case:
Assume a port's mac_address is 12:34:56:78:aa:bb
Then put these to allowed address pair:
[{"ip_address": "10.0.0.1"},
{"ip_address": "10.0.0.2",
"mac_address": "12:34:56:78:aa:bb"}]
This can pass in extension's validator, but will cause error in db, for
mac_address is None in extension, but conver to
port's real mac_address in db.
Unit test code:
def test_update_add_none_and_own_mac_address_pairs(self):
with self.network() as net:
res = self._create_port(self.fmt, net['network']['id'])
port = self.deserialize(self.fmt, res)
mac_address = port['port']['mac_address']
address_pairs = [{'ip_address': '10.0.0.1'},
{'mac_address': mac_address,
'ip_address': '10.0.0.1'}]
update_port = {'port': {addr_pair.ADDRESS_PAIRS:
address_pairs}}
req = self.new_update_request('ports', update_port,
[Yahoo-eng-team] [Bug 1373741] [NEW] The v2.1 API links of "list versions" API doesn't show v2.1
Public bug reported:
Now v2.1 API is provided on /v2.1 URL as the default but the links does
not show v2.1 like the following:
$ curl -i 'http://192.168.11.62:8774/' -X GET -H "Accept: application/json" -H
"X-Auth-Project-Id: demo" -H "X-Auth-Token:
{SHA1}a478a30ec8bdadbdb5b8f98d97bf99ac83a8a1ea"
[..]
{"versions": [
{
"status": "CURRENT", "updated": "2011-01-21T11:33:21Z", "id": "v2.0",
"links": [{"href": "http://192.168.11.62:8774/v2/";, "rel": "self"}]
},
{
"status": "EXPERIMENTAL", "updated": "2013-07-23T11:33:21Z", "id": "v2.1",
"links": [{"href": "http://192.168.11.62:8774/v2/";, "rel": "self"}]
}
]}
The links is the same as v2 now, but the links should be
"links": [{"href": "http://192.168.11.62:8774/v2.1/";, "rel": "self"}]
ideally.
** Affects: nova
Importance: Undecided
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/1373741
Title:
The v2.1 API links of "list versions" API doesn't show v2.1
Status in OpenStack Compute (Nova):
New
Bug description:
Now v2.1 API is provided on /v2.1 URL as the default but the links
does not show v2.1 like the following:
$ curl -i 'http://192.168.11.62:8774/' -X GET -H "Accept: application/json"
-H "X-Auth-Project-Id: demo" -H "X-Auth-Token:
{SHA1}a478a30ec8bdadbdb5b8f98d97bf99ac83a8a1ea"
[..]
{"versions": [
{
"status": "CURRENT", "updated": "2011-01-21T11:33:21Z", "id": "v2.0",
"links": [{"href": "http://192.168.11.62:8774/v2/";, "rel": "self"}]
},
{
"status": "EXPERIMENTAL", "updated": "2013-07-23T11:33:21Z", "id": "v2.1",
"links": [{"href": "http://192.168.11.62:8774/v2/";, "rel": "self"}]
}
]}
The links is the same as v2 now, but the links should be
"links": [{"href": "http://192.168.11.62:8774/v2.1/";, "rel": "self"}]
ideally.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1373741/+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 1373680] [NEW] keystone fails to start on icehouse side of grenade, "error: [Errno 98] Address already in use"
Public bug reported: I know we used to have a bug for this but I can't find it anymore, so opening a new one as this failed a job: http://logs.openstack.org/84/123784/1/check/check-grenade- dsvm/0082b12/logs/old/screen-key.txt.gz#_2014-09-24_17_42_14_365 2014-09-24 17:42:14.365 32570 ERROR root [-] Failed to start the admin server 2014-09-24 17:42:14.365 32570 TRACE root Traceback (most recent call last): 2014-09-24 17:42:14.365 32570 TRACE root File "/opt/stack/old/keystone/bin/keystone-all", line 79, in serve 2014-09-24 17:42:14.365 32570 TRACE root server.start() 2014-09-24 17:42:14.365 32570 TRACE root File "/opt/stack/old/keystone/keystone/common/environment/eventlet_server.py", line 89, in start 2014-09-24 17:42:14.365 32570 TRACE root backlog=backlog) 2014-09-24 17:42:14.365 32570 TRACE root File "/usr/lib/python2.7/dist-packages/eventlet/convenience.py", line 38, in listen 2014-09-24 17:42:14.365 32570 TRACE root sock.bind(addr) 2014-09-24 17:42:14.365 32570 TRACE root File "/usr/lib/python2.7/socket.py", line 224, in meth 2014-09-24 17:42:14.365 32570 TRACE root return getattr(self._sock,name)(*args) 2014-09-24 17:42:14.365 32570 TRACE root error: [Errno 98] Address already in use 2014-09-24 17:42:14.365 32570 TRACE root ** 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/1373680 Title: keystone fails to start on icehouse side of grenade, "error: [Errno 98] Address already in use" Status in OpenStack Identity (Keystone): New Bug description: I know we used to have a bug for this but I can't find it anymore, so opening a new one as this failed a job: http://logs.openstack.org/84/123784/1/check/check-grenade- dsvm/0082b12/logs/old/screen-key.txt.gz#_2014-09-24_17_42_14_365 2014-09-24 17:42:14.365 32570 ERROR root [-] Failed to start the admin server 2014-09-24 17:42:14.365 32570 TRACE root Traceback (most recent call last): 2014-09-24 17:42:14.365 32570 TRACE root File "/opt/stack/old/keystone/bin/keystone-all", line 79, in serve 2014-09-24 17:42:14.365 32570 TRACE root server.start() 2014-09-24 17:42:14.365 32570 TRACE root File "/opt/stack/old/keystone/keystone/common/environment/eventlet_server.py", line 89, in start 2014-09-24 17:42:14.365 32570 TRACE root backlog=backlog) 2014-09-24 17:42:14.365 32570 TRACE root File "/usr/lib/python2.7/dist-packages/eventlet/convenience.py", line 38, in listen 2014-09-24 17:42:14.365 32570 TRACE root sock.bind(addr) 2014-09-24 17:42:14.365 32570 TRACE root File "/usr/lib/python2.7/socket.py", line 224, in meth 2014-09-24 17:42:14.365 32570 TRACE root return getattr(self._sock,name)(*args) 2014-09-24 17:42:14.365 32570 TRACE root error: [Errno 98] Address already in use 2014-09-24 17:42:14.365 32570 TRACE root To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1373680/+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 1373391] Re: bootstrap_datepicker/datepicker3.css' could not be found in the COMPRESS_ROOT
The issue gone after the desktop reboot
** Changed in: horizon
Status: Incomplete => Invalid
--
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/1373391
Title:
bootstrap_datepicker/datepicker3.css' could not be found in the
COMPRESS_ROOT
Status in OpenStack Dashboard (Horizon):
Invalid
Bug description:
Error during template rendering
In template
/opt/stack/horizon/openstack_dashboard/templates/_stylesheets.html, error at
line 3
'horizon/lib/bootstrap_datepicker/datepicker3.css' could not be found in the
COMPRESS_ROOT '/opt/stack/horizon/static' or with staticfiles.
1 {% load compress %}
2
3 {% compress css %}
4
5
6
7
8
9
10{% endcompress %}
11
12
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1373391/+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 1331563] Re: container does not show up after creation
Not sure if it makes sense to have "icehouse-backport-potential" on a bug that doesn't link to the master patch, we probably should find the original commit that fixed it first. In the meantime, marking as Invalid on master and opening a Icehouse task. ** Also affects: horizon/icehouse Importance: Undecided Status: New ** Changed in: horizon Status: New => Invalid -- 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/1331563 Title: container does not show up after creation Status in OpenStack Dashboard (Horizon): Invalid Status in OpenStack Dashboard (Horizon) icehouse series: New Bug description: When creating a container, the Horizon behavior is confusing. It loads you into the container, but the container is not listed. You have to backup the URL and reload to get it to show up. Our users find this very confusing. As you can see in the screen shot the URL shows that I should be inside a new container, which I am not since I can see the old ones and my new container "dude_wheres_my_container" is nowhere to be found. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1331563/+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 1373671] [NEW] SSH driver does not work with non-english locale
Public bug reported:
The SSH driver's "vmware" and "virsh" command sets contain a grep clause
which depends upon localized strings, causing this driver to be unusable
on systems with a non-english locale setting.
For vmware:
136 'list_running': (
137 "vmsvc/power.getstate {_NodeName_} | "
138 "grep 'Powered on' >/dev/null && "
139 "echo '\"{_NodeName_}\"' || true"),
For virsh:
159 'list_running': ("list --all|grep running | "
160 "awk -v qc='\"' -F\" \" '{print qc$2qc}'"),
Below is the output when the system locale is changed to "de_DE". The
translation of the unexpected error is "Error: Domain is already active".
However, any attempt to turn the node off is a no-op, because the SSH driver
does not believe the node is running.
2014-09-24 16:55:14.587 DEBUG ironic.drivers.modules.ssh [-] Checking Node:
baremetalbrbm_2's Mac address. from (pid=19417) _get_hosts_name_for_node
/opt/stack/ironic/ironic/drivers/modules/ssh.py:404
2014-09-24 16:55:14.684 DEBUG ironic.drivers.modules.ssh [-] Found Mac address:
52:54:00:de:30:e3 from (pid=19417) _get_hosts_name_for_node
/opt/stack/ironic/ironic/drivers/modules/ssh.py:417
2014-09-24 16:55:14.782 DEBUG ironic.drivers.modules.ssh [-] Cannot execute SSH
cmd /usr/bin/virsh --connect qemu:///system start baremetalbrbm_2. Reason:
Unexpected error while running command.
Command: /usr/bin/virsh --connect qemu:///system start baremetalbrbm_2
Exit code: 1
Stdout: '\n'
Stderr: 'Fehler: Domain ist bereits aktiv\n'. from (pid=19417) _ssh_execute
/opt/stack/ironic/ironic/drivers/modules/ssh.py:277
2014-09-24 16:55:14.794 WARNING ironic.conductor.manager [-] Error in deploy of
node 20770fde-b719-413d-9170-b257a76064a7: Failed to execute command via SSH:
/usr/bin/virsh --connect qemu:///system start baremetalbrbm_2.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 455,
in fire_timers
timer()
File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/timer.py", line
58, in __call__
cb(*args, **kw)
File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line
212, in main
result = function(*args, **kwargs)
File "/opt/stack/ironic/ironic/conductor/manager.py", line 504, in
_do_node_deploy
node.target_provision_state = states.NOSTATE
File "/usr/local/lib/python2.7/dist-packages/oslo/utils/excutils.py", line
82, in __exit__
six.reraise(self.type_, self.value, self.tb)
File "/opt/stack/ironic/ironic/conductor/manager.py", line 497, in
_do_node_deploy
new_state = task.driver.deploy.deploy(task)
File "/opt/stack/ironic/ironic/conductor/task_manager.py", line 116, in
wrapper
return f(*args, **kwargs)
File "/opt/stack/ironic/ironic/drivers/modules/pxe.py", line 344, in deploy
manager_utils.node_power_action(task, states.REBOOT)
File "/opt/stack/ironic/ironic/conductor/task_manager.py", line 116, in
wrapper
return f(*args, **kwargs)
File "/opt/stack/ironic/ironic/conductor/utils.py", line 118, in
node_power_action
'target': new_state, 'error': e}
File "/usr/local/lib/python2.7/dist-packages/oslo/utils/excutils.py", line
82, in __exit__
six.reraise(self.type_, self.value, self.tb)
File "/opt/stack/ironic/ironic/conductor/utils.py", line 112, in
node_power_action
task.driver.power.reboot(task)
File "/opt/stack/ironic/ironic/conductor/task_manager.py", line 116, in
wrapper
return f(*args, **kwargs)
File "/opt/stack/ironic/ironic/drivers/modules/ssh.py", line 586, in reboot
state = _power_on(ssh_obj, driver_info)
File "/opt/stack/ironic/ironic/drivers/modules/ssh.py", line 446, in _power_on
_ssh_execute(ssh_obj, cmd_to_power_on)
File "/opt/stack/ironic/ironic/drivers/modules/ssh.py", line 278, in
_ssh_execute
raise exception.SSHCommandFailed(cmd=cmd_to_exec)
SSHCommandFailed: Failed to execute command via SSH: /usr/bin/virsh --connect
qemu:///system start baremetalbrbm_2.
** Affects: ironic
Importance: High
Status: Confirmed
** Project changed: nova => ironic
** Changed in: ironic
Status: New => Confirmed
** Changed in: ironic
Importance: Undecided => High
--
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/1373671
Title:
SSH driver does not work with non-english locale
Status in OpenStack Bare Metal Provisioning Service (Ironic):
Confirmed
Bug description:
The SSH driver's "vmware" and "virsh" command sets contain a grep
clause which depends upon localized strings, causing this driver to be
unusable on systems with a non-english locale setting.
For vmware:
136 'list_running': (
137 "vmsvc/power.getstate {_NodeName_} | "
138 "grep 'Powered on' >/dev/null && "
139 "echo '\"{_Node
[Yahoo-eng-team] [Bug 1263790] Re: ipmitool does not support OPERATOR priv level
** Changed in: nova Status: Triaged => Won't Fix -- 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/1263790 Title: ipmitool does not support OPERATOR priv level Status in OpenStack Bare Metal Provisioning Service (Ironic): Fix Released Status in OpenStack Compute (Nova): Won't Fix Bug description: If the BMC / IPMI credentials being used for management of hardware were only granted OPERATOR privileges, there is no way to inform Nova's baremetal driver or Ironic's ipmitool driver to use this non- default privilege level. These will issue ipmitool commands with no "-L" parameter, resulting in privilege errors, because the default ipmitool privlvl is ADMINISTRATOR. This could be fixed by adding an optional field to store the privilege level. To manage notifications about this bug go to: https://bugs.launchpad.net/ironic/+bug/1263790/+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 1373666] [NEW] Cisco N1KV: Missing tenant id in REST call to controller
Public bug reported: Bug: Missing tenant id in the create port REST API to VSM (controller). The fix is to add the missing tenant id parameter in the REST API ** 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/1373666 Title: Cisco N1KV: Missing tenant id in REST call to controller Status in OpenStack Neutron (virtual network service): New Bug description: Bug: Missing tenant id in the create port REST API to VSM (controller). The fix is to add the missing tenant id parameter in the REST API To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1373666/+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 1373660] [NEW] An in-use dhcp port can be deleted
Public bug reported:
An in-use dhcp-port can be deleted by a tenant:
For example:
stack@Controller:~/DEVSTACK/user-1$ neutron net-list
+--+---+--+
| id | name | subnets
|
+--+---+--+
| 90b34c78-9204-4a2f-8c23-a0f8d5676b6d | public|
a90927be-72a4-47d1-8285-ba5bc403d99a |
| cdb1392e-b9a2-4d85-b736-a729235b4b82 | user-3net |
13a4c458-2c00-4da7-9f68-97b0d6a0a74b 10.1.2.0/24 |
+--+---+--+
stack@DVR-Controller:~/DEVSTACK/user-1$ neutron port-list --network-id
cdb1392e-b9a2-4d85-b736-a729235b4b82 --device_owner 'network:dhcp'
+--+--+---+-+
| id | name | mac_address | fixed_ips
|
+--+--+---+-+
| ed9bf7f4-e5df-4543-ab9c-b9a7885fed68 | | fa:16:3e:36:aa:1a |
{"subnet_id": "13a4c458-2c00-4da7-9f68-97b0d6a0a74b", "ip_address": "10.1.2.3"}
|
+--+--+---+-+
stack@Controller:~/DEVSTACK/user-1$
stack@Controller:~/DEVSTACK/user-1$ cd ../manage
stack@Controller:~/DEVSTACK/manage$ ./os_admin neutron
dhcp-agent-list-hosting-net cdb1392e-b9a2-4d85-b736-a729235b4b82
+--+++---+
| id | host | admin_state_up | alive |
+--+++---+
| 674ffd44-f4a6-4695-b24c-59ef02d9cbd8 | Controller | True | :-) |
+--+++---+
As an user of the tenant:
stack@Controller:~/DEVSTACK/manage$ neutron port-delete
ed9bf7f4-e5df-4543-ab9c-b9a7885fed68
Deleted port: ed9bf7f4-e5df-4543-ab9c-b9a7885fed68
stack@Controller:~/DEVSTACK/manage$ neutron port-list --network-id
cdb1392e-b9a2-4d85-b736-a729235b4b82 --device_owner 'network:dhcp'
stack@Controller:~/DEVSTACK/manage$
The network is still scheduled with the same dhcp agent:
stack@Controller:~/DEVSTACK/manage$ ./os_admin neutron
dhcp-agent-list-hosting-net cdb1392e-b9a2-4d85-b736-a729235b4b82
/home/stack/DEVSTACK/manage
+--+++---+
| id | host | admin_state_up | alive |
+--+++---+
| 674ffd44-f4a6-4695-b24c-59ef02d9cbd8 | Controller | True | :-) |
+--+++---+
The port deletion should not be allowed. This makes the configuration of the
qdhcp namespace on the controller node inconsistent with the databse
information. The tap device taped9bf7f4-e5 still in the namespace but
the port is no longer found in the database.
** 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/1373660
Title:
An in-use dhcp port can be deleted
Status in OpenStack Neutron (virtual network service):
New
Bug description:
An in-use dhcp-port can be deleted by a tenant:
For example:
stack@Controller:~/DEVSTACK/user-1$ neutron net-list
+--+---+--+
| id | name | subnets
|
+--+---+--+
| 90b34c78-9204-4a2f-8c23-a0f8d5676b6d | public|
a90927be-72a4-47d1-8285-ba5bc403d99a |
| cdb1392e-b9a2-4d85-b736-a729235b4b82 | user-3net |
13a4c458-2c00-4da7-9f68-97b0d6a0a74b 10.1.2.0/24 |
+--+---+--+
stack@DVR-Controller:~/DEVSTACK/user-1$ neutron port-list --network-id
cdb1392e-b9a2-4d85-b736-a729235b4b82 --device_owner 'network:dhcp'
+--+--+---+-+
| id | name | mac_address | fixed_ips
[Yahoo-eng-team] [Bug 1373652] [NEW] For redundant Arista switches do not fail L3 operations if one switch is available
Public bug reported: If Arista HW is configured in MLAG (redundancy mode), allow the L3 operation to succeed if configuration was successful on at least on one of the switches. ** 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/1373652 Title: For redundant Arista switches do not fail L3 operations if one switch is available Status in OpenStack Neutron (virtual network service): New Bug description: If Arista HW is configured in MLAG (redundancy mode), allow the L3 operation to succeed if configuration was successful on at least on one of the switches. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1373652/+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 1373651] [NEW] saved dates resets when switch to a different language
Public bug reported: The saved from and to date don't seem to be honored when switch to different language. How to reproduce: >From Admin -> Overview change the From or To date by picking up the different date, for example, today is 9/24/2014 The original From is 9/1/2014 The original To is 9/24/2014 Change From to 9/4/2014 Change To to 9/20/2014 click Submit Make sure it is saved. Click Settings -> User Settings Change select a different language, say Chinese, click save. Now the page should show some Chinese. Go back to Admin -> Overview, you will notice that the saved From date 9/4/2014 is changed to 9/1/2014, the saved To date 9/20/2014 is changed to 9/24/2014. Same issue in Project -> Overivew as well. Expected: The saved From and To dates should not get changed when switch to a different language. ** 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/1373651 Title: saved dates resets when switch to a different language Status in OpenStack Dashboard (Horizon): New Bug description: The saved from and to date don't seem to be honored when switch to different language. How to reproduce: From Admin -> Overview change the From or To date by picking up the different date, for example, today is 9/24/2014 The original From is 9/1/2014 The original To is 9/24/2014 Change From to 9/4/2014 Change To to 9/20/2014 click Submit Make sure it is saved. Click Settings -> User Settings Change select a different language, say Chinese, click save. Now the page should show some Chinese. Go back to Admin -> Overview, you will notice that the saved From date 9/4/2014 is changed to 9/1/2014, the saved To date 9/20/2014 is changed to 9/24/2014. Same issue in Project -> Overivew as well. Expected: The saved From and To dates should not get changed when switch to a different language. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1373651/+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 1190394] Re: unable to determine router-ip
*** This bug is a duplicate of bug 1255142 ***
https://bugs.launchpad.net/bugs/1255142
** This bug is no longer a duplicate of bug 1189358
non-admin user cannot see external address associated with router
** This bug has been marked a duplicate of bug 1255142
unable to get router's external IP when non admin (blocker for 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/1190394
Title:
unable to determine router-ip
Status in OpenStack Neutron (virtual network service):
New
Bug description:
if a normal tenant creates a router and then uplinks this to a network
(that is router:external). The an ip address is allocated out of that
network and assigned to the router. This ip address is then used to
nat with. Currently there is no way for this tenant to determine what
that ip address is.
As an admin you can if you run quantum router-port-list: you see:
arosen@arosen-desktop:~$ quantum router-port-list router
+--+--+---++
| id | name | mac_address | fixed_ips
|
+--+--+---++
| 3ab0e378-c0ec-4b84-b311-0c06b336fd50 | | fa:16:3e:ef:99:1a |
{"subnet_id": "743d30ec-d78f-4d77-95e6-3da764da38c8", "ip_address": "10.0.0.1"}
|
| 85061c58-1341-448d-ae89-50e316b3ccb0 | | fa:16:3e:7f:55:20 |
{"subnet_id": "4a30a2ee-65a0-4231-8d9e-b3e556b4637d", "ip_address":
"12.12.12.4"} |
| f756db1e-d32e-4cde-8cf9-e4d95959725e | | fa:16:3e:7b:04:45 |
{"subnet_id": "a5dba76f-218f-472b-b819-46b1773e54a4", "ip_address":
"169.254.169.253"} |
+--+--+---++
but as a normal tenant:
arosen@arosen-desktop:~/devstack$ quantum router-port-list router
+--+--+---+-+
| id | name | mac_address | fixed_ips
|
+--+--+---+-+
| 3ab0e378-c0ec-4b84-b311-0c06b336fd50 | | fa:16:3e:ef:99:1a |
{"subnet_id": "743d30ec-d78f-4d77-95e6-3da764da38c8", "ip_address": "10.0.0.1"}
|
+--+--+---+-+
Currently we are not storing the tenant_id for some reason on the
router-port on the otherside:
arosen@arosen-desktop:~$ quantum port-show
85061c58-1341-448d-ae89-50e316b3ccb0
+---+---+
| Field | Value
|
+---+---+
| admin_state_up| True
|
| device_id | 59880398-1d34-40c7-8cb5-92ac55b01fd6
|
| device_owner | network:router_gateway
|
| fixed_ips | {"subnet_id":
"4a30a2ee-65a0-4231-8d9e-b3e556b4637d", "ip_address": "12.12.12.4"} |
| id| 85061c58-1341-448d-ae89-50e316b3ccb0
|
| mac_address | fa:16:3e:7f:55:20
|
| name |
|
| network_id| 53d499d3-d7c7-434c-805c-04fff13e560c
|
| port_security_enabled | False
|
| queue_id |
|
| security_groups |
|
| status| ACTIVE
|
| tenant_id |
[Yahoo-eng-team] [Bug 1369514] Re: django-pyscss can't find bootstrap files from xstatic
This bug was fixed in the package python-django-pyscss - 1.0.3-0ubuntu1 --- python-django-pyscss (1.0.3-0ubuntu1) utopic; urgency=low * New upstream point release, resolving problem reading bootstrap css files in OpenStack Horizon (LP: #1369514). * Merge from Debian unstable. Remaining changes: - d/p/disable-discover-runner.patch: Drop test requirement for django-discover-runner from setup.py, fixing FTBFS in offline environments. python-django-pyscss (1.0.2-2) unstable; urgency=medium * Drop python-django-discover-runner and python-pil from depends, as it is only needed for tests. Also, python-django-discover-runner requires python-unittest2, which conflicts with horizon. python-django-pyscss (1.0.2-1) unstable; urgency=medium * New upstream release. python-django-pyscss (1.0.1-3) unstable; urgency=medium * Adds Django 1.7 compat patch (Closes: #755628). -- James PageWed, 24 Sep 2014 21:58:37 +0100 ** Changed in: python-django-pyscss (Ubuntu) Status: New => Fix Released -- 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/1369514 Title: django-pyscss can't find bootstrap files from xstatic Status in OpenStack Dashboard (Horizon): In Progress Status in “python-django-pyscss” package in Ubuntu: Fix Released Bug description: Originally reported and fixed upstream here: https://github.com/fusionbox/django-pyscss/issues/14 We need to upgrade django-pyscss to version 1.0.3 to have the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1369514/+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 1373637] [NEW] ML2 plugin does not handle failure during rollback for failed create operations
Public bug reported: During create operations for port/network/subnet in ML2 plugin (for both bulk and non bulk operations), if the crate fails, the resource is deleted in the rollback. If the deletion of the resource fails, the resource may continue to remain in the db without any indication that the resource is to be removed. One possible solution is to set the status of such a resource to ERROR under these circumstances. This bug is to track fixing this problem. ** 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/1373637 Title: ML2 plugin does not handle failure during rollback for failed create operations Status in OpenStack Neutron (virtual network service): New Bug description: During create operations for port/network/subnet in ML2 plugin (for both bulk and non bulk operations), if the crate fails, the resource is deleted in the rollback. If the deletion of the resource fails, the resource may continue to remain in the db without any indication that the resource is to be removed. One possible solution is to set the status of such a resource to ERROR under these circumstances. This bug is to track fixing this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1373637/+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 1370137] Re: pyscss can't compile bootstrap 3.2.0
This bug was fixed in the package python-pyscss - 1.2.1-0ubuntu1
---
python-pyscss (1.2.1-0ubuntu1) utopic; urgency=medium
* New upstream point release, resolving compilation failures for
bootstrap >= 3.2.0 (LP: #1370137).
* d/p/python-3.2-six.u.patch: Dropped, causes exceptions decoding Unicode
characters and is not required for Ubuntu 14.10 (LP: #1373605).
* d/control,rules: Add python{3}-{pytest,pil} to Build-Depends, execute test
suite during package build.
-- James PageWed, 24 Sep 2014 21:54:24 +0100
** Changed in: python-pyscss (Ubuntu)
Status: New => Fix Released
--
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/1370137
Title:
pyscss can't compile bootstrap 3.2.0
Status in OpenStack Dashboard (Horizon):
Fix Committed
Status in “python-pyscss” package in Ubuntu:
Fix Released
Bug description:
As reported in https://github.com/Kronuz/pyScss/issues/287
We need to upgrade pyscss as soon as this fix is released to allow unbundling
of bootstrap.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1370137/+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 1373633] [NEW] Nuage syncmanager needs information about external networks to sync sharednetworks in VSD
Public bug reported: Nuage syncmanager is able to sync an external network as a sharednetwork in VSD, if the external network is configured as gateway to the router. But in case when an external network is not configured as gateway, syncmanager has to pass information like the external netid , subnet data etc. to the backend ** Affects: neutron Importance: Undecided Assignee: Sayaji Patil (sayaji15) Status: New ** Tags: nuage ** Description changed: - Nuage syncmanager is able to sync an external network - as a sharednetwork in VSD, when the external network is configured + Nuage syncmanager is able to sync an external network + as a sharednetwork in VSD, if the external network is configured as gateway to the router. - But in case when an external network is not configured as gateway, + But in case when an external network is not configured as gateway, syncmanager needs some extra information ** Description changed: Nuage syncmanager is able to sync an external network as a sharednetwork in VSD, if the external network is configured as gateway to the router. But in case when an external network is not configured as gateway, - syncmanager needs some extra information + syncmanager needs to pass information like the external netid , + subnetid etc. to the backend ** Changed in: horizon Assignee: (unassigned) => Sayaji Patil (sayaji15) ** Project changed: horizon => neutron ** Description changed: Nuage syncmanager is able to sync an external network as a sharednetwork in VSD, if the external network is configured as gateway to the router. But in case when an external network is not configured as gateway, - syncmanager needs to pass information like the external netid , - subnetid etc. to the backend + syncmanager needs to pass information like the external netid , + subnet data etc. to the backend ** Description changed: Nuage syncmanager is able to sync an external network as a sharednetwork in VSD, if the external network is configured as gateway to the router. But in case when an external network is not configured as gateway, - syncmanager needs to pass information like the external netid , + syncmanager has to pass information like the external netid , subnet data etc. to the backend -- 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/1373633 Title: Nuage syncmanager needs information about external networks to sync sharednetworks in VSD Status in OpenStack Neutron (virtual network service): New Bug description: Nuage syncmanager is able to sync an external network as a sharednetwork in VSD, if the external network is configured as gateway to the router. But in case when an external network is not configured as gateway, syncmanager has to pass information like the external netid , subnet data etc. to the backend To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1373633/+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 1373634] [NEW] ML2 plugin bulk operations require multiple notifications being sent for sec group member updates
Public bug reported: Currently, security group member updates can be sent for individual ports and therefore bulk creates require multi notifications (one for each port if necessary). In particular in the ML2 plugin for supporting bulk port creates self.notify_security_groups_member_updated() need to be called once for each port being created. Updates can be batched to reduce traffic on the rpc bus. This bug is to track making necessary changes to accommodate this. ** 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/1373634 Title: ML2 plugin bulk operations require multiple notifications being sent for sec group member updates Status in OpenStack Neutron (virtual network service): New Bug description: Currently, security group member updates can be sent for individual ports and therefore bulk creates require multi notifications (one for each port if necessary). In particular in the ML2 plugin for supporting bulk port creates self.notify_security_groups_member_updated() need to be called once for each port being created. Updates can be batched to reduce traffic on the rpc bus. This bug is to track making necessary changes to accommodate this. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1373634/+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 1370137] Re: pyscss can't compile bootstrap 3.2.0
** Also affects: python-pyscss (Ubuntu) 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/1370137 Title: pyscss can't compile bootstrap 3.2.0 Status in OpenStack Dashboard (Horizon): Fix Committed Status in “python-pyscss” package in Ubuntu: New Bug description: As reported in https://github.com/Kronuz/pyScss/issues/287 We need to upgrade pyscss as soon as this fix is released to allow unbundling of bootstrap. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1370137/+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 1369514] Re: django-pyscss can't find bootstrap files from xstatic
** Also affects: python-django-pyscss (Ubuntu) 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/1369514 Title: django-pyscss can't find bootstrap files from xstatic Status in OpenStack Dashboard (Horizon): In Progress Status in “python-django-pyscss” package in Ubuntu: New Bug description: Originally reported and fixed upstream here: https://github.com/fusionbox/django-pyscss/issues/14 We need to upgrade django-pyscss to version 1.0.3 to have the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1369514/+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 1373599] [NEW] Trust operations in policy.json are misleading
Public bug reported:
The sample policy.json files included in Keystone have the trust API
operations listed. For example:
"identity:create_trust": "user_id:%(trust.trustor_user_id)s",
"identity:get_trust": "rule:admin_or_owner",
"identity:list_trusts": "",
"identity:list_roles_for_trust": "",
"identity:check_role_for_trust": "",
"identity:get_role_for_trust": "",
"identity:delete_trust": "",
This implies that these trust operations are protected by policy, which
is true but misleading. While policy does protect these operations,
they are hardcoded to be very restrictive. Here are some examples from
the controller code:
--
@controller.protected()
def delete_trust(self, context, trust_id):
trust = self.trust_api.get_trust(trust_id)
if not trust:
raise exception.TrustNotFound(trust_id=trust_id)
user_id = self._get_user_id(context)
_admin_trustor_only(context, trust, user_id)
self.trust_api.delete_trust(trust_id)
@controller.protected()
def list_roles_for_trust(self, context, trust_id):
trust = self.get_trust(context, trust_id)['trust']
if not trust:
raise exception.TrustNotFound(trust_id=trust_id)
user_id = self._get_user_id(context)
_trustor_trustee_only(trust, user_id)
return {'roles': trust['roles'],
'links': trust['roles_links']}
--
In the trust controller code, the following restrictions are currently
hard-coded:
create_trust - trustor only
get_trust - trustor or trustee only
l ist_trusts - admin only to list all trusts, trustor or trustee only for
related trusts
list_roles_for_trust - trustor or trustee only
check_role_for_trust - trustor or trustee only
get_role_for_trust - trustor or trustee only (indirectly via
check_role_for_trust)
delete_trust - admin or trustor only
The policies in policy.json can make these operations more restricted,
but not less restricted than the hard-coded restrictions. We can't
simply remove these settings from policy.json, as that would cause the
"default" rule to be used which makes trusts unusable in the case of the
default "default" rule of "admin_required". This only leaves us with
the option of clearly documenting the behavior IMHO. Unfortunately,
JSON doesn't allow comments, so we can't just add nice comments right
there in policy.json. I think that the correct approach is:
- Add a general purpose paragraph to the RBAC section of
doc/source/configuration.rst that states that some operations have hard-
coded restrictions that policy is unable to circumvent. Mention that
policy can still make these operations more restrictive.
- Add documentation for the trust extension at
keystone/doc/source/extensions/trust.rst that mentions the hard-coded
restrictions for each trust operation. Documentation for the trust
extension in this area is completely missing at this time.
** Affects: keystone
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1373599
Title:
Trust operations in policy.json are misleading
Status in OpenStack Identity (Keystone):
Confirmed
Bug description:
The sample policy.json files included in Keystone have the trust API
operations listed. For example:
"identity:create_trust": "user_id:%(trust.trustor_user_id)s",
"identity:get_trust": "rule:admin_or_owner",
"identity:list_trusts": "",
"identity:list_roles_for_trust": "",
"identity:check_role_for_trust": "",
"identity:get_role_for_trust": "",
"identity:delete_trust": "",
This implies that these trust operations are protected by policy,
which is true but misleading. While policy does protect these
operations, they are hardcoded to be very restrictive. Here are some
examples from the controller code:
--
@controller.protected()
def delete_trust(self, context, trust_id):
trust = self.trust_api.get_trust(trust_id)
if not trust:
raise exception.TrustNotFound(trust_id=trust_id)
user_id = self._get_user_id(context)
_admin_trustor_only(context, trust, user_id)
self.trust_api.delete_trust(trust_id)
@controller.protected()
def list_roles_for_trust(self, context, trust_id):
trust = self.get_trust(context, trust_id)['trust']
if not trust:
raise exception.TrustNotFound(trust_id=trust_id)
user_id = self._get_user_id(context)
_trustor_trustee_only(trust, user_id)
return {'roles': trust['roles'],
'links': trust['roles_links']}
--
[Yahoo-eng-team] [Bug 1372311] Re: pre-populate gateway in create network dialog
The problem with this change is that if the Network Address is modifed in this form, then the form will have to somehow know whether the Gateway IP address should be overwritten with a new default. For example, if the user has entered something specific into the Gateway IP address field, then you wouldn't want a change in Network Address to overwrite this; on the other hand, if the Gateway IP address is displaying the default address and you change the Network Address, then you would want to overwrite it. Other options should be considered for how to display the default rather than overwriting a user-editable field. Moving to Opinion status; feel free to change it if you have some way to address this. ** Tags added: ux ** Changed in: horizon Status: New => Opinion -- 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/1372311 Title: pre-populate gateway in create network dialog Status in OpenStack Dashboard (Horizon): Opinion Bug description: On the second step of Create Network dialog, the Gateway IP field acts oddly. According to the help text, to use the default value, leave it blank. If you want to not use a Gateway, check the box underneath it that says Disable Gateway. If most people just want to use the default value as I'd expect they would, it would be nice to explicitly show that value and populate the field after the user enters a Network Address. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1372311/+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 1373337] Re: Updating quotas path issue
Testing on master, I was unable to verify 2: this must be the tenant uuid. Bear in mind that this is an admin only operation. As for 1. I believe this should be rectified in the documentation. ** Changed in: neutron Status: New => Incomplete ** Also affects: openstack-manuals Importance: Undecided Status: New ** Tags added: icehouse-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1373337 Title: Updating quotas path issue Status in OpenStack Neutron (virtual network service): Incomplete Status in OpenStack Manuals: New Bug description: In the docs (http://developer.openstack.org/api-ref-networking-v2.html #quotas-ext), it clearly says that to update quota values, the request should be: PUT /v2.0/quotas But I'm getting a 404 when you do this. If you do this instead: PUT /v2.0/quotas/foo it works as expected, where "foo" can literally be anything. I looked at how the python-neutronclient handles this, and they seem to append the tenant_id to the end - which is completely undocumented. So: 1. Is this a bug with the Neutron API or with the Neutron docs? 2. Why does any arbitrary string get accepted? I'm using Neutron on devstack, Icehouse release. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1373337/+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 1373417] Re: can't update ipv6-ra-mode and ipv6-address-mode due to invalid ip version exception
Hang on, what's the state of the subnet prior to the update? ** Changed in: python-neutronclient Status: In Progress => Incomplete ** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Assignee: (unassigned) => Baodong (Robert) Li (baoli) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1373417 Title: can't update ipv6-ra-mode and ipv6-address-mode due to invalid ip version exception Status in OpenStack Neutron (virtual network service): New Status in Python client library for Neutron: Incomplete Bug description: $ neutron subnet-update --ipv6-ra-mode dhcpv6-stateful ipv6-private-subnet 'Namespace' object has no attribute 'ip_version' To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1373417/+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 1373547] [NEW] Cisco N1kv: Remove unnecessary REST call to delete VM network on controller
Public bug reported: Remove the rest call to delete vm network on the controller and ensure that database remains consistent. ** Affects: neutron Importance: Undecided Assignee: Abhishek Raut (abhraut) Status: New ** Tags: cisco ** Changed in: neutron Assignee: (unassigned) => Abhishek Raut (abhraut) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1373547 Title: Cisco N1kv: Remove unnecessary REST call to delete VM network on controller Status in OpenStack Neutron (virtual network service): New Bug description: Remove the rest call to delete vm network on the controller and ensure that database remains consistent. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1373547/+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 1239481] Re: nova baremetal requires manual neutron setup for metadata access
** Also 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/1239481 Title: nova baremetal requires manual neutron setup for metadata access Status in OpenStack Bare Metal Provisioning Service (Ironic): New Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): Won't Fix Status in tripleo - openstack on openstack: Triaged Bug description: a subnet setup with host routes can use a bare metal gateway as long as there is a metadata server on the same network: neutron subnet-create ... (network, dhcp settings etc) host_routes type=dict list=true destination=169.254.169.254/32,nexthop= --gateway_ip= But this requires manual configuration - it would be nice if nova could configure this as part of bringing up the network for a given node. To manage notifications about this bug go to: https://bugs.launchpad.net/ironic/+bug/1239481/+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 1373535] [NEW] obj_make_compatible is wrong
Public bug reported: Commit 7cdfdccf1bb936d559bd3e247094a817bb3c03f4 attempted to make the obj_make_compatible calls consistent, but it actually changed them the wrong way. Change https://review.openstack.org/#/c/121663/ addresses the bug but is sitting on top of a change that might be too risky at this point for juno-rc1, so this should be a separate fix. ** Affects: nova Importance: High Status: Triaged ** Tags: unified-objects ** Changed in: nova Status: New => Triaged ** Changed in: nova Importance: Undecided => High -- 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/1373535 Title: obj_make_compatible is wrong Status in OpenStack Compute (Nova): Triaged Bug description: Commit 7cdfdccf1bb936d559bd3e247094a817bb3c03f4 attempted to make the obj_make_compatible calls consistent, but it actually changed them the wrong way. Change https://review.openstack.org/#/c/121663/ addresses the bug but is sitting on top of a change that might be too risky at this point for juno-rc1, so this should be a separate fix. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1373535/+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 1373525] [NEW] Pass instance's name to neutron
Public bug reported: Nova, while creating or updating port for an instance, does not pass name to the port's request body. Though, device-id is set as VM's uuid it would help to pass the name along with it for the ease of corelating port with the instance. Instance's name will be the port's new name and it will be easier to corelate them. ** Affects: nova Importance: Undecided 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/1373525 Title: Pass instance's name to neutron Status in OpenStack Compute (Nova): New Bug description: Nova, while creating or updating port for an instance, does not pass name to the port's request body. Though, device-id is set as VM's uuid it would help to pass the name along with it for the ease of corelating port with the instance. Instance's name will be the port's new name and it will be easier to corelate them. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1373525/+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 1373524] [NEW] dvr snat delete binding changed
Public bug reported: Recent changes in the l3 plugin related to dvr snat binding has changed how the binding is sent to the l3-agent. This patch changes the l3-agent to properly handle the external gateway clear/delete cases. SNAT namespaces will not be deleted in all cases without this fix. ** Affects: neutron Importance: Undecided Assignee: Mike Smith (michael-smith6) Status: New ** Tags: l3-dvr-backlog ** Tags added: l3-dvr-backlog ** Changed in: neutron Assignee: (unassigned) => Mike Smith (michael-smith6) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1373524 Title: dvr snat delete binding changed Status in OpenStack Neutron (virtual network service): New Bug description: Recent changes in the l3 plugin related to dvr snat binding has changed how the binding is sent to the l3-agent. This patch changes the l3-agent to properly handle the external gateway clear/delete cases. SNAT namespaces will not be deleted in all cases without this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1373524/+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 1365961] Re: Dangerous iptables rule generated in case of protocol "any" and source-port/destination-port usage
The security note for this issue has been published as OSSN-0029: https://wiki.openstack.org/wiki/OSSN/OSSN-0029 ** Changed in: ossn Status: In Progress => 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/1365961 Title: Dangerous iptables rule generated in case of protocol "any" and source-port/destination-port usage Status in OpenStack Neutron (virtual network service): Fix Committed Status in OpenStack Security Advisories: Won't Fix Status in OpenStack Security Notes: Fix Released Bug description: Icehouse 2014.1.2, FWaas using iptables driver In order to allow DNS (TCP and UDP) request, the following rule was defined: neutron firewall-rule-create --protocol any --destination-port 53 --action allow On L3agent namespace this has been translated in the following iptables rules: -A neutron-l3-agent-iv441c58eb2 -j ACCEPT -A neutron-l3-agent-ov441c58eb2 -j ACCEPT => there is no restriction on the destination port(53), like we could expect it !!! There is 2 solutions to handle this issue: 1) Doesn't allow user to create a rule specifing protocol "any" AND a source-port/destination-port. 2) Generating the following rules (like some firewalls do): -A neutron-l3-agent-iv441c58eb2 -p tcp -m tcp --dport 53 -j ACCEPT -A neutron-l3-agent-iv441c58eb2 -p udp -m udp --dport 53 -j ACCEPT -A neutron-l3-agent-ov441c58eb2 -p tcp -m tcp --dport 53 -j ACCEPT -A neutron-l3-agent-ov441c58eb2 -p udp -m udp --dport 53 -j ACCEPT => TCP and UDP have been completed. The source code affected is located in neutron/services/firewall/drivers/linux/iptables_fwaas.py (L268) def _port_arg(self, direction, protocol, port): if not (protocol in ['udp', 'tcp'] and port): return '' return '--%s %s' % (direction, port) => trunk code is affected too. Nota: This is not a real Neutron security vulnerability but it is a real security vulnerability for applications living in the Openstack cloud... That's why I tagged it as "security vulnerability" Regards, To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1365961/+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 1373502] [NEW] tenant list needs to sorted alphabetically , else need proper search mechanism
Public bug reported: 1. Login to DevStack as admin 2. Go to Identity->Projects 3. Observe that tenant list is not sorted It will be difficult for user/admin to search for specific tenant, if it is not sorted list or there no mechanism to search the tenant. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: "tenants.docx" https://bugs.launchpad.net/bugs/1373502/+attachment/4213773/+files/tenants.docx -- 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/1373502 Title: tenant list needs to sorted alphabetically , else need proper search mechanism Status in OpenStack Dashboard (Horizon): New Bug description: 1. Login to DevStack as admin 2. Go to Identity->Projects 3. Observe that tenant list is not sorted It will be difficult for user/admin to search for specific tenant, if it is not sorted list or there no mechanism to search the tenant. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1373502/+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 1373491] [NEW] feature request: option to run user-data as non-root
Public bug reported: We have a use case where we want to offer users cloudable services (AWS, Openstack), but *without* the possiblity of getting root access. We can lock down an instance of course, by denying root logins and removing the instance user from sudo, or restricting the rules. But we'd like to still allow user-controlled user-data. The idea is that a user might boot a machine with user-data that say, wget's a .war into the tomcat directory, or changes a configuration file that isn't system- wide. Or even bootstraps their $HOME/.bashrc, etc. files. Right now, the user-data option is going to run everything as root, meaning they must specifically fixup ownership and permissions, not the mention that they could do really whatever they want. My proposal would therefore be some sort of option, like user-data- account: www. If not specified, it defaults to root. ** Affects: cloud-init Importance: Undecided Status: New ** Tags: user-data -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1373491 Title: feature request: option to run user-data as non-root Status in Init scripts for use on cloud images: New Bug description: We have a use case where we want to offer users cloudable services (AWS, Openstack), but *without* the possiblity of getting root access. We can lock down an instance of course, by denying root logins and removing the instance user from sudo, or restricting the rules. But we'd like to still allow user-controlled user-data. The idea is that a user might boot a machine with user-data that say, wget's a .war into the tomcat directory, or changes a configuration file that isn't system-wide. Or even bootstraps their $HOME/.bashrc, etc. files. Right now, the user-data option is going to run everything as root, meaning they must specifically fixup ownership and permissions, not the mention that they could do really whatever they want. My proposal would therefore be some sort of option, like user-data- account: www. If not specified, it defaults to root. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1373491/+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 1373478] [NEW] filter scheduler makes invalid assumption of monotonicity
Public bug reported: The current filter scheduler handles the scheduling of a homogenous batch of N instances with a loop that assumes that a host ruled out in one iteration can not be desirable in a later iteration --- but that is a false assumption. Consider the case of a filter whose purpose is to achieve balance across some sort of areas. These might be AZs, host aggregates, racks, whatever. Consider a request to schedule 4 identical instances; suppose that there are two hosts, one in each of two different areas, initially hosting nothing. For the first iteration, both hosts pass this filter. One gets picked, call it host A. On the second iteration, only the other host (call it B) passes the filter. So the second instance goes on B. On the third iteration, both hosts would pass the filter but the filter is only asked about host B. So the third instance goes on B. On the fourth iteration, host B is unacceptable but that is the only host about which the filter is asked. So the scheduling fails with a complaint about no acceptable host found. ** Affects: nova Importance: Undecided 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/1373478 Title: filter scheduler makes invalid assumption of monotonicity Status in OpenStack Compute (Nova): New Bug description: The current filter scheduler handles the scheduling of a homogenous batch of N instances with a loop that assumes that a host ruled out in one iteration can not be desirable in a later iteration --- but that is a false assumption. Consider the case of a filter whose purpose is to achieve balance across some sort of areas. These might be AZs, host aggregates, racks, whatever. Consider a request to schedule 4 identical instances; suppose that there are two hosts, one in each of two different areas, initially hosting nothing. For the first iteration, both hosts pass this filter. One gets picked, call it host A. On the second iteration, only the other host (call it B) passes the filter. So the second instance goes on B. On the third iteration, both hosts would pass the filter but the filter is only asked about host B. So the third instance goes on B. On the fourth iteration, host B is unacceptable but that is the only host about which the filter is asked. So the scheduling fails with a complaint about no acceptable host found. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1373478/+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 1373430] Re: Error while compressing files
** 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/1373430 Title: Error while compressing files Status in OpenStack Dashboard (Horizon): New Status in tripleo - openstack on openstack: Triaged Bug description: All ci jobs failing Earliest Failure : 2014-09-24 09:51:55 UTC Example : http://logs.openstack.org/50/123150/3/check-tripleo/check-tripleo-ironic-undercloud-precise-nonha/3c60b32/console.html Sep 24 11:51:43 overcloud-controller0-dxjfgv3agarr os-collect-config[724]: dib-run-parts Wed Sep 24 11:51:43 UTC 2014 Running /opt/stack/os-config-refresh/post-configure.d/14-horizon Sep 24 11:51:53 overcloud-controller0-dxjfgv3agarr os-collect-config[724]: CommandError: An error occured during rendering /opt/stack/venvs/openstack/lib/python2.7/site-packages/horizon/templates/horizon/_scripts.html: 'horizon/lib/bootstrap_datepicker/locales/bootstrap-datepicker..js' could not be found in the COMPRESS_ROOT '/opt/stack/venvs/openstack/lib/python2.7/site-packages/openstack_dashboard/static' or with staticfiles. Sep 24 11:51:53 overcloud-controller0-dxjfgv3agarr os-collect-config[724]: Found 'compress' tags in: Sep 24 11:51:53 overcloud-controller0-dxjfgv3agarr os-collect-config[724]: /opt/stack/venvs/openstack/lib/python2.7/site-packages/horizon/templates/horizon/_scripts.html Sep 24 11:51:53 overcloud-controller0-dxjfgv3agarr os-collect-config[724]: /opt/stack/venvs/openstack/lib/python2.7/site-packages/horizon/templates/horizon/_conf.html Sep 24 11:51:53 overcloud-controller0-dxjfgv3agarr os-collect-config[724]: /opt/stack/venvs/openstack/lib/python2.7/site-packages/openstack_dashboard/templates/_stylesheets.html Sep 24 11:51:53 overcloud-controller0-dxjfgv3agarr os-collect-config[724]: Compressing... [2014-09-24 11:51:53,459] (os-refresh-config) [ERROR] during post-configure phase. [Command '['dib-run-parts', '/opt/stack/os-config-refresh/post-configure.d']' returned non-zero exit status 1] To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1373430/+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 1373454] [NEW] glance-api raises 500 error for invalid scheme while creating image
Public bug reported: glance-api raises 500 error for invalid scheme while creating image using v1 api in get_store_or_400() method. The reason, in this method exception.UnknownScheme() exception is caught and this UnknownScheme exception class is not present in glance/common/excepion.py module as it is moved under glance_store project. Ideally it should caught UnknownScheme exception from glance_store's exception module. Stacktrace on glance-api screen: 2014-09-24 07:06:38.868 31867 INFO glance.wsgi.server [e03c9dff-5213-4b05-9958-9b53d404c419 8264cb3f7ed04408ad6df9f6741f5be2 be4a5d48cbb748be923182b30ec ed78c - - -] Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py", line 434, in handle_one_response result = self.application(self.environ, start_response) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__ resp = self.call_func(req, *args, **self.kwargs) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func return self.func(req, *args, **kwargs) File "/opt/stack/glance/glance/common/wsgi.py", line 394, in __call__ response = req.get_response(self.application) File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1320, in send application, catch_exc_info=False) File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1284, in call_application app_iter = application(self.environ, start_response) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__ resp = self.call_func(req, *args, **self.kwargs) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func return self.func(req, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/osprofiler/web.py", line 106, in __call__ return request.get_response(self.application) File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1320, in send application, catch_exc_info=False) File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1284, in call_application app_iter = application(self.environ, start_response) File "/usr/local/lib/python2.7/dist-packages/keystonemiddleware/auth_token.py", line 559, in __call__ return self._app(env, start_response) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__ resp = self.call_func(req, *args, **self.kwargs) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func return self.func(req, *args, **kwargs) File "/opt/stack/glance/glance/common/wsgi.py", line 394, in __call__ response = req.get_response(self.application) File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1320, in send application, catch_exc_info=False) File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1284, in call_application app_iter = application(self.environ, start_response) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__ resp = self.call_func(req, *args, **self.kwargs) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func return self.func(req, *args, **kwargs) File "/opt/stack/glance/glance/common/wsgi.py", line 394, in __call__ response = req.get_response(self.application) File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1320, in send application, catch_exc_info=False) File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1284, in call_application app_iter = application(self.environ, start_response) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__ resp = self.call_func(req, *args, **self.kwargs) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func return self.func(req, *args, **kwargs) File "/opt/stack/glance/glance/common/wsgi.py", line 394, in __call__ response = req.get_response(self.application) File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1320, in send application, catch_exc_info=False) File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1284, in call_application app_iter = application(self.environ, start_response) File "/usr/lib/python2.7/dist-packages/paste/urlmap.py", line 206, in __call__ return app(environ, start_response) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ return resp(environ, start_response) File "/usr/local/lib/python2.7/dist-packages/routes/middleware.py", line 131, in __call__ response = self.app(environ, start_response) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__ return resp(environ, start_response) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__ resp = self.call_func(req, *args, **self.kwargs) File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func return self.func(req, *args, **kwargs) File "/opt/stack/glance/glance/common/w
[Yahoo-eng-team] [Bug 1373439] [NEW] Django models.py bug already fixed
Public bug reported: In this file https://github.com/openstack/horizon/blob/master/horizon/models.py#L20 we have this message: "Stub file to work around django bug: https://code.djangoproject.com/ticket/7198"; And this bug was already fixed, so, in my opinion, we should to improve this models.py ** 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/1373439 Title: Django models.py bug already fixed Status in OpenStack Dashboard (Horizon): New Bug description: In this file https://github.com/openstack/horizon/blob/master/horizon/models.py#L20 we have this message: "Stub file to work around django bug: https://code.djangoproject.com/ticket/7198"; And this bug was already fixed, so, in my opinion, we should to improve this models.py To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1373439/+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 1373414] [NEW] Icehouse Glance starts but does not listen - doesn't bind to configured port 9292
Public bug reported:
Ubuntu 14.04.1 LTS, all configured as described in the official
installation guide up to "Install the Image service" section.
service glance-api start
and
service glance-registry start
report NO errors.
Relevant processes are confirmed running.
But neither is listening to port 9292, and so image-create in next
section of the Installation Guide ("Verify the Identity Service
installation") obviously fails with
[Errno 111] Connection refused
Meanwhile, in /var/log/glance/api.log, a block of traces repeats endlessly.
The block contains plenty of warnings but one Error and one Critical worth
attention
2014-09-24 08:35:42.527 21646 ERROR glance.store.sheepdog [-] Error in store
configuration: [Errno 2] No such file or directory
2014-09-24 08:35:42.534 21646 WARNING glance.store.base [-] Failed to configure
store correctly: Store sheepdog could not be configured correctly. Reason:
Error in store configuration: [Errno 2] No such file or directory Disabling add
method.
2014-09-24 08:35:42.537 21646 WARNING glance.store [-] Deprecated:
glance.store.sheepdog.Store not found in `known_store`. Stores need to be
explicitly enabled in the configuration file.
2014-09-24 08:35:42.552 21646 WARNING glance.store [-] Deprecated:
glance.store.rbd.Store not found in `known_store`. Stores need to be explicitly
enabled in the configuration file.
2014-09-24 08:35:42.561 21646 WARNING glance.store.base [-] Failed to configure
store correctly: Store gridfs could not be configured correctly. Reason:
Missing dependencies: pymongo Disabling add method.
2014-09-24 08:35:42.564 21646 WARNING glance.store [-] Deprecated:
glance.store.gridfs.Store not found in `known_store`. Stores need to be
explicitly enabled in the configuration file.
2014-09-24 08:35:42.998 21646 WARNING glance.store.base [-] Failed to configure
store correctly: Store cinder could not be configured correctly. Reason: Cinder
storage requires a context. Disabling add method.
2014-09-24 08:35:43.002 21646 WARNING glance.store [-] Deprecated:
glance.store.cinder.Store not found in `known_store`. Stores need to be
explicitly enabled in the configuration file.
2014-09-24 08:35:43.036 21646 WARNING glance.store [-] Deprecated:
glance.store.swift.Store not found in `known_store`. Stores need to be
explicitly enabled in the configuration file.
2014-09-24 08:35:43.152 21646 WARNING glance.store [-] Deprecated:
glance.store.vmware_datastore.Store not found in `known_store`. Stores need to
be explicitly enabled in the configuration file.
2014-09-24 08:35:43.164 21646 WARNING glance.store [-] Deprecated:
glance.store.s3.Store not found in `known_store`. Stores need to be explicitly
enabled in the configuration file.
2014-09-24 08:35:44.287 21646 WARNING keystoneclient.middleware.auth_token [-]
This middleware module is deprecated as of v0.10.0 in favor of
keystonemiddleware.auth_token - please update your WSGI pipeline to reference
the new middleware package.
2014-09-24 08:35:44.291 21646 CRITICAL glance [-] AttributeError: 'StrOpt'
object has no attribute 'type'
The CRITICAL error is raised from deep within
/usr/local/lib/python2.7/dist-packages/keystoneclient/middleware/auth_token.py
where the statement
opt_types = dict((o.dest, o.type) for o in opts)
fails. My guess is this must be a syntax error in some config file, leading to
wrong/corrupt opts, which causes dict(..) call to fail.
However I edited the config files exactly as described in the guide.
No applicable/relevant comment found on the web for this error message and
CRITICAL condition.
As for the ERROR, it is caused by collie not found. Installing sheepdog
the error changes: now collie is found, but it now dislikes "localhost"
as ip address. Which of the "localhost" strings that are spread over the
Glance-related config files ? I didn't change them, and this guide is
not requiring to change localhost to another string, so I was assuming
these default config files were ok.
Most importantly, as per the official installation guide, following the
instructions was supposed to result in setting up a plain file-based
storage. Is sheepdog involved in this storage model, or is it activated
by mistake? (again, I didn't change any sheepdog-related option in the
Glance config files).
** Affects: glance
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/1373414
Title:
Icehouse Glance starts but does not listen - doesn't bind to
configured port 9292
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
Ubuntu 14.04.1 LTS, all configured as described in the official
installation guide up to "Install the Image service" section.
service glance-api start
and
service glance-registry start
report NO errors.
Relevant processes are confirmed running.
But neither i
[Yahoo-eng-team] [Bug 1373410] [NEW] Can't update ipv6-ra-mode or ipv6-address-mode for a ipv6 subnet
Public bug reported:
$ neutron subnet-create --ip-version 6 --name mysub --ipv6-ra-mode slaac
private 2001:1::/64
Created a new subnet:
+---+--+
| Field | Value
|
+---+--+
| allocation_pools | {"start": "2001:1::2", "end":
"2001:1:::::fffe"} |
| cidr | 2001:1::/64
|
| dns_nameservers |
|
| enable_dhcp | True
|
| gateway_ip| 2001:1::1
|
| host_routes |
|
| id| d767b839-1258-4282-b5db-816024d14d7d
|
| ip_version| 6
|
| ipv6_address_mode |
|
| ipv6_ra_mode | slaac
|
| name | mysub
|
| network_id| 145596e3-8098-48c1-98c7-4ba04242090d
|
| tenant_id | 358c86130343491696987e1bffe9cb12
|
+---+--+
$ neutron subnet-update --ipv6-ra-mode dhcpv6-stateful mysub
Invalid input for operation: ipv6_ra_mode set to 'dhcpv6-stateful' with
ipv6_address_mode set to 'None' is not valid. If both attributes are set, they
must be the same value. (HTTP 400) (Request-ID:
req-7f2982c7-b124-4b14-9284-6e0cc889dd28)
** Affects: neutron
Importance: Undecided
Assignee: Baodong (Robert) Li (baoli)
Status: Confirmed
** Changed in: neutron
Status: New => Confirmed
** Changed in: neutron
Assignee: (unassigned) => Baodong (Robert) Li (baoli)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1373410
Title:
Can't update ipv6-ra-mode or ipv6-address-mode for a ipv6 subnet
Status in OpenStack Neutron (virtual network service):
Confirmed
Bug description:
$ neutron subnet-create --ip-version 6 --name mysub --ipv6-ra-mode slaac
private 2001:1::/64
Created a new subnet:
+---+--+
| Field | Value
|
+---+--+
| allocation_pools | {"start": "2001:1::2", "end":
"2001:1:::::fffe"} |
| cidr | 2001:1::/64
|
| dns_nameservers |
|
| enable_dhcp | True
|
| gateway_ip| 2001:1::1
|
| host_routes |
|
| id| d767b839-1258-4282-b5db-816024d14d7d
|
| ip_version| 6
|
| ipv6_address_mode |
|
| ipv6_ra_mode | slaac
|
| name | mysub
|
| network_id| 145596e3-8098-48c1-98c7-4ba04242090d
|
| tenant_id | 358c86130343491696987e1bffe9cb12
|
+---+--+
$ neutron subnet-update --ipv6-ra-mode dhcpv6-stateful mysub
Invalid input for operation: ipv6_ra_mode set to 'dhcpv6-stateful' with
ipv6_address_mode set to 'None' is not valid. If both attributes are set, they
must be the same value. (HTTP 400) (Request-ID:
req-7f2982c7-b124-4b14-9284-6e0cc889dd28)
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1373410/+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 1373391] [NEW] bootstrap_datepicker/datepicker3.css' could not be found in the COMPRESS_ROOT
Public bug reported:
Error during template rendering
In template /opt/stack/horizon/openstack_dashboard/templates/_stylesheets.html,
error at line 3
'horizon/lib/bootstrap_datepicker/datepicker3.css' could not be found in the
COMPRESS_ROOT '/opt/stack/horizon/static' or with staticfiles.
1 {% load compress %}
2
3 {% compress css %}
4
5
6
7
8
9
10 {% endcompress %}
11
12
** 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/1373391
Title:
bootstrap_datepicker/datepicker3.css' could not be found in the
COMPRESS_ROOT
Status in OpenStack Dashboard (Horizon):
New
Bug description:
Error during template rendering
In template
/opt/stack/horizon/openstack_dashboard/templates/_stylesheets.html, error at
line 3
'horizon/lib/bootstrap_datepicker/datepicker3.css' could not be found in the
COMPRESS_ROOT '/opt/stack/horizon/static' or with staticfiles.
1 {% load compress %}
2
3 {% compress css %}
4
5
6
7
8
9
10{% endcompress %}
11
12
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1373391/+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 1306559] Re: Fix python26 compatibility for RFCSysLogHandler
** Changed in: murano Status: Fix Committed => 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/1306559 Title: Fix python26 compatibility for RFCSysLogHandler Status in Cinder: Confirmed Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in OpenStack Identity (Keystone): Confirmed Status in Murano: Fix Released Status in OpenStack Neutron (virtual network service): Confirmed Bug description: Currently used pattern https://review.openstack.org/#/c/63094/15/openstack/common/log.py (lines 471-479) will fail for Python 2.6.x. In order to fix the broken Python 2.6.x compatibility, old style explicit superclass method calls should be used instead. Here is an example of how to check this for Python v2.7 and v2.6: import logging.handlers print type(logging.handlers.SysLogHandler) print type(logging.Handler) Results would be: Python 2.7: , so super() may be used for RFCSysLogHandler(logging.handlers.SysLogHandler) Python 2.6:, so super() may *NOT* be used for RFCSysLogHandler(logging.handlers.SysLogHandler) To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1306559/+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 1373359] [NEW] Vxlan UDP port is not updated in db
Public bug reported:
The value for Vxlan UDP port should be changed in ml2_vxlan_endpoints table
according to the values configured in ml2_conf.ini at L2 agent side.
VXLAN_UDP_PORT = 4789
def add_endpoint(self, ip, udp_port=VXLAN_UDP_PORT):
LOG.debug(_("add_vxlan_endpoint() called for ip %s"), ip)
** Affects: neutron
Importance: Undecided
Assignee: Romil Gupta (romilg)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Romil Gupta (romilg)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1373359
Title:
Vxlan UDP port is not updated in db
Status in OpenStack Neutron (virtual network service):
New
Bug description:
The value for Vxlan UDP port should be changed in ml2_vxlan_endpoints table
according to the values configured in ml2_conf.ini at L2 agent side.
VXLAN_UDP_PORT = 4789
def add_endpoint(self, ip, udp_port=VXLAN_UDP_PORT):
LOG.debug(_("add_vxlan_endpoint() called for ip %s"), ip)
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1373359/+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 1373337] [NEW] Updating quotas path issue
Public bug reported: In the docs (http://developer.openstack.org/api-ref-networking-v2.html #quotas-ext), it clearly says that to update quota values, the request should be: PUT /v2.0/quotas But I'm getting a 404 when you do this. If you do this instead: PUT /v2.0/quotas/foo it works as expected, where "foo" can literally be anything. I looked at how the python-neutronclient handles this, and they seem to append the tenant_id to the end - which is completely undocumented. So: 1. Is this a bug with the Neutron API or with the Neutron docs? 2. Why does any arbitrary string get accepted? I'm using Neutron on devstack, Icehouse release. ** 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/1373337 Title: Updating quotas path issue Status in OpenStack Neutron (virtual network service): New Bug description: In the docs (http://developer.openstack.org/api-ref-networking-v2.html #quotas-ext), it clearly says that to update quota values, the request should be: PUT /v2.0/quotas But I'm getting a 404 when you do this. If you do this instead: PUT /v2.0/quotas/foo it works as expected, where "foo" can literally be anything. I looked at how the python-neutronclient handles this, and they seem to append the tenant_id to the end - which is completely undocumented. So: 1. Is this a bug with the Neutron API or with the Neutron docs? 2. Why does any arbitrary string get accepted? I'm using Neutron on devstack, Icehouse release. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1373337/+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 1373333] [NEW] glance-replicator livecopy cannot work due to Bad header: x-image-meta-virtual-size
Public bug reported:
I would like to use "glance-replicator livecopy" command to replicate
the images from one openstack instance to anthor, it goes to error while
running the livecopy command:
2014-09-24 17:32:09.082 24953 CRITICAL glance [-] ServerErrorException:
400 Bad Request
The server could not comply with the request since it is either
malformed or otherwise incorrect.
Bad header: x-image-meta-virtual-size
2014-09-24 17:32:09.082 24953 TRACE glance Traceback (most recent call last):
2014-09-24 17:32:09.082 24953 TRACE glance File "/usr/bin/glance-replicator",
line 10, in
2014-09-24 17:32:09.082 24953 TRACE glance sys.exit(main())
2014-09-24 17:32:09.082 24953 TRACE glance File
"/usr/lib/python2.6/site-packages/glance/cmd/replicator.py", line 739, in main
2014-09-24 17:32:09.082 24953 TRACE glance command(options, args)
2014-09-24 17:32:09.082 24953 TRACE glance File
"/usr/lib/python2.6/site-packages/glance/cmd/replicator.py", line 516, in
replication_livecopy
2014-09-24 17:32:09.082 24953 TRACE glance image_response)
2014-09-24 17:32:09.082 24953 TRACE glance File
"/usr/lib/python2.6/site-packages/glance/cmd/replicator.py", line 238, in
add_image
2014-09-24 17:32:09.082 24953 TRACE glance response =
self._http_request('POST', url, headers, image_data)
2014-09-24 17:32:09.082 24953 TRACE glance File
"/usr/lib/python2.6/site-packages/glance/cmd/replicator.py", line 125, in
_http_request
2014-09-24 17:32:09.082 24953 TRACE glance raise
ServerErrorException(response.read())
2014-09-24 17:32:09.082 24953 TRACE glance ServerErrorException: 400 Bad Request
2014-09-24 17:32:09.082 24953 TRACE glance
2014-09-24 17:32:09.082 24953 TRACE glance The server could not comply with the
request since it is either malformed or otherwise incorrect.
2014-09-24 17:32:09.082 24953 TRACE glance
2014-09-24 17:32:09.082 24953 TRACE glance Bad header:
x-image-meta-virtual-size
2014-09-24 17:32:09.082 24953 TRACE glance
** Affects: glance
Importance: Undecided
Status: New
** Tags: glance-replicator
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/137
Title:
glance-replicator livecopy cannot work due to Bad header: x-image-
meta-virtual-size
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
I would like to use "glance-replicator livecopy" command to replicate
the images from one openstack instance to anthor, it goes to error
while running the livecopy command:
2014-09-24 17:32:09.082 24953 CRITICAL glance [-]
ServerErrorException: 400 Bad Request
The server could not comply with the request since it is either
malformed or otherwise incorrect.
Bad header: x-image-meta-virtual-size
2014-09-24 17:32:09.082 24953 TRACE glance Traceback (most recent call last):
2014-09-24 17:32:09.082 24953 TRACE glance File
"/usr/bin/glance-replicator", line 10, in
2014-09-24 17:32:09.082 24953 TRACE glance sys.exit(main())
2014-09-24 17:32:09.082 24953 TRACE glance File
"/usr/lib/python2.6/site-packages/glance/cmd/replicator.py", line 739, in main
2014-09-24 17:32:09.082 24953 TRACE glance command(options, args)
2014-09-24 17:32:09.082 24953 TRACE glance File
"/usr/lib/python2.6/site-packages/glance/cmd/replicator.py", line 516, in
replication_livecopy
2014-09-24 17:32:09.082 24953 TRACE glance image_response)
2014-09-24 17:32:09.082 24953 TRACE glance File
"/usr/lib/python2.6/site-packages/glance/cmd/replicator.py", line 238, in
add_image
2014-09-24 17:32:09.082 24953 TRACE glance response =
self._http_request('POST', url, headers, image_data)
2014-09-24 17:32:09.082 24953 TRACE glance File
"/usr/lib/python2.6/site-packages/glance/cmd/replicator.py", line 125, in
_http_request
2014-09-24 17:32:09.082 24953 TRACE glance raise
ServerErrorException(response.read())
2014-09-24 17:32:09.082 24953 TRACE glance ServerErrorException: 400 Bad
Request
2014-09-24 17:32:09.082 24953 TRACE glance
2014-09-24 17:32:09.082 24953 TRACE glance The server could not comply with
the request since it is either malformed or otherwise incorrect.
2014-09-24 17:32:09.082 24953 TRACE glance
2014-09-24 17:32:09.082 24953 TRACE glance Bad header:
x-image-meta-virtual-size
2014-09-24 17:32:09.082 24953 TRACE glance
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/137/+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 1367500] Re: IPv6 network doesn't create namespace, dhcp port
Fix proposed to branch: master
Review: https://review.openstack.org/123671
** Changed in: neutron
Status: Invalid => 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/1367500
Title:
IPv6 network doesn't create namespace, dhcp port
Status in OpenStack Neutron (virtual network service):
In Progress
Bug description:
IPv6 networking has been changed during last commits.
Create network and IPv6 subnet with default settings. Create port in the
network:
it doesn't create any namespace, it doesn't create DHCP port in the subnet,
although port get IP from DHCP server.
Although IPv4 networking continues to work as required.
$ neutron net-create netto
Created a new network:
+-+--+
| Field | Value|
+-+--+
| admin_state_up | True |
| id | 849b4dbf-0914-4cfb-956b-e0cc5d8054ab |
| name| netto|
| router:external | False|
| shared | False|
| status | ACTIVE |
| subnets | |
| tenant_id | 5664b23312504826818c9cb130a9a02f |
+-+--+
$ neutron subnet-create --ip-version 6 netto 2011::/64
Created a new subnet:
+---+--+
| Field | Value
|
+---+--+
| allocation_pools | {"start": "2011::2", "end":
"2011:::::fffe"} |
| cidr | 2011::/64
|
| dns_nameservers |
|
| enable_dhcp | True
|
| gateway_ip| 2011::1
|
| host_routes |
|
| id| e10300d1-194f-4712-b2fc-2107ac3fe909
|
| ip_version| 6
|
| ipv6_address_mode |
|
| ipv6_ra_mode |
|
| name |
|
| network_id| 849b4dbf-0914-4cfb-956b-e0cc5d8054ab
|
| tenant_id | 5664b23312504826818c9cb130a9a02f
|
+---+--+
$ neutron port-create netto
Created a new port:
+---++
| Field | Value
|
+---++
| admin_state_up| True
|
| allowed_address_pairs |
|
| binding:vnic_type | normal
|
| device_id |
|
| device_owner |
|
| fixed_ips | {"subnet_id":
"e10300d1-194f-4712-b2fc-2107ac3fe909", "ip_address": "2011::2"} |
| id| 175eaa91-441e-48df-9267-bc7fc808dce8
|
| mac_address | fa:16:3e:26:51:79
|
| name |
|
| network_id| 849b4dbf-0914-4cfb-956b-e0cc5d8054ab
|
| security_groups | c7756502-5eda-4f43-9977-21cfb73b4d4e
|
| status| DOWN
|
| tenant_id | 5664b23312504826818c9cb130a9a02f
|
+---++
$ neutron
[Yahoo-eng-team] [Bug 1373073] Re: Image v1 json client timeout while checking that image was deleted
Above is comment valid if we get image through nova or glance V1 API. for Glance V2 API, I think glance does not provide the deleted images in SHOW API. Images has been fetched from image repo with 'force_show_deleted' param as false (default value) - https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L111 ** Changed in: tempest Status: New => Invalid ** Also affects: glance 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/1373073 Title: Image v1 json client timeout while checking that image was deleted Status in OpenStack Image Registry and Delivery Service (Glance): New Status in Tempest: Invalid Bug description: Description: - Icehouse Openstack cloud - Tempest commit 4b1b8cfd4526203e5706ec387cf6362ecaa5ed5b I'm getting tearDown class error after executing image tests _StringException: Traceback (most recent call last): File "/home/user/WF_tempest/tempest-icehouse/tempest/api/image/base.py", line 58, in tearDownClass cls.client.wait_for_resource_deletion(image_id) File "/home/user/WF_tempest/tempest-icehouse/tempest/common/rest_client.py", line 551, in wait_for_resource_deletion raise exceptions.TimeoutException TimeoutException: Request timed out After some investiogation, i've found that client tried to check deleted VM by def is_resource_deleted(self, id): try: self.get_image_meta(id) except exceptions.NotFound: return True return False But get_image_meta able to get metadata of deleted image, it just has status = deleted. My quick fix was: def is_resource_deleted(self, id): try: _, meta = self.get_image_meta(id) if meta['status'] == 'deleted': return True except exceptions.NotFound: return True return False To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1373073/+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 1373310] [NEW] Angular JS integeration in Openstack horizon dashboard should be documentation
Public bug reported: Angular JS integeration in Openstack horizon dashboard should be documentation. As of now most of the UI developers not able to find appropriate documentation or approach on Horizon and Angular JS framework. ** 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/1373310 Title: Angular JS integeration in Openstack horizon dashboard should be documentation Status in OpenStack Dashboard (Horizon): New Bug description: Angular JS integeration in Openstack horizon dashboard should be documentation. As of now most of the UI developers not able to find appropriate documentation or approach on Horizon and Angular JS framework. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1373310/+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 1371559] Re: v2 image-update does not handle some schema properties properly
** Also affects: glance
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/1371559
Title:
v2 image-update does not handle some schema properties properly
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Status in Python client library for Glance:
New
Bug description:
Step1: Create an empty image using api v1 or v2.
Step2: Use glanceclient with v2 API to update image property called
"architecture":
glance --os-image-version 2 image-update --property architecture='x86'
This will show following error message:
409 Conflict
409 Conflict
There was a conflict when trying to complete your request.
Property architecture does not exist.
(HTTP 409)
The error shows up, because the client sends to glance API following
data:
[{"patch: "/architecture", "value": "x86", "op": "replace"}]
instead of
[{"patch: "/architecture", "value": "x86", "op": "add"}]
The issue is somehow related to overridden patch method in
SchemaBasedModel class, which propagates non existing properties from
schema properties.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1371559/+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 1373287] [NEW] Security group doesn't work when L2 agent enable ipset
Public bug reported: In bellow case, if L2 agent enable ipset, security group does not work: 1. create new security group with IPv6 ingress rule (and no IPv4) 2. launch an instance in this security group ** 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/1373287 Title: Security group doesn't work when L2 agent enable ipset Status in OpenStack Neutron (virtual network service): New Bug description: In bellow case, if L2 agent enable ipset, security group does not work: 1. create new security group with IPv6 ingress rule (and no IPv4) 2. launch an instance in this security group To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1373287/+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 1373268] [NEW] Fix space issue in help message for user_storage_quota config parameter
Public bug reported: """.Optional unit can be specified for the value. Accepted units are B, KB, MB, GB and TB representing Bytes, KiloBytes, MegaBytes, GigaBytes and TeraBytesrespectively.." To """.Optional unit can be specified for the value. Accepted units are B, KB, MB, GB and TB representing Bytes, KiloBytes, MegaBytes, GigaBytes and TeraBytes respectively.." ** Affects: glance Importance: Undecided Assignee: Pranali Deore (pranali-deore) Status: New ** Tags: ntt ** Changed in: glance Assignee: (unassigned) => Pranali Deore (pranali-deore) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1373268 Title: Fix space issue in help message for user_storage_quota config parameter Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: """.Optional unit can be specified for the value. Accepted units are B, KB, MB, GB and TB representing Bytes, KiloBytes, MegaBytes, GigaBytes and TeraBytesrespectively.." To """.Optional unit can be specified for the value. Accepted units are B, KB, MB, GB and TB representing Bytes, KiloBytes, MegaBytes, GigaBytes and TeraBytes respectively.." To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1373268/+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 1373266] [NEW] Fix space and spelling issues in log/exception messages
Public bug reported: 1) neutron/common/exceptions.py class PortInUse message = "Unable to complete operation on port %(port_id)s for network %(net_id)s. Port already has an attacheddevice %(device_id)s." should be message = "Unable to complete operation on port %(port_id)s for network %(net_id)s. Port already has an attached device %(device_id)s." 2) neutron/db/l3_db.py 'Cannot add floating IP to port %s that hasno fixed IP addresses' should be 'Cannot add floating IP to port %s that has no fixed IP addresses' 3) neutron/plugins/bigswitch/config.py config parameter 'servers' help message = "A comma separated list of Big Switch or Floodlight servers and port numbers. The plugin proxies the requests to the Big Switch/Floodlight server, which performs the networking configuration. Only oneserver is needed per deployment, but you may wish todeploy multiple servers to support failover." should be help message = "A comma separated list of Big Switch or Floodlight servers and port numbers. The plugin proxies the requests to the Big Switch/Floodlight server, which performs the networking configuration. Only one server is needed per deployment, but you may wish to deploy multiple servers to support failover." 4) #: neutron/plugins/bigswitch/plugin.py:399 #: neutron/plugins/ml2/drivers/mech_bigswitch/driver.py:106 msgid "Iconsistency with backend controller triggering full synchronization." should be msgid "Inconsistency with backend controller triggering full synchronization." 5) #: neutron/plugins/cisco/common/cisco_faults.py:120 msgid "Unable to find a Novatenant with the specified identifier." should be msgid "Unable to find a Nova tenant with the specified identifier." 6) #: neutron/plugins/cisco/l3/hosting_device_drivers/csr1kv_hd_driver.py:68 #, python-format msgid "Failed to create config file: %s. Trying toclean up." should be msgid "Failed to create config file: %s. Trying to clean up." 7) #: neutron/plugins/hyperv/agent/hyperv_neutron_agent.py:69 msgid "" "Specifies the maximum number of retries to enable Hyper-V's port metrics " "collection. The agent will try to enable the feature once every " "polling_interval period for at most metrics_max_retries or until it " "succeedes." should be msgid "" "Specifies the maximum number of retries to enable Hyper-V's port metrics " "collection. The agent will try to enable the feature once every " "polling_interval period for at most metrics_max_retries or until it " "succeeds." 8) #: neutron/plugins/hyperv/agent/hyperv_neutron_agent.py:311 #, python-format msgid "Network %s is not avalailable on this agent" should be msgid "Network %s is not available on this agent" 9) #: neutron/plugins/hyperv/agent/security_groups_driver.py:92 msgid "Aplying port filter." should be msgid "Applying port filter." 10) #: neutron/plugins/ibm/agent/sdnve_neutron_agent.py:143 #, python-format msgid "info_update received. New controlleris to be set to: %s" should be msgid "info_update received. New controller is to be set to: %s" 11) #: neutron/plugins/ibm/common/exceptions.py:28 #, python-format msgid "The input does not contain nececessary info: %(msg)s" should be msgid "The input does not contain necessary info: %(msg)s" 12) #: neutron/plugins/midonet/midonet_lib.py:159 msgid "Tried to add tonon-existent DHCP" should be msgid "Tried to add to non-existent DHCP" 13) #: neutron/plugins/midonet/common/config.py:31 msgid "ID of the project that MidoNet admin userbelongs to." should be msgid "ID of the project that MidoNet admin user belongs to." 14) #: neutron/plugins/ml2/drivers/arista/arista_l3_driver.py:336 #, python-format msgid "Error occured while trying to execute commands %(cmd)s on EOS %(host)s" should be msgid "Error occurred while trying to execute commands %(cmd)s on EOS %(host)s" 15) #: neutron/plugins/ml2/drivers/arista/config.py:60 msgid "" "Defines Region Name that is assigned to this OpenStack Controller. This " "is useful when multiple OpenStack/Neutron controllers are managing the " "same Arista HW clusters. Note that this name must match with the region " "name registered (or known) to keystone service. Authentication with " "Keysotne is performed by EOS. This is optional. If not set, a value of " "\"RegionOne\" is assumed." s/Keysotne/Keystone 16) #: neutron/plugins/ml2/drivers/arista/mechanism_arista.py:739 #, python-format msgid "Network %s is not created as it is not found inArista DB" should be msgid "Network %s is not created as it is not found in Arista DB" 17) #: neutron/plugins/ml2/drivers/arista/mechanism_arista.py:781 #, python-format msgid "Network %s is not updated as it is not found inArista DB" msgstr "" should be msgid "Network %s is not updated as it is not found in Arista DB" 18) #: neutron/plugins/ml2/drivers/l2pop/config.py:25 msgid "" "Delay within which agent is expected to update existing ports whent it " "restarts" should be msgid "" "Delay within which agent is expected to update existing port
