[Yahoo-eng-team] [Bug 1253497] Re: Replace uuidutils.generate_uuid() with str(uuid.uuid4())
** No longer affects: murano -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1253497 Title: Replace uuidutils.generate_uuid() with str(uuid.uuid4()) Status in Barbican: Fix Released Status in BillingStack: Invalid Status in Blazar: Fix Committed Status in Cinder: Invalid Status in Designate: Fix Released Status in Glance: Fix Released Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): Invalid Status in Ironic: Fix Released Status in Karbor: New Status in Manila: Fix Released Status in neutron: Invalid Status in OpenStack Compute (nova): Invalid Status in oslo-incubator: Fix Released Status in Sahara: Fix Released Status in staccato: Invalid Status in taskflow: Invalid Status in OpenStack DBaaS (Trove): Fix Released Status in tuskar: Fix Released Bug description: http://lists.openstack.org/pipermail/openstack- dev/2013-November/018980.html > Hi all, > > We had a discussion of the modules that are incubated in Oslo. > > https://etherpad.openstack.org/p/icehouse-oslo-status > > One of the conclusions we came to was to deprecate/remove uuidutils in > this cycle. > > The first step into this change should be to remove generate_uuid() from > uuidutils. > > The reason is that 1) generating the UUID string seems trivial enough to > not need a function and 2) string representation of uuid4 is not what we > want in all projects. > > To address this, a patch is now on gerrit. > https://review.openstack.org/#/c/56152/ > > Each project should directly use the standard uuid module or implement its > own helper function to generate uuids if this patch gets in. > > Any thoughts on this change? Thanks. > Unfortunately it looks like that change went through before I caught up on email. Shouldn't we have removed its use in the downstream projects (at least integrated projects) before removing it from Oslo? Doug To manage notifications about this bug go to: https://bugs.launchpad.net/barbican/+bug/1253497/+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 1699060] Re: Impossible to define policy rule based on domain ID
Mass opening bugs definitely not going to solve this. Also it's not quite clear from the bug or mail — what the projects should/shouldn't do. Is it really an issue with oslo.policy? ** No longer affects: murano -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1699060 Title: Impossible to define policy rule based on domain ID Status in Cinder: New Status in Glance: New Status in heat: New Status in Manila: New Status in neutron: New Status in OpenStack Compute (nova): New Status in watcher: New Bug description: We have common approach to set rules for each API using policy.json file. And for the moment, it is not possible to use "domain_id" in policy rules, only "project_id" and "user_id". It becomes very important because Keystone API v3 is used more and more. The only service that supports rules with "domain_id" is Keystone itself. As a result we should be able to use following rules: "admin_or_domain_owner": "is_admin:True or domain_id:%(domain_id)s", "domain_owner": "domain_id:%(domain_id)s", like this: "volume:get": "rule:domain_owner", or "volume:get": "rule:admin_or_domain_owner", Right now, we always get 403 error having such rules. Related mail-list thread: https://openstack.nimeyo.com/115438 /openstack-dev-all-policy-rules-for-apis-based-on-domain_id To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1699060/+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 1692767] Re: Start keystone service failed with uwsgi in devstack
The correct way to do it would be to add a tmpfiles.d config file, that
would create the directory at startup. also it's not about keystone, but
about devstack
** Also affects: devstack
Importance: Undecided
Status: New
** Summary changed:
- Start keystone service failed with uwsgi in devstack
+ [devstack] keystone service fails to start after reboot
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1692767
Title:
[devstack] keystone service fails to start after reboot
Status in devstack:
New
Status in OpenStack Identity (keystone):
New
Bug description:
Enviroment
OS: CentOS7.2
I deployed the devstack environment successfully in CentOS system.
After rebooting the CentOS system， the keystone service could not be
started. The uwsgi raised exception as follows.
Apr 23 22:38:53 devstack.localdomain systemd[1]: devstack@keystone.service
failed.
Apr 23 22:42:46 devstack.localdomain systemd[1]: Starting Devstack
devstack@keystone.service...
Apr 23 22:42:46 devstack.localdomain devstack@keystone.service[7242]: [uWSGI]
getting INI configuration from /etc/keystone/keystone-uwsgi-public.ini
Apr 23 22:42:46 devstack.localdomain devstack@keystone.service[7242]:
open("./python_plugin.so"): No such file or directory [core/utils.c line 3686]
Apr 23 22:42:46 devstack.localdomain devstack@keystone.service[7242]: !!!
UNABLE to load uWSGI plugin: ./python_plugin.so: cannot open shared object
file: No such file or directory !!!
Apr 23 22:42:46 devstack.localdomain devstack@keystone.service[7242]: ***
Starting uWSGI 2.0.15 (64bit) on [Sun Apr 23 22:42:46 2017] ***
Apr 23 22:42:46 devstack.localdomain systemd[1]: devstack@keystone.service:
main process exited, code=exited, status=1/FAILURE
Apr 23 22:42:46 devstack.localdomain systemd[1]: Failed to start Devstack
devstack@keystone.service.
Apr 23 22:42:46 devstack.localdomain systemd[1]: Unit
devstack@keystone.service entered failed state.
Apr 23 22:42:46 devstack.localdomain systemd[1]: devstack@keystone.service
failed.
So i think this is a bug. I tried to create the /var/run/uwsgi directory and
chown it stack user. Then it works.
sudo mkdir -p /var/run/uwsgi
sudo chown stack:stack uwsgi
So what do you think that?
To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1692767/+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 1661453] Re: Unlocalized strings on App Catalog tab
https://github.com/openstack/murano-dashboard/blob/master/muranodashboard/dashboard.py#L24 https://github.com/openstack/murano-dashboard/blob/master/muranodashboard/catalog/panel.py#L20 both these strings are marked for translation. closing as invalid ** Changed in: murano 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/1661453 Title: Unlocalized strings on App Catalog tab Status in OpenStack Dashboard (Horizon): Invalid Status in Murano: Invalid Bug description: On App Catalog tab, the label "App Catalog" and "Browse Local" are not localized. I am not able to locate those strings in Zanata. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1661453/+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 1082248] Re: Use uuidutils instead of uuid.uuid4()
** No longer affects: python-muranoclient -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1082248 Title: Use uuidutils instead of uuid.uuid4() Status in Cinder: In Progress Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in Karbor: Fix Released Status in kolla: Fix Committed Status in kuryr: Fix Released Status in kuryr-libnetwork: Fix Released Status in Magnum: In Progress Status in Mistral: Fix Released Status in networking-calico: In Progress Status in networking-ovn: Fix Released Status in networking-sfc: In Progress Status in neutron: Fix Released Status in OpenStack Compute (nova): In Progress Status in Sahara: Fix Released Status in senlin: Fix Released Status in tacker: In Progress Status in watcher: Fix Released Bug description: Openstack common has a wrapper for generating uuids. We should only use that function when generating uuids for consistency. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1082248/+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 1082248] Re: Use uuidutils instead of uuid.uuid4()
** No longer affects: murano -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1082248 Title: Use uuidutils instead of uuid.uuid4() Status in Cinder: In Progress Status in Gnocchi: In Progress Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in Karbor: Fix Released Status in kolla: In Progress Status in kuryr: In Progress Status in kuryr-libnetwork: Fix Released Status in Magnum: In Progress Status in Mistral: Fix Released Status in networking-calico: In Progress Status in networking-ovn: Fix Released Status in networking-sfc: In Progress Status in neutron: Fix Released Status in OpenStack Compute (nova): In Progress Status in python-muranoclient: In Progress Status in Sahara: Fix Released Status in senlin: Fix Released Status in tacker: In Progress Status in watcher: Fix Released Bug description: Openstack common has a wrapper for generating uuids. We should only use that function when generating uuids for consistency. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1082248/+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 1590608] Re: Services should use http_proxy_to_wsgi middleware
** No longer affects: murano -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1590608 Title: Services should use http_proxy_to_wsgi middleware Status in Aodh: Fix Released Status in Barbican: Confirmed Status in Ceilometer: Fix Released Status in Cinder: Fix Released Status in cloudkitty: New Status in congress: New Status in Glance: Fix Released Status in Gnocchi: Fix Committed Status in heat: In Progress Status in OpenStack Identity (keystone): Fix Released Status in Magnum: New Status in neutron: In Progress Status in Panko: Fix Released Status in OpenStack Search (Searchlight): In Progress Status in senlin: New Status in OpenStack DBaaS (Trove): In Progress Bug description: It's a common problem when putting a service behind a load balancer to need to forward the Protocol and hosts of the original request so that the receiving service can construct URLs to the loadbalancer and not the private worker node. Most services have implemented some form of secure_proxy_ssl_header = HTTP_X_FORWARDED_PROTO handling however exactly how this is done is dependent on the service. oslo.middleware provides the http_proxy_to_wsgi middleware that handles these headers and the newer RFC7239 forwarding header and completely hides the problem from the service. This middleware should be adopted by all services in preference to their own HTTP_X_FORWARDED_PROTO handling. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1590608/+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 1614361] Re: tox.ini needs to be updated as openstack infra now supports upper constraints
** No longer affects: murano -- 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/1614361 Title: tox.ini needs to be updated as openstack infra now supports upper constraints Status in Cinder: In Progress Status in Designate: Fix Released Status in Glance: In Progress Status in heat: In Progress Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic Inspector: Fix Released Status in Mistral: Fix Released Status in networking-ovn: Invalid Status in octavia: Fix Released Status in python-mistralclient: New Status in python-muranoclient: Fix Released Status in tacker: In Progress Status in OpenStack DBaaS (Trove): Invalid Status in vmware-nsx: Fix Released Status in zaqar: Fix Released Status in Zaqar-ui: Fix Released Bug description: Openstack infra now supports upper constraints for releasenotes, cover, venv targets. tox.ini uses install_command for these targets, which can now be safely removed. Reference for mail that details this support: http://lists.openstack.org/pipermail/openstack-dev/2016-August/101474.html To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1614361/+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 1603307] Re: horizon plugin gives the KeyError
** Changed in: murano Status: In Progress => 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/1603307 Title: horizon plugin gives the KeyError Status in OpenStack Dashboard (Horizon): In Progress Status in Murano: Invalid Bug description: horizon master with murano-dashboard, open the murano-dashboard, give the error: File "/opt/openstack/horizon/.tox/venv/lib/python2.7/site-packages/django/dispatch/dispatcher.py", line 189, in send response = receiver(signal=self, sender=sender, **named) File "/opt/openstack/horizon/horizon/templatetags/angular.py", line 36, in update_angular_template_hash theme = context['THEME'] # current theme being compressed KeyError: 'THEME' To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1603307/+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 1596829] Re: String interpolation should be delayed at logging calls
** No longer affects: murano
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1596829
Title:
String interpolation should be delayed at logging calls
Status in Ceilometer:
New
Status in congress:
In Progress
Status in Glance:
In Progress
Status in glance_store:
New
Status in heat:
New
Status in Ironic:
Fix Released
Status in masakari:
In Progress
Status in networking-vsphere:
Fix Released
Status in neutron:
Fix Released
Status in OpenStack Compute (nova):
In Progress
Status in os-brick:
Fix Released
Status in os-vif:
Fix Released
Status in python-cinderclient:
Fix Released
Status in python-glanceclient:
Fix Released
Status in python-neutronclient:
Fix Released
Status in OpenStack Object Storage (swift):
New
Status in taskflow:
New
Bug description:
String interpolation should be delayed to be handled by the logging
code, rather than being done at the point of the logging call.
Wrong: LOG.debug('Example: %s' % 'bad')
Right: LOG.debug('Example: %s', 'good')
See the following guideline.
* http://docs.openstack.org/developer/oslo.i18n/guidelines.html
#adding-variables-to-log-messages
The rule for it should be added to hacking checks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1596829/+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 1465315] Re: [dashboard] descriptions of fields (for example license/requirements) should be limited in UI.
** Also affects: murano/mitaka Importance: Undecided Status: New ** Also affects: murano/newton Importance: Low Assignee: omar (oshykhkerimov) Status: Fix Released ** Changed in: murano/mitaka Status: New => Confirmed ** Changed in: murano/mitaka Importance: Undecided => Low ** Tags added: mitaka-backport-potential -- 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/1465315 Title: [dashboard] descriptions of fields (for example license/requirements) should be limited in UI. Status in OpenStack Dashboard (Horizon): Invalid Status in Murano: Fix Released Status in Murano mitaka series: Confirmed Status in Murano newton series: Fix Released Bug description: To reproduce: add a long license description. https://www.dropbox.com/s/40d86ct7ww18w5z/Screenshot%202015-06-15%2017.37.08.png?dl=0 This looks cluttered and makes little sense. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1465315/+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 1582816] [NEW] ModalBackdropMixin imposes empty init method
Public bug reported: Recently a commit landed in horizon, that changed inheritance order of Mixins. https://github.com/openstack/horizon/commit/4c33d2d40cac592385f7bcfbc106c379d7b70020 The change itself is ok, however this now means, that any class inherited from ModalFormMixin should have an init without parameters. This change broke murano-dashboard since we inherit from both formtools wizard and ModalFormMixin. here is an example of the errors we get http://paste.openstack.org/show/497387/ It might be a good idea to allow *args, **kwargs in ModalBackdropMixin's init method ** Affects: horizon Importance: Undecided Assignee: Kirill Zaitsev (kzaitsev) Status: In Progress -- 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/1582816 Title: ModalBackdropMixin imposes empty init method Status in OpenStack Dashboard (Horizon): In Progress Bug description: Recently a commit landed in horizon, that changed inheritance order of Mixins. https://github.com/openstack/horizon/commit/4c33d2d40cac592385f7bcfbc106c379d7b70020 The change itself is ok, however this now means, that any class inherited from ModalFormMixin should have an init without parameters. This change broke murano-dashboard since we inherit from both formtools wizard and ModalFormMixin. here is an example of the errors we get http://paste.openstack.org/show/497387/ It might be a good idea to allow *args, **kwargs in ModalBackdropMixin's init method To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1582816/+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 1489059] Re: "db type could not be determined" running py34
** No longer affects: murano -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1489059 Title: "db type could not be determined" running py34 Status in Aodh: Fix Released Status in Barbican: Fix Released Status in Bareon: Fix Released Status in Cinder: In Progress Status in cloudkitty: Fix Committed Status in Fuel for OpenStack: In Progress Status in Glance: Fix Committed Status in glance_store: Fix Committed Status in hacking: Fix Released Status in heat: Fix Released Status in Ironic: Fix Released Status in ironic-lib: Fix Committed Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in keystonemiddleware: Fix Released Status in kolla: Fix Released Status in Manila: Fix Released Status in networking-midonet: Fix Released Status in networking-ofagent: Fix Released Status in neutron: Fix Released Status in python-glanceclient: Fix Released Status in python-keystoneclient: Fix Released Status in python-muranoclient: Fix Released Status in python-solumclient: Fix Released Status in python-swiftclient: In Progress Status in Rally: Fix Released Status in Sahara: Fix Released Status in OpenStack Search (Searchlight): Fix Released Status in senlin: Fix Released Status in tap-as-a-service: Fix Released Status in tempest: Fix Released Status in zaqar: Fix Released Status in python-ironicclient package in Ubuntu: Fix Committed Bug description: When running tox for the first time, the py34 execution fails with an error saying "db type could not be determined". This issue is know to be caused when the run of py27 preceeds py34 and can be solved erasing the .testrepository and running "tox -e py34" first of all. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1489059/+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 1555752] [NEW] AJAX Row updates are borken for non-multi-select tables
Public bug reported:
The offending code is found in horizon/static/horizon/js/horizon.tables.js
if($row.find('.table-row-multi-select')[0].checked)
In case the table is multi_valued=False there would be no '.table-row-
multi-select' element. [0] would return undefined and accessing .checked
would raise an error.
This was introduced by https://review.openstack.org/#/c/252161/ Before
this commit this access was guarded by jquery helper method.
** Affects: horizon
Importance: Undecided
Status: New
** Tags: js
--
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/1555752
Title:
AJAX Row updates are borken for non-multi-select tables
Status in OpenStack Dashboard (Horizon):
New
Bug description:
The offending code is found in horizon/static/horizon/js/horizon.tables.js
if($row.find('.table-row-multi-select')[0].checked)
In case the table is multi_valued=False there would be no '.table-row-
multi-select' element. [0] would return undefined and accessing
.checked would raise an error.
This was introduced by https://review.openstack.org/#/c/252161/ Before
this commit this access was guarded by jquery helper method.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1555752/+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 1280105] Re: urllib/urllib2 is incompatible for python 3
** No longer affects: murano -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1280105 Title: urllib/urllib2 is incompatible for python 3 Status in Ceilometer: Fix Released Status in Cinder: In Progress Status in Fuel for OpenStack: Fix Committed Status in Glance: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Magnum: In Progress Status in Manila: In Progress Status in neutron: Fix Released Status in python-troveclient: In Progress Status in refstack: Fix Released Status in Sahara: Fix Released Status in tacker: In Progress Status in tempest: In Progress Status in Trove: In Progress Status in Zuul: In Progress Bug description: urllib/urllib2 is incompatible for python 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1280105/+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 1548545] [NEW] Terminating process, that starts API workers does not terminate the workers
Public bug reported:
Experiencing an issue with master, my HEAD points to
7e27d6ef05ec856e7b62f65218bdef3896ac55a2
Here is full log of glance-api
$ tox -e venv -- glance-api
--config-file=/home/teferi/glance/etc/glance-api.conf
venv develop-inst-noop: /home/teferi/glance
venv installed: aioeventlet==0.4,alembic==0.8.4,amqp==1.4.9,anyjson==0.3.3,-e
git+https://git.openstack.org/openstack/app-catalog@2ea8f13555a07ac3b32abcf6b5ef40c4012bb5f2#egg=app_catalog_artifact_plugin=contrib/glare,appdirs==1.4.0,automaton==1.2.0,Babel==2.2.0,cachetools==1.1.5,castellan==0.3.1,cffi==1.5.2,contextlib2==0.5.1,coverage==4.0.3,cryptography==1.2.2,debtcollector==1.3.0,decorator==4.0.9,docutils==0.12,enum34==1.1.2,eventlet==0.18.4,extras==0.0.3,fasteners==0.14.1,fixtures==1.4.0,flake8==2.2.4,funcsigs==0.4,functools32==3.2.3.post2,futures==3.0.5,futurist==0.12.0,-e
git+https://git.openstack.org/openstack/glance@7e27d6ef05ec856e7b62f65218bdef3896ac55a2#egg=glance,glance-store==0.11.0,greenlet==0.4.9,hacking==0.10.2,httplib2==0.9.2,idna==2.0,ipaddress==1.0.16,iso8601==0.1.11,Jinja2==2.8,jsonschema==2.5.1,keystoneauth1==2.3.0,keystonemiddleware==4.3.0,kombu==3.0.33,linecache2==1.0.0,Mako==1.0.3,MarkupSafe==0.23,mccabe==0.2.1,mock==1.3.0,monotonic==0.6,mox3==0.14
.0,msgpack-python==0.4.7,netaddr==0.7.18,netifaces==0.10.4,networkx==1.11,os-client-config==1.15.0,oslo.concurrency==3.4.0,oslo.config==3.7.0,oslo.context==2.0.0,oslo.db==4.5.0,oslo.i18n==3.3.0,oslo.log==3.0.0,oslo.messaging==4.3.0,oslo.middleware==3.6.0,oslo.policy==1.4.0,oslo.serialization==2.3.0,oslo.service==1.5.0,oslo.utils==3.6.0,oslosphinx==4.3.0,oslotest==2.1.0,osprofiler==1.1.0,Paste==2.0.2,PasteDeploy==1.5.2,pbr==1.8.1,pep8==1.5.7,pika==0.10.0,pika-pool==0.1.3,positional==1.0.1,prettytable==0.7.2,psutil==1.2.1,psycopg2==2.6.1,pyasn1==0.1.9,pycadf==2.1.0,pycparser==2.14,pycrypto==2.6.1,pyflakes==0.8.1,Pygments==2.1.1,pyinotify==0.9.6,PyMySQL==0.7.1,pyOpenSSL==0.15.1,pyrsistent==0.11.12,pysendfile==2.0.1,python-dateutil==2.4.2,python-editor==0.5,python-keystoneclient==2.2.0,python-mimeparse==1.5.1,python-subunit==1.2.0,python-swiftclient==2.7.0,pytz==2015.7,PyYAML==3.11,qpid-python==0.32,reno==1.5.0,repoze.lru==0.6,requests==2.9.1,requestsexceptions==1.1.3,retrying==1.3.3,Ro
utes==2.2,semantic-version==2.5.0,simplegeneric==0.8.1,six==1.10.0,Sphinx==1.2.3,SQLAlchemy==1.0.12,sqlalchemy-migrate==0.10.0,sqlparse==0.1.18,stevedore==1.11.0,taskflow==1.28.0,Tempita==0.5.2,testrepository==0.0.20,testresources==1.0.0,testscenarios==0.5.0,testtools==2.0.0,traceback2==1.4.0,trollius==2.1,unittest2==1.1.0,WebOb==1.5.1,wheel==0.29.0,wrapt==1.10.6,WSME==0.8.0,xattr==0.7.9
venv runtests: PYTHONHASHSEED='1343193181'
venv runtests: commands[0] | glance-api
--config-file=/home/teferi/glance/etc/glance-api.conf
/home/teferi/glance/.tox/venv/local/lib/python2.7/site-packages/paste/deploy/loadwsgi.py:22:
DeprecationWarning: Parameters to load are deprecated. Call .resolve and
.require separately.
return pkg_resources.EntryPoint.parse("x=" + s).load(False)
/home/teferi/glance/.tox/venv/local/lib/python2.7/site-packages/paste/deploy/loadwsgi.py:22:
DeprecationWarning: Parameters to load are deprecated. Call .resolve and
.require separately.
return pkg_resources.EntryPoint.parse("x=" + s).load(False)
/home/teferi/glance/.tox/venv/local/lib/python2.7/site-packages/oslo_middleware/ssl.py:28:
DeprecationWarning: The 'oslo_middleware.ssl' module usage is deprecated,
please use oslo_middleware.http_proxy_to_wsgi instead
"oslo_middleware.http_proxy_to_wsgi")
/home/teferi/glance/.tox/venv/local/lib/python2.7/site-packages/paste/deploy/loadwsgi.py:22:
DeprecationWarning: Parameters to load are deprecated. Call .resolve and
.require separately.
return pkg_resources.EntryPoint.parse("x=" + s).load(False)
/home/teferi/glance/.tox/venv/local/lib/python2.7/site-packages/paste/deploy/loadwsgi.py:22:
DeprecationWarning: Parameters to load are deprecated. Call .resolve and
.require separately.
return pkg_resources.EntryPoint.parse("x=" + s).load(False)
/home/teferi/glance/.tox/venv/local/lib/python2.7/site-packages/paste/deploy/loadwsgi.py:22:
DeprecationWarning: Parameters to load are deprecated. Call .resolve and
.require separately.
return pkg_resources.EntryPoint.parse("x=" + s).load(False)
/home/teferi/glance/.tox/venv/local/lib/python2.7/site-packages/paste/deploy/loadwsgi.py:22:
DeprecationWarning: Parameters to load are deprecated. Call .resolve and
.require separately.
return pkg_resources.EntryPoint.parse("x=" + s).load(False)
/home/teferi/glance/.tox/venv/local/lib/python2.7/site-packages/paste/deploy/loadwsgi.py:22:
DeprecationWarning: Parameters to load are deprecated. Call .resolve and
.require separately.
return pkg_resources.EntryPoint.parse("x=" + s).load(False)
/home/teferi/glance/.tox/venv/local/lib/python2.7/site-packages/cryptography/x509/__init__.py:32:
PendingDeprecationWarning: CRLExtensionOID has been renamed to
[Yahoo-eng-team] [Bug 1544964] [NEW] [glare] glance-glare fails with default paste config
Public bug reported:
$ tox -e venv -- glance-glare --config-file ./etc/glance-glare.conf
...
2016-02-12 16:02:20.318 16830 ERROR glance.common.config [-] Unable to load
glare-api from configuration file
/Users/teferi/openstack/glance/etc/glance-glare-paste.ini.
Got: ImportError('No module named router',)
ERROR: Unable to load glare-api from configuration file
/Users/teferi/openstack/glance/etc/glance-glare-paste.ini.
Got: ImportError('No module named router',)
** Affects: glance
Importance: Undecided
Status: New
** Tags: artifacts
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1544964
Title:
[glare] glance-glare fails with default paste config
Status in Glance:
New
Bug description:
$ tox -e venv -- glance-glare --config-file ./etc/glance-glare.conf
...
2016-02-12 16:02:20.318 16830 ERROR glance.common.config [-] Unable to load
glare-api from configuration file
/Users/teferi/openstack/glance/etc/glance-glare-paste.ini.
Got: ImportError('No module named router',)
ERROR: Unable to load glare-api from configuration file
/Users/teferi/openstack/glance/etc/glance-glare-paste.ini.
Got: ImportError('No module named router',)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1544964/+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 1543105] [NEW] Artifacts code conceals what/where errors happened during plugin loading
Public bug reported: Currently exception is converted to string and we get smth like "2016-02-08 15:47:53.218 12604 ERROR glance.common.artifacts.loader [-] Could not load plugin from assets.glance_image.v1.package: __init__() got multiple values for keyword argument 'mutable' " and the stacktrace shown later conceals the place where the actual error has happened. this doesn't help much with debugging plugin code. It would be great to have relevant stacktrace printed on errors in artifact definitions. ** Affects: glance Importance: Undecided Status: New ** Tags: artifacts -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1543105 Title: Artifacts code conceals what/where errors happened during plugin loading Status in Glance: New Bug description: Currently exception is converted to string and we get smth like "2016-02-08 15:47:53.218 12604 ERROR glance.common.artifacts.loader [-] Could not load plugin from assets.glance_image.v1.package: __init__() got multiple values for keyword argument 'mutable' " and the stacktrace shown later conceals the place where the actual error has happened. this doesn't help much with debugging plugin code. It would be great to have relevant stacktrace printed on errors in artifact definitions. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1543105/+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 1532086] Re: Use print('value') instead of print 'value' in python3
** Changed in: murano
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1532086
Title:
Use print('value') instead of print 'value' in python3
Status in Bandit:
Invalid
Status in congress:
New
Status in Murano:
Invalid
Status in OpenStack Compute (nova):
Won't Fix
Status in Trove:
Invalid
Bug description:
Do not use print 'some string' in python3, python3 will complain.
Use print('some string') instead, because that will work on both python2 n
python3.
It will help in adding support for python3.
Example:-
File : nova/tools/xenserver/stress_test.py
Line : 166
print "%s, finished in %.2f secs" % (result, duration)
To manage notifications about this bug go to:
https://bugs.launchpad.net/bandit/+bug/1532086/+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 1279611] Re: urlparse is incompatible for python 3
** No longer affects: murano -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1279611 Title: urlparse is incompatible for python 3 Status in Ceilometer: Fix Released Status in Cinder: Fix Released Status in Glance: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in python-neutronclient: Fix Released Status in Sahara: Fix Released Status in storyboard: Fix Committed Status in OpenStack Object Storage (swift): In Progress Status in tempest: In Progress Status in Trove: Fix Released Status in tuskar: Fix Released Status in zaqar: Fix Released Status in Zuul: Fix Committed Bug description: import urlparse should be changed to : import six.moves.urllib.parse as urlparse for python3 compatible. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1279611/+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 1280105] Re: urllib/urllib2 is incompatible for python 3
Would be fixed as part of a larger https://blueprints.launchpad.net/murano/+spec/murano-python-3-support ** Changed in: murano Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1280105 Title: urllib/urllib2 is incompatible for python 3 Status in Ceilometer: Fix Released Status in Cinder: In Progress Status in Glance: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Magnum: In Progress Status in Manila: In Progress Status in Murano: Invalid Status in neutron: Fix Released Status in OpenStack Compute (nova): In Progress Status in refstack: In Progress Status in Sahara: Fix Released Status in tempest: In Progress Status in Trove: In Progress Status in Zuul: In Progress Bug description: urllib/urllib2 is incompatible for python 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1280105/+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 1323975] Re: do not use default=None for config options
** 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/1323975 Title: do not use default=None for config options Status in Aodh: Fix Released Status in Barbican: Fix Released Status in Ceilometer: Fix Released Status in Cinder: Fix Released Status in congress: Fix Committed Status in Designate: Fix Released Status in Glance: Fix Released Status in glance_store: Fix Released Status in Gnocchi: Fix Committed Status in heat: Fix Released Status in Ironic: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Magnum: Fix Released Status in Manila: Fix Released Status in Mistral: Fix Released Status in Murano: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in oslo-incubator: Fix Released Status in oslo.messaging: Fix Released Status in Rally: Fix Committed Status in Sahara: Fix Released Status in tempest: In Progress Status in Trove: In Progress Status in zaqar: Fix Released Bug description: In the cfg module default=None is set as the default value. It's not necessary to set it again when defining config options. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1323975/+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 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong
** 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 OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1259292 Title: Some tests use assertEqual(observed, expected) , the argument order is wrong Status in Barbican: In Progress Status in Ceilometer: Invalid Status in Cinder: Fix Released Status in congress: In Progress Status in Designate: Fix Released Status in Glance: Fix Released Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): Fix Released Status in Magnum: Fix Released Status in Manila: Fix Released Status in Mistral: Fix Released Status in Murano: Fix Released Status in OpenStack Compute (nova): Won't Fix Status in python-ceilometerclient: Invalid Status in python-cinderclient: Fix Released Status in python-designateclient: Fix Committed Status in python-mistralclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in Sahara: Fix Released Status in zaqar: Fix Committed Bug description: The test cases will produce a confusing error message if the tests ever fail, so this is worth fixing. To manage notifications about this bug go to: https://bugs.launchpad.net/barbican/+bug/1259292/+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 1438975] Re: Image stuck "Queued" forever when creating image with invalid location URL
*** This bug is a duplicate of bug 1467787 *** https://bugs.launchpad.net/bugs/1467787 ** This bug has been marked a duplicate of bug 1467787 Validate create image url field -- 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/1438975 Title: Image stuck "Queued" forever when creating image with invalid location URL Status in OpenStack Dashboard (Horizon): In Progress Bug description: If you attempt to create a new image with Image Location and a unsupported URL scheme the image will get stuck as "Queued" forever. I'm proposing a patch that improves error handling for image create operations. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1438975/+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 1485925] [NEW] setting AVAILABLE_REGIONS breaks header layout
Public bug reported: To reproduce: set 2 available keystone endpoints in local_settings.py, for example like this: AVAILABLE_REGIONS = [ (OPENSTACK_KEYSTONE_URL, 'cluster1'), (OPENSTACK_KEYSTONE_URL, 'cluster2'), ] Then login to horizon and observe header and try to change cluster1 to cluster 2. The layout looks broken. https://www.dropbox.com/s/87a98mnvm2eadqk/Screenshot%202015-08-18%2012.13.25.png?dl=0 tested in Safari and Google Chrome. Git bisect pointed to Change-Id: I73c5529ae477a17f10a17946ac7120969578a0ba https://review.openstack.org/#/c/207660/ as the most possible cause of this behaviour. ** 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/1485925 Title: setting AVAILABLE_REGIONS breaks header layout Status in OpenStack Dashboard (Horizon): New Bug description: To reproduce: set 2 available keystone endpoints in local_settings.py, for example like this: AVAILABLE_REGIONS = [ (OPENSTACK_KEYSTONE_URL, 'cluster1'), (OPENSTACK_KEYSTONE_URL, 'cluster2'), ] Then login to horizon and observe header and try to change cluster1 to cluster 2. The layout looks broken. https://www.dropbox.com/s/87a98mnvm2eadqk/Screenshot%202015-08-18%2012.13.25.png?dl=0 tested in Safari and Google Chrome. Git bisect pointed to Change-Id: I73c5529ae477a17f10a17946ac7120969578a0ba https://review.openstack.org/#/c/207660/ as the most possible cause of this behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1485925/+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 1481384] Re: Package Definitions filters are working not properly
you should file a different bug to horizon, regarding image filters, not re-transfer this one ** Project changed: horizon = murano -- 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/1481384 Title: Package Definitions filters are working not properly Status in murano: Opinion Bug description: Filters on 'Package Definitions' page are filtering only packages only on current page not all packages. Preconditions: All packages is uploaded from http://apps.openstack.org/#tab=murano-apps Steps to reproduce: Navigate to 'Package Definitions' page Hit on 'Package Name' field Actual result: First package in the list is 'Docker Standalone Host' Expected result: First package in the list is 'Zabbix Server https://bugs.launchpad.net/mos/+bug/1481382 To manage notifications about this bug go to: https://bugs.launchpad.net/murano/+bug/1481384/+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 1473369] Re: new mock release broke a bunch of unit tests
** Also affects: python-muranoclient/kilo 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/1473369 Title: new mock release broke a bunch of unit tests Status in murano: In Progress Status in murano juno series: New Status in murano kilo series: In Progress Status in neutron: In Progress Status in python-muranoclient: In Progress Status in python-muranoclient kilo series: New Bug description: http://lists.openstack.org/pipermail/openstack- dev/2015-July/069156.html To manage notifications about this bug go to: https://bugs.launchpad.net/murano/+bug/1473369/+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 1473369] Re: new mock release broke a bunch of unit tests
** Also affects: murano 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/1473369 Title: new mock release broke a bunch of unit tests Status in murano: In Progress Status in murano juno series: New Status in murano kilo series: New Status in neutron: In Progress Status in python-muranoclient: In Progress Bug description: http://lists.openstack.org/pipermail/openstack- dev/2015-July/069156.html To manage notifications about this bug go to: https://bugs.launchpad.net/murano/+bug/1473369/+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 1464991] [NEW] Errors are not handled correctly during image updates
Public bug reported: To reproduce: Log in to horizon as unprivileged user. Navigate to image editing, try to mark an image as public. Observed result: an error message, stating: Danger: There was an error submitting the form. Please try again. Logs indicate, that an UnboundLocalError occurrs File /Users/teferi/murano/horizon/openstack_dashboard/api/glance.py, line 129, in image_update return image UnboundLocalError: local variable 'image' referenced before assignment This is because image variable is not handled correctly in image_update function. ** Affects: horizon Importance: Undecided Assignee: Kirill Zaitsev (kzaitsev) Status: New ** Changed in: horizon Assignee: (unassigned) = Kirill Zaitsev (kzaitsev) -- 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/1464991 Title: Errors are not handled correctly during image updates Status in OpenStack Dashboard (Horizon): New Bug description: To reproduce: Log in to horizon as unprivileged user. Navigate to image editing, try to mark an image as public. Observed result: an error message, stating: Danger: There was an error submitting the form. Please try again. Logs indicate, that an UnboundLocalError occurrs File /Users/teferi/murano/horizon/openstack_dashboard/api/glance.py, line 129, in image_update return image UnboundLocalError: local variable 'image' referenced before assignment This is because image variable is not handled correctly in image_update function. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1464991/+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
