[Yahoo-eng-team] [Bug 1495519] Re: import flow doesn't raise error on forbidden location
** Changed in: glance
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1495519
Title:
import flow doesn't raise error on forbidden location
Status in Glance:
Fix Released
Status in Glance liberty series:
New
Bug description:
The following command correctly raises an exception server side but it
doesn't report the error back to the user. This ends up in the user
"thinking" the task was created correctly:
$ glance --os-image-api-version 2 --os-image-url
http://localhost:9292/v2 --os-tenant-id
a1875f8a27f74708b6fb9281e7430a98 task-create --type import --input
'{"import_from_format": "qcow2", "import_from":
"swift://127.0.0.1:8000/test.qcow2", "image_properties":
{"disk_format": "qcow2", "container_format": "bare"}}'
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1495519/+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 1512369] Re: glance should declare a test-requirements.txt on swiftclient
** No longer affects: glance ** Changed in: glance/liberty Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1512369 Title: glance should declare a test-requirements.txt on swiftclient Status in Glance liberty series: Fix Released Bug description: As glance is building its config, it needs swiftclient. And it isn't defined in test-requirements.txt, meaning that some options may be missing for swift. I've added python-swiftclient in the Build-Depends- Indep: of the Debian package, though it should IMO also go into the test-requirements.txt of the upstream project. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/liberty/+bug/1512369/+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 1672215] Re: device_id/device_owner field in Admin Edit Port form are not filled with the current values
Reviewed: https://review.openstack.org/444669 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=61fece80e1c153dd7569011cb247b066095753ee Submitter: Jenkins Branch:master commit 61fece80e1c153dd7569011cb247b066095753ee Author: Akihiro Motoki Date: Sun Mar 12 21:03:07 2017 + Populate device_id/owner fields in Admin Edit Port form The initial values are not filled with the current value. As a result, when submitting a form, these fields will be cleared. Change-Id: Ie7eb288c381681a422aa5ae4edfb8acf645f701a Closes-Bug: #1672215 ** Changed in: horizon Status: In Progress => 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/1672215 Title: device_id/device_owner field in Admin Edit Port form are not filled with the current values Status in OpenStack Dashboard (Horizon): Fix Released Bug description: device_id/device_owner field in Admin Edit Port form are not filled with the current values. They should be filled with the current values. Otherwise, these fields will cleared when submitting the form without filling appropriate values. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1672215/+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 1671595] Re: shared field in network-edit from should be controlled by 'update_network:shared' policy
Reviewed: https://review.openstack.org/443927 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=13a4cef86924c51e98afd1c460aef163c429bfa5 Submitter: Jenkins Branch:master commit 13a4cef86924c51e98afd1c460aef163c429bfa5 Author: Akihiro Motoki Date: Thu Mar 9 18:17:03 2017 + Use correct policy name for "Edit Network" form setup UpdateNetwork form should use 'update_network:shared' instead of 'create_update:shared' to check 'shared' field can be edited. Change-Id: I482e98a36a7fb5abc7131d413d2ebde36503d8ab Closes-Bug: #1671595 ** Changed in: horizon Status: In Progress => 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/1671595 Title: shared field in network-edit from should be controlled by 'update_network:shared' policy Status in OpenStack Dashboard (Horizon): Fix Released Bug description: 'shared' field in the network edit form refers to the policy 'create_network:shared'. It should be 'update_network:shared'. https://github.com/openstack/horizon/blob/3e195b61e0aa3ea979ff63758dd0da5834e30218/openstack_dashboard/dashboards/project/networks/forms.py#L52 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1671595/+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 1667154] Re: User id on action log shouldn't be a link
Reviewed: https://review.openstack.org/437191 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=804db52d7dd6ff5f0d6c6ed9a5196f0d399357e6 Submitter: Jenkins Branch:master commit 804db52d7dd6ff5f0d6c6ed9a5196f0d399357e6 Author: Ying Zuo Date: Wed Feb 22 15:34:01 2017 -0800 Remove link for user id field on project action log The action log under project dashboard should not link to the user details panel which requires admin permission. Change-Id: I802188db6f1f8fc7e854980eca85d3b1a75aec1e Closes-bug: #1667154 ** Changed in: horizon Status: In Progress => 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/1667154 Title: User id on action log shouldn't be a link Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The user id field in the action log table on project/instance details panel is currently a link to the user details panel. If a non-admin user clicks on it, he will be logged out since he doesn't have the permission to access the panel. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1667154/+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 1672215] [NEW] device_id/device_owner field in Admin Edit Port form are not filled with the current values
Public bug reported: device_id/device_owner field in Admin Edit Port form are not filled with the current values. They should be filled with the current values. Otherwise, these fields will cleared when submitting the form without filling appropriate values. ** Affects: horizon Importance: Low Assignee: Akihiro Motoki (amotoki) Status: In Progress ** Tags: neutron -- 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/1672215 Title: device_id/device_owner field in Admin Edit Port form are not filled with the current values Status in OpenStack Dashboard (Horizon): In Progress Bug description: device_id/device_owner field in Admin Edit Port form are not filled with the current values. They should be filled with the current values. Otherwise, these fields will cleared when submitting the form without filling appropriate values. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1672215/+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 1672213] [NEW] 'True' is displayed in "Admin State" choice field when editing a port
Public bug reported: The choice of Admin State field for a port is UP or DOWN, but "True" is displayed when the Edit Port form is displayed. ** Affects: horizon Importance: Low Assignee: Akihiro Motoki (amotoki) Status: New ** Tags: neutron -- 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/1672213 Title: 'True' is displayed in "Admin State" choice field when editing a port Status in OpenStack Dashboard (Horizon): New Bug description: The choice of Admin State field for a port is UP or DOWN, but "True" is displayed when the Edit Port form is displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1672213/+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 1672211] [NEW] Lbaasv2 - Could not load neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPlugin
Public bug reported:
Hi,
i'm trying to install lbaas for my openstack. Im on ubuntu16.04 Openstack
Newton with 3 node OVS deploy.
Following this guide for lbaas
https://docs.openstack.org/ocata/networking-guide/config-lbaas.html
controller node
aptitude search neutron-lbaas
p neutron-lbaas-agent
- Neutron is a virtual network service for
Openstack - LBaaS agent
i A neutron-lbaas-common
- Neutron is a virtual network service for
Openstack - common
i neutron-lbaasv2-agent
- Neutron is a virtual network service for
Openstack - LBaaSv2 agent
i A python-neutron-lbaas
- Loadbalancer-as-a-Service driver for
OpenStack Neutron
so neutron-lbaas-common neutron-lbaasv2-agent python-neutron-lbaas are
installed.
/etc/neutron/neutron.conf
[DEFAULT]
debug= true
core_plugin = ml2
service_plugins =
router,neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPluginv2
allow_overlapping_ips = True
dhcp_agents_per_network = 1
transport_url = rabbit://openstack:mjvnzq8@controller
auth_strategy = keystone
notify_nova_on_port_status_changes = True
notify_nova_on_port_data_changes = True
core_plugin = ml2
[agent]
root_helper = sudo /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf
[cors]
[cors.subdomain]
[database]
connection = mysql+pymysql://neutron:mjvnzq8@controller/neutron
[keystone_authtoken]
auth_uri = http://controller:5000
auth_url = http://controller:35357
memcached_servers = controller:11211
auth_type = password
project_domain_name = default
user_domain_name = default
project_name = service
username = neutron
password = *
[matchmaker_redis]
[nova]
auth_url = http://controller:35357
auth_type = password
project_domain_name = default
user_domain_name = default
region_name = RegionOne
project_name = service
username = nova
password = *
[oslo_concurrency]
[oslo_messaging_amqp]
[oslo_messaging_notifications]
[oslo_messaging_rabbit]
[oslo_messaging_zmq]
[oslo_policy]
[qos]
[quotas]
[ssl]
[service_providers]
service_provider =
LOADBALANCERV2:Haproxy:neutron_lbaas.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default
/etc/neutron/neutron_lbaas.conf
[service_providers]
service_provider =
LOADBALANCERV2:Haproxy:neutron_lbaas.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default
So that is the server side, after i restart it wont work anymore because it
cant load the lbaas driver
/var/log/neutron/neutron-server.log
2017-03-12 20:55:16.464 769 INFO neutron.common.config [-] Logging enabled!
2017-03-12 20:55:16.464 769 INFO neutron.common.config [-]
/usr/bin/neutron-server version 9.0.0
2017-03-12 20:55:16.464 769 INFO neutron.common.config [-] Logging enabled!
2017-03-12 20:55:16.465 769 INFO neutron.common.config [-]
/usr/bin/neutron-server version 9.0.0
2017-03-12 20:55:16.473 769 INFO neutron.manager [-] Loading core plugin: ml2
2017-03-12 20:55:16.669 769 INFO neutron.plugins.ml2.managers [-] Configured
type driver names: ['flat', 'vlan', 'vxlan']
2017-03-12 20:55:16.678 769 INFO neutron.plugins.ml2.drivers.type_flat [-]
Allowable flat physical_network names: ['provider']
2017-03-12 20:55:16.681 769 INFO neutron.plugins.ml2.drivers.type_vlan [-]
Network VLAN ranges: {'provider': []}
2017-03-12 20:55:16.684 769 INFO neutron.plugins.ml2.managers [-] Loaded type
driver names: ['flat', 'vlan', 'vxlan']
2017-03-12 20:55:16.684 769 INFO neutron.plugins.ml2.managers [-] Registered
types: ['flat', 'vlan', 'vxlan']
2017-03-12 20:55:16.685 769 INFO neutron.plugins.ml2.managers [-] Tenant
network_types: ['vxlan']
2017-03-12 20:55:16.685 769 INFO neutron.plugins.ml2.managers [-] Configured
extension driver names: ['port_security']
2017-03-12 20:55:16.689 769 INFO neutron.plugins.ml2.managers [-] Loaded
extension driver names: ['port_security']
2017-03-12 20:55:16.690 769 INFO neutron.plugins.ml2.managers [-] Registered
extension drivers: ['port_security']
2017-03-12 20:55:16.690 769 INFO neutron.plugins.ml2.managers [-] Configured
mechanism driver names: ['openvswitch', 'l2population']
2017-03-12 20:55:16.692 769 WARNING neutron.agent.securitygroups_rpc [-] Driver
configuration doesn't match with enable_security_group
2017-03-12 20:55:16.693 769 INFO neutron.plugins.ml2.managers [-] Loaded
mechanism driver names: ['openvswitch', 'l2population']
2017-03-12 20:55:16.693 769 INFO neutron.plugins.ml2.managers [-] Registered
mechanism drivers: ['openvswitch', 'l2population']
2017-03-12 20:55:16.771 769 INFO neutron.plugins.ml2.managers [-]
[Yahoo-eng-team] [Bug 1485144] Re: User cannot create an admin network without knowing the physical network name
Reviewed: https://review.openstack.org/383977 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=31f4aa97671dba21792d5e6695c7321dc60c890f Submitter: Jenkins Branch:master commit 31f4aa97671dba21792d5e6695c7321dc60c890f Author: Ying Zuo Date: Fri Oct 7 17:09:31 2016 -0700 Provide available physical networks on create network modal Added setting physical_networks to provide users list of available physical networks to choose from on the admin create network modal. Default to an empty list and the physical network field is a regular input field where users can type in the name of the physical network to be used. If it's set to a list of physical network names, the physical network field is a dropdown menu where users can choose a physical network to use. Closes-bug: #1485144 Change-Id: I342b3776a52179d5b4a704fb984912878ff3dc81 ** Changed in: horizon Status: In Progress => 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/1485144 Title: User cannot create an admin network without knowing the physical network name Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Currently user cannot create an admin network without knowing the physical network name. It will be more convenient if the physical network field is a choice field such that user can choose the name from the list. Steps to reproduce: 1. Go to Admin -> Network 2. Click create network 3. You will notice that the physical network field is a text field To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1485144/+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 1672133] [NEW] local-memory cache backend of Django session backend can't pass session data after logining
Public bug reported:
the browser remained in the login page after login with right user and
password, when I change backend session engine from mysql to local-memory
cache. I inspect the code, and found this code:
in .../django/core/cache/__init__.py
class CacheHandler(object):
def __init__(self):
self._caches = local()
def __getitem__(self, alias):
try:
return self._caches.caches[alias]
except AttributeError:
self._caches.caches = {}
except KeyError:
getitemp("no caches.caches.caches key in cache handler getitem, ")
pass
if alias not in settings.CACHES:
raise InvalidCacheBackendError(
"Could not find config for '%s' in settings.CACHES" % alias
)
cache = _create_cache(alias)
self._caches.caches[alias] = cache
return cache
def all(self):
return getattr(self._caches, 'caches', {}).values()
caches = CacheHandler()
in Login view, the user has autenticated, and the session info has been
recorded in caches._caches.caches[alias],
but when browser re-targets to project view, the backend is a new process with
new caches(),so
except AttributeError:
self._caches.caches = {}
no old session data in it, the view return to login page again.
Is this a bug? or a Django bug?
thanks.
** 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/1672133
Title:
local-memory cache backend of Django session backend can't pass
session data after logining
Status in OpenStack Dashboard (Horizon):
New
Bug description:
the browser remained in the login page after login with right user and
password, when I change backend session engine from mysql to local-memory
cache. I inspect the code, and found this code:
in .../django/core/cache/__init__.py
class CacheHandler(object):
def __init__(self):
self._caches = local()
def __getitem__(self, alias):
try:
return self._caches.caches[alias]
except AttributeError:
self._caches.caches = {}
except KeyError:
getitemp("no caches.caches.caches key in cache handler getitem, ")
pass
if alias not in settings.CACHES:
raise InvalidCacheBackendError(
"Could not find config for '%s' in settings.CACHES" % alias
)
cache = _create_cache(alias)
self._caches.caches[alias] = cache
return cache
def all(self):
return getattr(self._caches, 'caches', {}).values()
caches = CacheHandler()
in Login view, the user has autenticated, and the session info has been
recorded in caches._caches.caches[alias],
but when browser re-targets to project view, the backend is a new process
with new caches(),so
except AttributeError:
self._caches.caches = {}
no old session data in it, the view return to login page again.
Is this a bug? or a Django bug?
thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1672133/+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
