[Yahoo-eng-team] [Bug 1763280] Re: Floating ip filter has no effect
Reviewed: https://review.openstack.org/560818 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=797859beb7848a6661940aa9028dbfcd2fcb28dd Submitter: Zuul Branch:master commit 797859beb7848a6661940aa9028dbfcd2fcb28dd Author: pengyuesheng Date: Thu Apr 12 16:02:01 2018 +0800 Floating ip filter has no effect the API of tenant_floating_ip_list add '**search_opts', Change-Id: Ie4f47f768909a2af7a916d2ad6ce43b3e157b432 Closes-Bug: #1763280 ** 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/1763280 Title: Floating ip filter has no effect Status in OpenStack Dashboard (Horizon): Fix Released Bug description: In the floating ip page, enter the information click filter, but the returned information is not what we expected,the filter did not work. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1763280/+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 1755958] Re: dashboard:make the image min_disk and min_ram valule empty, error report after user update image , not before
Reviewed: https://review.openstack.org/561115 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=f843b6389f9bc8bb67d59adbb22a97544bad0e75 Submitter: Zuul Branch:master commit f843b6389f9bc8bb67d59adbb22a97544bad0e75 Author: pengyuesheng Date: Fri Apr 13 11:29:09 2018 +0800 Make fields in image edit required Make the min_disk and min_ram fields in the image edit form required, so that the form can't be submitted with empty values for those fields, which always results in an error. Change-Id: I5a3fdb74f127ed1d084ac7b47dfd6e0d8b076a1c Closes-Bug: #1755958 ** 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/1755958 Title: dashboard:make the image min_disk and min_ram valule empty,error report after user update image ,not before Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The Dashboard UI Bug : dashboard->Project->Compute->Image->Edit mirror.Then make the Minimum Disk and Minimum RAM value null.we can also click the "Update Image".we will get the inf "Error:Unable to update the image".The UI should check the empty value and give the errors to inform the user of a problem. The Compare: If we give the "Minimum Disk" and "Minimum RAM" an invalid value,the UI will give user the hint about invalid value normally and the "Update Image" can't be clicked as usual. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1755958/+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 1789046] [NEW] unit test cannot be started under Python 3.7
Public bug reported:
Hi,
Building Horizon in Debian Stretch is no problem, and all unit test
pass. Unfortunately, under Python 3.7 in Debian Sid, it doesn't even
start to run unit tests:
+ http_proxy=127.0.0.1:9 https_proxy=127.0.0.9:9 HTTP_PROXY=127.0.0.1:9
HTTPS_PROXY=127.0.0.1:9
PYTHONPATH=/<>/debian/tmp/usr/lib/python3/dist-packages
PYTHON=python3.7 python3.7 -m coverage run /<>/manage.py test -v 2
--settings=horizon.test.settings horizon/test/unit
/usr/lib/python3/dist-packages/scss/selector.py:54: FutureWarning: Possible
nested set at position 329
''', re.VERBOSE | re.MULTILINE)
/usr/lib/python3/dist-packages/pep8.py:110: FutureWarning: Possible nested set
at position 1
EXTRANEOUS_WHITESPACE_REGEX = re.compile(r'[[({] | []}),;:]')
Traceback (most recent call last):
File "/<>/manage.py", line 25, in
execute_from_command_line(sys.argv)
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 381, in execute_from_command_line
utility.execute()
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/usr/lib/python3/dist-packages/django/core/management/commands/test.py", line
26, in run_from_argv
super().run_from_argv(argv)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
316, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
353, in execute
output = self.handle(*args, **options)
File
"/usr/lib/python3/dist-packages/django/core/management/commands/test.py", line
56, in handle
failures = test_runner.run_tests(test_labels)
File "/usr/lib/python3/dist-packages/django/test/runner.py", line 605, in
run_tests
self.run_checks()
File "/usr/lib/python3/dist-packages/django/test/runner.py", line 567, in
run_checks
call_command('check', verbosity=self.verbosity)
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 148, in call_command
return command.execute(*args, **defaults)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
353, in execute
output = self.handle(*args, **options)
File
"/usr/lib/python3/dist-packages/django/core/management/commands/check.py", line
65, in handle
fail_level=getattr(checks, options['fail_level']),
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
379, in check
include_deployment_checks=include_deployment_checks,
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
366, in _run_checks
return checks.run_checks(**kwargs)
File "/usr/lib/python3/dist-packages/django/core/checks/registry.py", line
71, in run_checks
new_errors = check(app_configs=app_configs)
File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 13, in
check_url_config
return check_resolver(resolver)
File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 23, in
check_resolver
return check_method()
File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 396, in
check
for pattern in self.url_patterns:
File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 37, in
__get__
res = instance.__dict__[self.name] = self.func(instance)
File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 533, in
url_patterns
patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 37, in
__get__
res = instance.__dict__[self.name] = self.func(instance)
File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 526, in
urlconf_module
return import_module(self.urlconf_name)
File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1006, in _gcd_import
File "", line 983, in _find_and_load
File "", line 967, in _find_and_load_unlocked
File "", line 677, in _load_unlocked
File "", line 728, in exec_module
File "", line 219, in _call_with_frames_removed
File "/<>/horizon/test/urls.py", line 36, in
url(r"auth/login/", views.login, {'template_name': "auth/login.html"},
AttributeError: module 'django.contrib.auth.views' has no attribute 'login'
Creating test database for alias 'default'
('file:memorydb_default?mode=memory=shared')...
Could someone from the Horizon team help me to find the solution? I need
this to be fixed in order to have Horizon for Debian Buster.
** 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/1789046
Title:
unit test cannot be started under Python 3.7
Status in
[Yahoo-eng-team] [Bug 1789040] [NEW] requests should be declared in requirements.txt instead of test-requirements
Public bug reported: requests is used in openstack_dashboard/exceptions.py, but it is only declared in requests in test-requirements.txt. It should be declared in requirements.txt. ** 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/1789040 Title: requests should be declared in requirements.txt instead of test- requirements Status in OpenStack Dashboard (Horizon): New Bug description: requests is used in openstack_dashboard/exceptions.py, but it is only declared in requests in test-requirements.txt. It should be declared in requirements.txt. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1789040/+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 1576425] Re: Security group changes can trigger thousands of messages
It's time to close this? Open a new bug for this if it's still an issue. ** Changed in: neutron 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/1576425 Title: Security group changes can trigger thousands of messages Status in neutron: Fix Released Bug description: There seems to be a scale issue with security groups and large number or agents. Users spinning up lots of instances in the same security group with source group rules can trigger orders of magnatutes more messages in rabbit that normal operation. Possibly this can be done more efficiently. I'm using Liberty To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1576425/+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 1750892] Re: Image remains in queued status after location set via PATCH
Reviewed: https://review.openstack.org/592775
Committed:
https://git.openstack.org/cgit/openstack/glance/commit/?id=e2c54d58b33c7350c78629cc7726b5fa4509637b
Submitter: Zuul
Branch:master
commit e2c54d58b33c7350c78629cc7726b5fa4509637b
Author: imacdonn
Date: Fri Aug 17 00:55:08 2018 +
Update status to active when locations replaced
Image status should be changed from 'queued' to 'active' when
'locations' has been successfully replaced.
Change-Id: I966688e67475e00a1eeb0cbe1632d5c811e41e4f
Closes-Bug: 1750892
** Changed in: glance
Status: In Progress => 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/1750892
Title:
Image remains in queued status after location set via PATCH
Status in Glance:
Fix Released
Bug description:
Pike release, with show_image_direct_url and show_multiple_locations
enabled.
Attempting to create an image using the HTTP backend with the glance
v2 API. I create a new/blank image (goes into "queued" status), then
set the location with:
curl -g -i -X PATCH -H 'Accept-Encoding: gzip, deflate' -H 'Accept:
*/*' -H 'User-Agent: imacdonn-getting-dangerous' -H 'X-Auth-Token:
xxx' -H 'Content-Type: application/openstack-images-v2.1-json-patch'
-d '[{"op":"replace", "path": "/locations", "value": [{"url":
"http://my_http_server/cirros.img;, "metadata": {}}]}]'
http://my_glance_api_endpoint:9292/v2/images/e5581f14-2d05-4ae7-8d78-9da42731a37e
This results in the direct_url getting set correctly, and the size of
the image is correctly determined, but the image remains in "queued"
status. It should become "active".
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1750892/+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
